Deploying a process flow
Introduction
When a process flow is deployed and enabled, it runs automatically, according to defined trigger shape settings (or API requests).
Typically, you would build your required flow from the draft version and then deploy this however, it is possible to deploy an older, inactive version if needed.
There are two methods for deploying a process flow:
If you use virtual environments, the steps detailed on this page will vary - please refer to Deploying a single process flow to a virtual environment.
Method 1 (deploy button)
Access version details for the required process flow
Open settings for the required process flow and scroll down to the versions panel.
Select the required version
The currently selected version (i.e. the version displayed on the canvas) is shown with an 'eye' icon in the selected column.
Make sure that the version you want to deploy is selected here - typically, this would be a draft version, for example:
The selected version is shown on the canvas - double-check the process flow to ensure that it's correct.
Deploy the selected version
Click the deploy button (a little further up in the settings panel):
The process flow is deployed, and the canvas now shows the deployed version - for example:
Remember - a process flow must be both deployed and enabled before it runs automatically.
Method 2 (ellipsis actions)
Access version details for the required process flow
Open settings for the required process flow and scroll down to the versions panel.
Access version actions
Click the ellipsis icon associated with the draft or inactive version that you want to deploy:
Deploy the associated version
Select the deploy option:
The process flow is deployed, and the canvas now shows the deployed version - for example:
Remember - a process flow must be both deployed and enabled before it runs automatically.
Last updated