Redirect workflows

When deactivating a workflow step that is currently Eligible for user action, the requests or package lines in that step will become stuck. Because the step is now unavailable, users cannot take action on it and will not be able to progress any further through the workflow.

The outgoing transition to be deleted is still intact, so the eligible package lines and requests will eventually be acted upon and flow out of the workflow step.

Add a new workflow step to the workflow and redirect the transitions to that new workflow step so that the movement of package lines and requests avoids the inactive step and is not interrupted.

For example, consider a workflow where you wanted to deactivate workflow step B in the sequence, as shown in Figure 4-2. Redirecting the workflow, Step 1.

Figure 4-2. Redirecting the workflow, Step 1

After removing the incoming and outgoing transitions to B, add a new workflow step D which will connect steps A and C, letting the workflow continue to process requests or package lines (see Figure 4-3. Redirecting the workflow, Step 2).

Figure 4-3. Redirecting the workflow, Step 2

Run the applicable reports again to make sure there are no entities eligible for action by the user in the step that was deactivated.