Deploying a single process flow to a virtual environment
Introduction
You can deploy any existing draft or inactive version of a process flow to a virtual environment.
This page provides instructions for deploying process flows in the context of virtual environments. Before deploying process flows to virtual environments for the first time, it's important to understand how flow versioning works - if you're not already familiar with this, please see Understanding flow versioning for virtual environments.
If you do NOT use virtual environments, different instructions apply; please refer to Deploying a process flow.
Need to know
A process flow can be deployed to any given virtual environment (or to
no environment) once. If you attempt to deploy a flow and an existing version is detected, you are prompted to overwrite the existing version as part of the deployment operation.Any version of a given process flow can be deployed to any number of virtual environments.
When a process flow is deployed to a virtual environment, it runs against the current deployed configuration version for that environment.
If a process flow includes a run process flow shape, the 'called' flow must be deployed to the same virtual environment. If a 'called' process flow can't be found in the same environment, an error is given, and the flow will fail.
Deploying a process flow to a virtual environment
Access the required process flow
Access the first process flow that you want to deploy.
Open process flow settings
Select the settings icon from the actions bar:

View deployments
Scroll down to the versions panel and click the view deployments option:

The view deployments page is displayed:

Choose an environment
Click in the environment field and select the required virtual environment from the dropdown list - for example:

Choose a flow version
Click in the flow version field and select the required process flow version from the dropdown list - for example:

Set a queue priority
Each process flow has a queue priority, defined in process flow settings. This applies to the process flow as a whole - any version you choose to deploy inherits this setting. If required, you can override the priority here:

Start the deployment
Click the deploy button to confirm your selections.

This deployment is added to the list and can be managed from here as needed.
Confirm the deployment
If any version of this process flow is found in your target environment (including no environment), you are prompted to confirm that you want to replace the existing deployment:

If you're satisfied that it's safe to proceed, confirm this action. At this point, the process flow is deployed AND enabled, which means it will run automatically as per any trigger settings.
Last updated
Was this helpful?
