Workflow version control

Edit online

You can implement version control for your workflows. You can run, deploy, view, and tile specific versions of workflows.

Each time that you save changes to workflows, new versions are created. By accessing and manipulating specific workflow versions, you can implement version control in several areas of the application.

Version control in the Workflows page

In the Workflows page, when you select a workflow and click the Actions menu, you can view all versions of the workflow by clicking Manage > Versions. Use the Version history drop-down to decide which versions you want to view. By default, all versions are shown. To view only versions that have a name, select Named versions. To view only versions that are active (scheduled, tiled, or deployed), select Active versions.

For each version, the following information is shown:
  • The name of the version, if it has a name.
  • The date and time that the version was created.
  • The username of the user who created the version.
  • Tags that indicate whether the workflow is active or whether it was pushed to a GitHub repository.
    • If a Git tag is shown, hover over the information icon beside the tag to see the hash and message for the Git commit.

When several versions of a workflow are created in the same working session, they are grouped under the same drop-down entry. In these group entries, the names of all users that created versions in the group are shown in a comma-separated list.

By clicking the overflow (three-dot) menu for a version, you can perform these actions:
Name the version
Rename the selected version.
Open the version
Open the selected version in read-only mode in the workflow editor.
Restore the version
Restore the selected version as the latest version.
Save the version as a copy
Save a copy of the selected version as a separate workflow.

Version control in the workflow editor

In the workflow editor, you can view all versions by clicking the Versions toolbar button. The list of saved versions is shown. Click the overflow (three-dot) icon to view the available actions. You can open an old version in a separate browser tab, rename a version, restore a version to become the latest one, or save a version as a separate copy.

Version control during workflow deployment

When you deploy a workflow by using the API gateway, you can specify which version you want to use when the workflow is run from the API endpoint. You can use the latest saved version, the version that was the latest when the deployment was created, or a specific version of your choosing. For more information, see Deploying workflows.

Version control in Automation Center

When you create a tile in Automation Center to run a workflow, you can specify which version you want to use when the tile is run. You can use the latest saved version, the version that was the latest when the tile was created, or a specific version of your choosing. For more information, see Using Automation center.

Version control in job scheduling

When you schedule a job to run a workflow automatically, you can specify which version you want to run. You can use the latest saved version, the version that was the latest when the job was created, or a specific version of your choosing. For more information, see Creating jobs.