Managing transitions at reassignment
When a transition is triggered, the responsible of the next transition is calculated.
If assignment of a person is modified, it may be necessary to re-trigger the previous workflow transition to update the next transition responsible.
Two cases can arise:
• case of back transitions
• case of loop transitions
In workflows supplied as standard, back and loop transitions are not used in normal workflow processing. They are reserved for the administrator to process exceptional cases.Back transition
When assignment modification infrequent, it may be sufficient to use back transitions.
In the example below on the Recommendation workflow, if the recommendation is in status “Action Plan to be submitted” and the recommendation owner changes, the administrator can:
• execute the “Ask for recommendation to be resent (Admin)” transition, and
• re-execute the “Send out recommendation” transition to update the recommendation responsible of the next transition
Loop transition
When person assignment changes are frequent, you can add a loop workflow transition on the status of the workflow concerned.
For example, in the "Top-Down Action Plan" workflow, a loop transition has been added on the "To be sent" state. In this way the action plan creator can easily reassign the action plan approver.
