Virtual environment packages

Introdduction

A package is a collection of process flow versions that can be deployed to a given virtual environment in a single operation. If you have lots of process flows to manage, this is more efficient than deploying them individually.

Having created a package, you add the required process flow versions and then (when you're ready) deploy the package to each virtual environment. Once a package is deployed, it remains available so you can deploy the same set of flow versions in future.

Need to know

• A package can contain one version of any given process flow. If you need to deploy different versions of the same process flow, you must create one package for each version.

• 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 is deployed. 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.