-
Notifications
You must be signed in to change notification settings - Fork 4
workflow versioning
We generally identify a workflow with the workflow name. Any update to a current workflow will be saved as a different instance in the WorkflowDefinition model, with the same workflow name but with different id. We have introduced a new attribute in the WorkflowDefinition model named as latest(a boolean). This attribute will be set to true, for the latest update of the workflow definition.
The modeler is not changed to handle the versioning. The update is being handled in the backend. When you publish your workflow with the same name as an existing workflow, we will create a new workflow definition instance with the same name, but a different id. The latest tag of the old workflow definition is set to false and is set to true in the new workflow defintion.
As we assume that the workflow defintion posted/published with the same name as an update to an already existing workflow, it is important to be aware of the names of already deployed workflow definitions.
Currently we do not allow user to use old workflow definitions, only the latest workflow definition is used in creating any new workflow instances. Any pending workflow instances that use an old version of workflow defintion will continue to use same version.