Existing users of Skelta Workflow.NET Release 1.8 can upgrade to Skelta Workflow.NET 2004, by purchasing an upgrade kit.

Important points to be considered before upgrading from Release 1.8.

1.  Take a backup of your configuration files, as well as the HTML templates, JavaScript files, CSS files and strings.txt that you have modified.

2.  Take a backup of the database configured for the applications.

3.  Delete the SkeltaTemp directory under the [Windows or WinNT]\Temp directory.

Upgrade Process Sequence

1.  If Release 1.8 is already installed on the system, the installer automatically detects the installed version and displays a warning message.

2.  Please read the details in the warning dialog and click the Next button.

3.  Select the Setup type from the next dialog and click on the Next button.

4.  Click the Install button on the next dialog to start installation.

5.  The Installer will popup the deactivation window (If the earlier version had been activated).

6.  Do not click on the Deactivate button in this window. The same license file will be used by the new version. So just close the window and the installation will continue.

7.  During the installation, the configuration files are automatically upgraded and the configured applications and actions are retained.

8.  The schema for the database configured for each application will be upgraded.

9.  After installation, open the WorkflowNET.Config.Xml and Actions.xml files and make the necessary modifications.

10.  Check and replace the HTML templates and JavaScript files from the backup.

11.  If you face any problems after replacing any file, delete the file and repair from Add/Remove Programs.

The following changes have been made to the configuration files in the new Release.

1.  The configuration for the Workflow engine and Task Scheduler has been moved to the WorkflowNET.Config.Xml file. The element contains all the settings for the Workflow engine and Task Scheduler services.

2.  A <virtualdirectorypath> element has been added to map to the virtual directory for the images and JavaScript files. This element is mandatory for all the applications. If this element is configured for a workflow, it will override the application settings.

3.  <contenthandler> elements can be configured for the workflows. Please refer to the documentation on configuring and developing content handlers for workflows.

4.  <blocking> element can be configured for workflows to specify the timeout and default URL for synchronization

  Skelta - A BPM Workflow Software Company