Workflows created using Skelta Workflow.NET on the Development server have to be moved to a Production server for final deployment. Some points have to be taken into consideration while moving the workflows between these servers. These points are described below.

Development Server

• Export the process definition using the Export/Import tool provided in the Process Designer
• Custom actions and the exact dlls referenced by the custom actions need to moved
• HTML templates (available in the 'workflowelements' folder) that have been changed for the application UI – Work action templates, Custom action templates, etc. – need to be moved
• New custom actions configured in the Actions.xml need to be moved
• Application block configured in the Workflow.NET.Config file need to be moved

Production Server (Assuming Skelta Workflow.NET is installed)

• Configure the application block In the WorkflowNet.Config.xml
• Copy the relevant files (Templates in the “workflowelements” folder that have been changed for the application UI) and dll’s (Custom Actions and related dlls) in the appropriate locations
• If any custom actions were used add the same in the Actions.xml file
• Import the process definition using the Export/Import tool provided in the Process Designer
• Deploy the workflow using the Deploy tool provided in the Process Designer
• Make sure that all application blocks are configured properly including the database configurations

  Skelta - A BPM Workflow Software Company