A: Browse to
K2 Management and find the workflow in the
Workflow Server node and select the
Versions tab. This tab shows all deployed version for the workflow in the
Version column. Example 1.0.x.x, 2.0.x.x, 3.0.x.x and 4.0.x.x (Default). In this example the default version is 4.0 and there are three previously-deployed versions of the workflow. To roll back to a previously-deployed version (in this case 3.0), select version 3.0 and click
Set as Default. The new default version of the workflow shows as 3.0 (Default). For more information, see
Versions.
When you set a previous version of a workflow as the default, keep in mind the following:
- Existing workflow instances are NOT migrated/changed/updated when you change the default workflow version.
- Changing the default version only affects new instances of the workflow.
- When you deploy a new version of the workflow, it automatically becomes the default version. Even if you previously set a different version as the default version. You may need to go back and reset the default version of the workflow if you deploy a newer version of the workflow.
- Since SmartObjects and SmartForms always use the latest deployed version, there is a possibility that modifying the default version of a workflow might result in unintended behavior if there are newer versions of SmartObjects and SmartForms referenced by the workflow, resulting in errors or unexpected behavior. Since it is unpredictable how SmartObjects and SmartForms may be used in workflows, it is difficult to provide specific guidance, but bear this potential impact in mind when setting the default version of a workflow. Where possible, it is recommended to allow existing instances of the workflow to complete before making changes to the default version of a workflow, especially when updates to SmartObjects and SmartForms are used in the workflow.
