ALM: User Guide

In this state, the documentation is developed. For the transition to "Approval", you can specify the roles of Participants who may perform this action. Using a predicate, you can specify that only the author of the document may submit it for approval.

On the same transition, add two system actions:

• Create approval (specifying the name of the approval template in the parameters, or without that)
• Set this state for all child pages, so that all sections of the document move synchronously to the "Approval" status.

If no template is specified for creating the approval, the system opens the form for creating an approval sheet, where all the necessary parameters can be specified.

Provide a path for returning document sections for rework, but allow this, for example, only for the document author, using the corresponding predicate on the "Return to work" transition.

For the "Approval" status, a transition into the same state must be created. The mechanism for approving project artifacts works on the basis of this transition. Use the system action "Set this state for all child pages" to make the process easier for approvers. Add the system action "Move to the next state when approval is complete" so that the document, with all its sections, automatically moves to the next state when all approvers on the current approval sheet have finished it.

The "Sign-off" transition is needed only when you have several approval stages carried out by different groups of people. Add a precondition on the transition so that it is not available until approval is complete. Add a system action that automatically closes the current approval (that is, moves it to the archive), and then an action that creates a new approval sheet, if that can be done, for example from a template. Otherwise, the approval sheet will have to be created again for this stage and its group of approvers.