Edition: Futurama Website/Futurama Export/Futurama Webservice

Module: Futurama Editor

User: System administrator


- License file

- User name and password for Futurama downloads

- Windows 2008 R2 server or higher (for client Windows 7 or higher)

- .NET Framework 4.6.2





This manual explains how to install the Futurama Editor. It also covers how to configure the Futurama Editor.


Visit the Futurama website to download the Futurama Editor code:

  • Go to
  • Go to the download section of the Support menu
  • Log in with user name and password
  • Click the most recent Futurama release
  • Extract the zip-file


Release folder

Use the release code from the folder 'exe'.

Installation initial version

If this is the first time the Futurama Editor is installed follow the steps in this paragraph. If the Futurama Editor is already installed consult the next paragraph 'Upgrading existing version'. To install the Futurama Editor module follow the next steps:

  • Create a new folder (for example Futurama) in which the code from the release folder can be installed
  • Copy the code from the release folder to this new folder
  • Copy the license file to this new folder
  • Rename the default.config to ActuIT.Futurama.Editor.exe.config (see the description in chapter 'Configuration' for the way the config can be configured)

To start the Futurama Editor double click on the executable 'ActuIT.Futurama.Editor.exe'. When double clicking on this executable the Futurama Editor will start. It is advised to create a shortcut to start the Futurama Editor. This prevents the navigation to the installation folder each time the Futurama Editor has to be used.

Upgrading existing version

If you already installed the Futurama Editor, and want to upgrade the existing version follow the steps in this paragraph. If this is the first installation of the Futurama Editor consult the preceding paragraph 'Installation initial version'. Follow the next steps to upgrade an existing version of the Futurama Editor:

  • Open the folder at the Windows webserver where you have installed the Futurama Editor code
  • Copy the code from the release folder to this new folder

Converting Futurama documents

The Futurama Editor is used to create new Futurama documents to develop a new Futurama application. In the situation that a new Futurama version is released and installed the existing Futurama documents are created in an older version. Futurama automatically converts these old documents to the new version at the moment that these documents are used for an application. This conversion however occurs everytime the document has to be read. If for example a website application is created with Futurama, everytime this application is visited the Futurama document first will be converted. To improve performance it is therefore recommended to convert and save these Futurama documents. This conversion can be done both manually and automatically. See the paragraph 'Converting Futurama Documents' how to convert these documents.

Converting Futurama Documents




After installing the Futurama Editor code further configuration for the use of the Futurama Editor is necessary. See below for this configuration.

Configuration File

In the release folder we provided a default.config. In the Installation steps mentioned above this default.config is renamed to ActuIT.Futurama.Editor.exe.config. In this configuration section the sections within this configuration file are explained.

configSections and futuramaSettings

Within the section 'configSections' you find a sectionGroup named futuramaSettings. This sectionGroup futuramaSettings is also a separate section in the config under the configSections section. Each section name within the sectionGroup futuramaSettings is also contained within the futuramaSettings section. Below a brief explanation of these futuramaSettings sections.

Configuration Log

It is possible to log errors, warnings, information messages and developers messages with Futurama. In the chapter 'Configuration Log' you can find information how to configure the configuration file to log this information.

Configuration Format

The format settings of for example dates and numbers are described in the chapter 'Configuration Format'.

Configuration Vision

The configuration of the connection between the Futurama Editor and Futurama Vision is described in the chapter 'Configuration Vision'.


The appSettings section of the configuration file is a place to store connection strings, server names, file paths and other miscellaneous settings that can be used by a Futurama application. The items inside the appSettings are items that need to be configurable depending upon environment. For instance, any database connection strings will change as you move your application from a testing server into production. With the Futurama formula 'ReadConfigKey' the value of any of these keys can be read and used within the modelling of your application. While developing with Futurama (using the Futurama Editor) in the configuration file of the Futurama Editor will be searched when using the ReadConfigKey formula.


The installation and configuration can be tested. See below how to test. If you encounter problems, check the chapter 'Troubleshooting'.

Open editor

Double click on the executable 'ActuIT.Futurama.Editor.exe' to start the Futurama Editor.


If you encounter problems with the installation of Futurama Editor check the sections below.

Logging information

In the ActuIT.Futurama.Editor.exe.config the log section is configured. First step in troubleshooting is checking the information in the different log files. Make sure that the log information is actually created. If you don't see any log information consult the chapter 'Configuration Log' for the settings to get this information.

Error message when opening Futurama Editor

When a error message appears while opening Futurama (for example: There is an error in XML document) there can be a problem in the settings.xml file. The settings.xml file contains the custom settings of the Futurama Editor. For example the settings of the windows within Futurama. Delete this settings.xml file and start the Futurama Editor again. This file is located in the user specific directory C:\Users\\AppData\Roaming\ActuIT\ (Vista, Windows 7 and later) or in C:\Documents and Settings\\Application Data\ActuIT\ (Windows XP and before). Note that in Windows versions using languages other than English these directories will have other names.

Windows in editor are frozen or invisible

In practice it can happen that during intensive use of the Editor the windows become 'frozen' or even invisible. Closing and restarting the Editor will then have no effect for the incorrect settings will be stored in settings.xml and re-applied. When this happens the solution is to close the Editor, remove the file settings.xml and restart the Editor. This will result in the Editor being started with the default settings. See the previous troubleshoot subject for the location of the settings.xml file.

Launching Futurama from a Network share

When the Futurama Editor is launched from a network share, the .Net has to be setup in such a way that applications which are launched from that share will have FullTrust rights. This can be accomplished by executing the following command:

%WINDIR%\Microsoft.NET\Framework\v4.0.30319\caspol.exe -m -ag 1 -url "file:////\\computername\sharename\*" FullTrust -exclusive on

Here %WINDIR% indicates the path to the Windows directory and \\computername\sharename is the share where Futurama is located.

License message

It is possible that a license message appears when starting Futurama. Check whether the license file is installed within the installation folder (see Installation paragraph for more information).

Consult the Troubleshooting page for more information how to troubleshoot problems that may occur during the installation.

Windows Platform FIPS error message

Browsing to the application gives the next error message: 'This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms'. This error can be disabled to change the Local Security Policy of the server. Below the steps to change the policy:

  1. go to Control Panel - Administrative tools
  2. Local Security Policy
  3. Local Policies
  4. Security options
  5. Policy: System cryptography: Use FIPS compliant algorthms for encryption, hashing, and signing
  6. Disable this policy

Related Topics

- ReadConfigKey: Futurama Formula to read settings from keys within the appSettings section of the configuration file

External Links

- Microsoft site with information how to configure FullTrust rights


If you have any questions about this subject or if you want to provide us feedback please send us an e-mail.

Updated: 2014-01-20