Versioning

How does versioning work?

In AireFlow, versioning sits at the workflow definition level. This means that you can create new versions of an entire workflow definition, but not individual tasks within a workflow.

Creating A New Version

To create a new version of a workflow, open the version manager by clicking the version in the workflow definitions list, then click "New Version". This will create a new version by duplicating the previous highest version. All triggers based on task events inside the workflow will be updated, but any tasks from separate workflow definitions that rely on task events from this workflow will need a new trigger adding to point to the new version of your tasks.

New versions are disabled by default, so nothing in your existing process will change until the new version is enabled.

Enabling or Disabling A Version

Using the version manager, a workflow version can be enabled or disabled. When a version is disabled, no tasks within it will be triggered. That includes both tasks triggered by custom events, and tasks triggered by events from other tasks.

Multiple versions of a workflow can be enabled simultaneously, however this can result in duplicate tasks being created if more than one version has tasks with similar triggers.

Editing A Version

To edit a specific version of a workflow, select that version using the version manager popup, then open the workflow editor panel like usual.

Upgrading In-Flight Workflows

If you have a long running workflow that someone is part-way through, disabling that version will prevent any further tasks in that workflow version from being created. If you only want to prevent new instances of that workflow being started, but allow existing ones to continue, then you should remove any custom event triggers from tasks at the start of the workflow, but leave the version enabled.

By removing only the triggers at the start of a workflow, any already running instances can be completed, but new custom events won't start the workflow for anybody else because there will be no relevant triggers. If there are any other workflow definitions that are triggered by the same custom events, they won't be affected by changes to triggers elsewhere.

Recomended Version Upgrade Strategy

• Only use a new version when something substantial needs to change, or you need to keep currently running workflows separate from instances of the new version
• Try to make changes compatible with already running workflows where possible
• Consider any clinical safety risks when disabling or enabling versions, and contact support@airelogic.com and clinical.safety@airelogic.com if any support is needed