Configuration

Settings

Within the configuration element the next code has to be included:

<configSections>
	<sectionGroup name="futuramaSettings">
		<section type="ActuIT.Futurama.Config.MappingSection, ActuIT.Futurama.Engine,Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" name="mapping"></section>
	</sectionGroup>
</configSections>

Next to this code, also within the configuration element the next code has to be included:

<futuramaSettings>
	<mapping rootPath="{Rootpath}" allowedFolders="{AllowedFolders}" allowedDocuments="{AllowedDocuments}" parentFolder="{Parentfolder}" folder="{Folder}" document="{Document}"></mapping>
</futuramaSettings>

Explanation

Within the map element some attributes can be set. Below the possible values of these attributes.

document

Indicates which Futurama document will be loaded. Notes:

• this attribute is optional. If this attribute is not included the default value is used
• the default value is 'website.xml'
• this attribute is only used in Website mode
• it must refer to a valid Futurama xml-file
• the value of this attribute can be overruled in the URL of a browser by with the parameter: '?Document={Document}'. For example http://servername/futurama/?Document=site.xml will load the Futurama document site.xml instead of the document that is defined in the configuration file 

folder

Indicates in which folder will be searched for the Futurama document, mentioned above. Notes:

• this attribute is optional. If this attribute is not included the default value is used
• the default value is 'default'
• this attribute is only used in Website mode
• the location of the folder is relative to the root of the web-application (the location of the default.aspx)
• the value of this attribute can be overruled in the URL of a browser by with the parameter: '?Folder={Folder}'. For example http://servername/futurama/?Folder=application will load the configured default Futurama document within the folder 'application' instead of the folder that is defined in the configuration file

parentFolder

Indicates in which parentfolder the folder is. Notes:

• this attribute is optional. If this attribute is not included the default value is used
• the default value is empty (parentFolder="");
• this attribute is only used in Website mode
• the location of the folder is relative to the root of the web-application (the location of the default.aspx)

rootPath

Indicates within which path will be searched for the folder/document that is used in a webservice call of Futurama. Notes:

• this attribute is optional. If the attribute is not included, the rootpath equals the location of the application (that is, the location of service.svc)
• this attribute is only used in Webservice mode and Server/Batch mode (for Futurama Export)

Starting from Futurama 6, this property is also supported in Futurama Web. To be able to use a rootPath you have to make sure that all web requests, also for static files such as images, documents, javascript are managed by Futurama, instead of by IIS. You can do this by adding code like this to the web.config:

<system.webserver>
	<handlers>
		<add type="Telerik.Web.UI.WebResource, Telerik.Web.UI" name="Telerik.Web.UI.WebResource" path="Telerik.Web.UI.WebResource.axd" verb="*"/>
		<add type="System.Web.StaticFileHandler" name="AspNetStaticFileHandler-GIF" path="*.gif" verb="GET,HEAD"/>
		<add type="System.Web.StaticFileHandler" name="AspNetStaticFileHandler-PNG" path="*.png" verb="GET,HEAD"/>
		<add type="System.Web.StaticFileHandler" name="AspNetStaticFileHandler-WOFF" path="*.woff" verb="GET,HEAD"/>
		<add type="System.Web.StaticFileHandler" name="AspNetStaticFileHandler-TTF" path="*.ttf" verb="GET,HEAD"/>
		<add type="System.Web.StaticFileHandler" name="AspNetStaticFileHandler-JPG" path="*.jpg" verb="GET,HEAD"/>
		<add type="System.Web.StaticFileHandler" name="AspNetStaticFileHandler-CSS" path="*.css" verb="GET,HEAD"/>
		<add type="System.Web.StaticFileHandler" name="AspNetStaticFileHandler-JS" path="*.js" verb="GET,HEAD"/>
	</handlers>
</system.webserver>

If a handler already exists, for example for Telerik, you need to merge these. In your situation you might need extra handlers if you use other files in your Futurama website.

allowedDocuments (from Futurama 16.11)

This field contains a comma separated list that allows filtering of the Futurama documents that are allowed to load.

• This attribute is optional. If a value is absent, then the filtering mechanism is disabled, and all documents are allowed to be specified. Individual values must be separated by using the ',' or ';' character, and are case-insensitive.

allowedFolders (from Futurama 16.11)

This field contains a comma separated list that allows filtering of the Futurama folders that are allowed to load. Individual values must be separated by using the ',' or ';' character, and are case-insensitive.

• This attribute is optional. If a value is absent, then the filtering mechanism is disabled, and any folder value is allowed to be specified.