App revisions

Revisions are snapshots of your workflow app at a specific point in time. In Workflow Designer, they help you managing changes and ensure the stability of your workflows.

The primary purpose of app revisions is to provide a robust version control mechanism for your workflow apps. By creating revisions, you can:

  • Make changes without affecting the current version of the app.
  • Revert to an older version of the app if needed. This allows you to return to a previously known good state of the app.
  • Provide an audit trail for changes made to the app.

Manage revisions

You can create revisions of your app in Workflow Designer to establish specific checkpoints.

Steps to create a revision

From the Apps page in your workspace:

  1. Navigate to the app you wish to manage.
  2. For the app, select More icon more → Create a revision.
  3. In the Creating a new revision dialog box:
    1. Enter a Key.
    2. Provide an optional Description.
    3. Click Create to create your revision.

Revision actions

Once revisions exist, you can view and perform several actions from the Revisions section of the app editor:

  • Revert to this revision: Restore the app in Workflow Designer to the state it was in when that specific revision was created.
  • Copy into workspace: Copy the selected revision into a different workspace.

    Create a revision and use this function to effectively copy the app to another workspace.

  • About: View information about the app revision.
  • Download: Download the app revision as a ZIP file for backup or sharing.
  • Delete: Permanently remove the app revision.

Important considerations

You can copy a specific app revision into a different workspace using the Copy into workspace action available in the Revisions section and use this as an effective way to copy an app to a different workspace.

You cannot copy a revision into the same workspace or into a workspace that already has a process with the same model key.

When you move an entire app to a different workspace, all associated revisions are included in the move.

However, there are specific scenarios to be aware of:

  • Conflicts: A conflict arises when a model in your app is linked to other models outside your app, or when a model from another app references a model in your app. In these situations, the conflicted models are copied instead of moved. The app retains its revisions, but there is no model history for the conflicted models.
  • Clashes: A clash occurs if there are models in the target workspace that have the same key as models in the app that you are moving. In such cases, the app revisions are lost for those particular models. No history will be available for those models.

The move operation provides advanced options that allow you to choose how to handle these conflicts:

  • Warn and stop: If the target workspace contains models with keys identical to the ones being moved, the operation stops with a warning. This prevents unintended overwrites or duplicate creations without explicit user intervention.
  • Copy conflicted models to the target workspace: This is the default behavior for conflicts.
  • Copy conflicted models from the shared workspace: This scenario is not possible in Workflow Designer as there are no shared workspaces.
  • Update existing models with moved versions: The moved models replace the existing models that have the same key.
  • Create new keys and move as new models: The keys of the moved models are renamed by appending a sequential number to the key names.