Modifying Workflows Already In Use

Workflows can be modified while they are going through their workflow steps after a package or request has been initiated. These modifications include adding new workflow steps, as well as changing the transitions, security assignments and notifications from within the workflow.

You can make changes to workflows that are in use by using the same procedures that you used to define the workflows from the Workflow Workbench.

Keep in mind that, when you modify workflows that are in use, specific limitations apply to which entities you can add, change, delete, or rename. These limitations are described in Table 7-9. Rules for modifying production workflows.

Table 7-9. Rules for modifying production workflows

Entity	Procedure
Transitions Security Notifications Workflow steps Workflow parameters	You can change any of these entities or add them to a workflow that is in use.
Transitions Security Notifications Workflow parameters	You can delete any of these entities from a workflow in use.
Workflow steps	You cannot delete this entity from a workflow in use, but you can rename it. You can delete transitions coming into or going out of a workflow step to effectively remove it from the workflow.

If a workflow that is in use is changed and saved, the changes take effect immediately. Any changes made to workflow steps are applied to all open package lines, requests, releases, and distributions.

Changes to a workflow can have undesirable effects on requests or packages that are in progress and are using that workflow.

Modifying a workflow that is in use can disrupt the normal flow in and out of the workflow and prevent it from reaching completion. For example, removing a transition from a workflow step may result in the requests or package lines getting stuck in that workflow step.