Updating the process flow version deployed in a virtual environment

Introduction

Having deployed a process flow to a virtual environment for the first time, any subsequent updates must go through an update cycle, where:

1. Changes to the master process flow are made in a draft version.

2. The updated draft flow version is tested against the required virtual environments.

3. Existing deployments of this process flow are deleted from all virtual environments.

4. The updated draft flow version is deployed.

If you're not familiar with how flow version deployments work in virtual environments, please refer to Understanding flow versioning for virtual environments.

Different deployment approaches for process flow updates

The approach you take to deploy an updated process flow to virtual environments depends on how many process flows / virtual environments are being updated:

• One or two

• More than a couple

Updating one or two process flows in one or two virtual environments

With just one or two process flows in a couple of virtual environments, it's reasonably efficient to delete existing flow versions from virtual environments and then deploy the updated process flow version(s) individually.

For instructions, please refer to Deploying a single process flow to a virtual environment.

Updating multiple process flows in multiple virtual environments

If you need to update more than a couple of flows in different virtual environments, it's more efficient to deploy your process flow updates via a package. A package is a collection of process flow versions, which can be deployed to a virtual environment in a single operation.

When a package is deployed to a virtual environment, any existing versions of packaged process flows are overwritten - there's no need to delete them first.

For instructions, please refer to Deploying a package.