In the workflow configuration, there is a new section in the transition dialog for Approvals. This allows a user with administrative permissions to define required approvers for a workflow status before the form can progress to the next step. Multiple approvers can be required to advance the workflow status if desired.
Required approvers are added via the dialog section above. Individual approvers can be selected, or you can assign a Role as an approver, where any user defined with the role will be a required approver.
The Enforce the order of approvals option requires that the approvals are made in the order in which they appear here. You can use the drag and drop method to position the approvers in the correct approval order.
Once all of the required approvers have approved the transition, the workflow can progress to the next status.
For required approvals, you can also assign the approval to a role instead of just an individual user. Along with a role based approval, you can define a number of required approvers for that role before the approval can be completed and progress to the next status. For instance, if there are 5 project managers in a project, you can require that at least 2 project managers approve the transition before it can be progressed to the next status.
There is also a section where you can define conditions on which approvals may be necessary. Under the Required Conditions section you are able to select a property which is included on the form and place a condition on the property where, if met, will require approval from the list you define.
For instance, if there is a property such, as Risk, where you define an amount which will require approval, this is where it is defined.
The Require Approvals with Conditions behaves the same as the standard Required Approvals where you can assign multiple approvers to the condition.
And like the Required Approvals detailed above, you can assign a role as an approver and define a number of required approvers for that role before the approval can be completed and progress to the next status.
If multiple approvers are required, then attempting to execute that transition puts the form instance into a locked "Under Review" state.
Note: If no approvals or conditions are set, the workflow works as it has previously where the user can progress the workflow if they have the correct permissions.
When an required approver opens the the issue it will appear as "Under Review" with the option to Approve or Reject the form.
Note: The Approve button is only enabled if the user is on the list of approvers.
When an approver has approved the form it will still be in an "Under review" state until all approvals are made. The workflow footer will appear as shown below to all have approved the form or are not on the approvers list:
Canceling (Rejecting) the approval puts it back into its original state and removes the lock. If all the users approve, then it automatically moves into the next state and removes the lock.
The Reject button is available to anyone with permissions to execute the transition.
Once all of the required approvers have approved the transition, the workflow can progress to the next status.