Deploying a package
Introduction
Having created a package with a collection of process flows for deployment to one or more virtual environments, you can deploy it.
Deploying a package adds all associated flow versions to a selected virtual environment. As part of the deployment, all process flow versions are enabled, so they will run in the virtual environment automatically, according to any defined trigger settings.
Need to know
You can deploy a given package to any active (i.e. deployed) virtual environment, as many times as you need.
If you deploy a package to a virtual environment and the package includes a process flow that already exists in that virtual environment, the package takes precedence - the existing version becomes
inactive
and the package version isdeployed
. Note that this behaviour differs from deploying a single process flow via process flow settings.When process flows are deployed via a package, they are enabled automatically (i.e. they will run according to any trigger shape settings).
Process flows are associated with a package for deployment purposes only. After a flow version is deployed, it won't be affected by any subsequent actions taken with the package - for example, if a package is removed, any associated flow deployments won't change.
The steps
Access virtual environment packages
Log in to the dashboard and select virtual environments
| packages
from the left-hand navigation menu.
Find the required package
Locate the package that you want to deploy (you can scroll the list, step through multiple pages, or search):

Select the deploy option
Click the ellipsis icon associated with the required package, then select the deploy
option:

Select a virtual environment
Click in the environment
field and select the required virtual environment - for example:

All flows in the associated package will be deployed to this environment. If the package includes a process flow for which a version already exists in the selected environment, the existing version in the virtual environment is replaced with the package version.
If you're in any doubt about what might be replaced in virtual environments as a result of this deployment, you can use the compare option to clarify updates.
Add notes & confirm your selection
Optionally, you can add notes for this deployment - after this, click the review
button:

Review pending deployments
Use the review
panel to double-check flow versions in the selected package - for example:

Deploy the package
When you're satisfied that the content of the package is correct, click the deploy
button - for example:

...all flow versions in the package are deployed to the selected virtual environment, and the deployments
count for this package is incremented in the packages
list - for example:

Deploy the package to the next virtual environment (optional)
If you need to deploy a package to multiple virtual environments, repeat steps 3-7 for each virtual environment in turn.
Last updated