System migration readiness
Before you migrate your Cora SeQuence system, you need to make sure that your workflow execution path does not contain elements that are not supported in V9.x.
Several Cora SeQuence activities are not supported in V9.x. As a result, before you migrate your data, you need to redesign all the workflows that include unsupported activities.
List of obsolete activities
|Human activities||Integration activities|
Identify obsolete workflow activities
Get a list of the workflows that include obsolete activities.
- Download the migration scripts.
- Run this script 00 - Pre-Migration List of Obsolete Activities in your System.sql.
For each obsolete activity, this script returns the following values:
- Workflow space name
- Workflow name
- Activity name
- Obsolete activity type
If the script returns an empty list, you don't need to redesign your workflows.
Redesign your implementation
Obsolete activities cannot be part of the workflow execution path. In case you have obsolete activities in the workflow execution path, you need to manually redesign the specific workflow.
- Human activities: Sequence 6 form and task activities should be reimplemented with V8 forms and tasks.
- Integration activities: If your implementation requires integration to other systems using obsolete activities, you need to change them to one of the supported integration activities, or implement custom code.
When you redesign the workflow, it is recommended that you create a new workflow version and work on the new version. After you have made all the required changes, activate the new version, so that new instances are created in that version. Instances of the old workflow can continue to run until they are closed.
For more details about workflow versions, see these articles:
The upgrade procedure does not delete obsolete activities, but changes them to a new type named Obsolete Activity. Obsolete activities remain in the workflow so their data can still be used for reports, but should not be connected to the workflow execution path. These activities cannot be opened or used on runtime pages, and will not display in the process tree.
In case obsolete activities stay as part of the workflow execution path, the workflow execution fails and an error is thrown.
Before migrating to V9.x, close all running workflow instances that use obsolete activities in their execution path.
In addition to handling obsolete activities, before you upgrade to V9.x, consider any customization that has been applied to your system. Any code customization needs to be reviewed, refactored, and adjusted to the V9.x application packaging requirements.
Following are some examples of customized code that needs to be handled before upgrading to V9.x:
- For Cora SeQuence V7 and later, server-side code added to runtime pages
- Workflow or activity extensions, such as custom properties
- Hooks added to the code, such as hooking up to the reassignment event of a task to add custom behavior.
- Customized Flowtime grids