Process flow versioning
Last updated
Last updated
With our process flow versioning system, you can be sure that a process flow that's currently deployed will never be edited (possibly with breaking changes) while it's in use.
To edit a deployed processed process flow, you take a copy as a and work on that - when you're ready, you can then .
Each time that you , the previously deployed version is saved as an version for future reference and, if required, future use.
At any given time, a process flow can be associated with one of the following version types:
Draft The process flow is being built.
A new process flow is added
A deployed version is copied to draft
An inactive version is copied to draft
Deploy
Deployed The process flow is currently in use, or ready for use.
A draft version is deployed
An inactive version is deployed
Copy to draft
Inactive The process flow was previously deployed but superseded by a later deployment.
A draft process flow is deployed
An inactive process flow is deployed
Copy to draft
Deploy
Deleted
There is always one draft version of a process flow. The draft version can be edited freely without any possibility of changing or breaking the version that's currently . With a draft version, you can add/update , and change the process flow name.
When you're working with a draft version of a process flow, you can take the following actions:
If you choose to run the draft version of a process flow manually, the draft version runs and any target connections will be updated. Where possible, it's always best to use sandbox connections when you're editing and testing draft process flows.
The deployed version of a process flow is the one that's currently in use (if it's enabled) or ready for use (if it's disabled).
If you run an inactive version of a process flow manually, the inactive version runs and any target connections will be updated.
You can view all versions of a process flow via the settings panel.
When you access a process flow, the version being viewed is noted in the title bar. If you are viewing a deployed or inactive version, you'll see a message advising that edits cannot be made, and the version number is displayed beneath the title.
To switch between different versions of a process flow, access the versions list and select the required entry.
Whilst it's often useful to refer back to an inactive version of a flow for a reminder of how things used to be set up, you may wish to remove older, inactive versions.
the process flow. If you enable a process flow when viewing a draft version, there's no impact on the draft version. However, the version will start to run automatically as per its settings.
. Use this option to run the draft process flow immediately.
. When you deploy a draft version, it becomes the currently deployed version and stays as the current draft - the previously deployed version becomes a new version.
The deployed version of a process flow cannot be edited - can't be added/updated, and you can't change the name. The only actions that you can take with a deployed version of a process flow are:
the process flow. Just because a process flow version is deployed, it doesn't necessarily mean that it will be triggered to run automatically as per settings. For this to happen, a process flow must be both deployed AND enabled.
. Use this option to run the process flow immediately.
. When you do this, the process flow remains deployed and an exact copy is taken as the current version, ready for you to edit - the existing draft version is discarded. This is a good solution if you've been editing a draft but reached the point where you need to restart from a known sound point.
Each time a draft version of a process flow is , the previously deployed version becomes an inactive version - so you have a full version history for all deployed versions of a process flow.
An inactive version of a process cannot be edited - can't be added/updated, and you can't change the name. The only actions that you can take with an inactive version of a are:
the process flow. If you enable a process flow when viewing an inactive version, there's no impact on the inactive version. However, the version will start to run automatically as per its settings.
. Whilst you can use this option to run the process flow immediately, it's not recommended.
. When you copy an inactive version to , an exact copy is taken as the current version, ready for you to edit (the existing draft version is discarded). There's no impact on the version.
. When you deploy an inactive version, it becomes the currently deployed version. The previously deployed version becomes a new inactive version, and the existing draft is not affected.
. Whilst it's often useful to refer back to an inactive version of a flow for a reminder of how things used to be set up, having lots of process flows with lots of inactive versions can be detrimental to system performance. In this case, deleting older inactive versions can be useful.
Deploying the version of a process flow - or deploying an version without editing it as a draft first - is a simple one-click operation from the versions list.
If you want to edit the currently version of a process flow - or an version - you must first copy it to draft. The existing version is replaced by the version you copy.
Step 1 Log in to the , then select process flows > process flows to access the manage process flows page.
Step 1 Log in to the , then .
Step 1 Log in to the , then .
Step 1 Log in to the , then .
Step 4 The version transitions to (and the previously deployed version transitions to a new version). If the process flow is , it becomes active immediately and will run as per defined trigger shape settings.
Step 1 Log in to the , then .
Step 4 The version transitions to (and the previously deployed version transitions to a new version). If the process flow is , it becomes active immediately and will run as per defined trigger shape settings.
Step 1 Log in to the , then .
Step 4 The existing version is replaced with the version you copied, ready to edit. The or version that you copied are not affected.
Step 1 Log in to the , then .
Step 4 The existing version is replaced with the version you copied, ready to edit. The or version that you copied are not affected.