When you use a fund approval hierarchy, you can require a minimum of two unique approval users. The dual approval process is modeled after a European workflow that requires a minimum of two sets of eyes to review every exception prior to the final approval. Otherwise, if you do not use the dual approval process, Control Center requires only one level of approval as long as that level meets, or is above, the level at which the edit test was raised.
About Annotators
When you use the dual approval process, you define an approval role level of 0, which has a default name of Annotator (Role 0). This is a reviewer-only user role level, or an "approval notes only" user level. Users assigned this role can add approval notes for review by another user in the dual approval process. The Annotator role does not have the ability to clear raised edits.
About Setup for Dual
...
Approval
You can select the dual approval option at the status map level. If you use the dual approval process, you must set up the Annotator (Role 0) user role as first approval role level. The Annotator is an initial reviewer-only role that adds approval notes that another approval role level can review for final approval.
If you plan to use dual approvalsapproval:
- Status Map. Edit a status map to allow it to use dual approvalsapproval. All funds assigned to that status map then follow the dual approval process. For more information, see Create a Status Map That Uses Dual ApprovalsApproval.
- User Roles. Set up user roles for use with the fund approval hierarchy that include the Annotator (Role 0) level, and assign those roles to the appropriate Eagle users. For more information, see Manage User Roles.
- Final Approval. Consider your usage of the Final Approval option and the Final Approval of All option, which allow you to approve edits at all role levels. In User Administration, you can use the Allow Final Approval Override option to control which Eagle users are authorized to use those options. If you use the dual approval process with the fund approval hierarchy, you typically do not allow general users to use the Final Approval or Final Approval of All options, requiring them to follow the dual approval process. You can use this option to allow high-level administrator users to circumvent the dual approval process and apply a final approval of edits in extreme cases, as needed. User do not see the Final Approval option and the Final Approval of All option unless you enable this option in User Administration.
About Approving Raised Edits
When you use dual approvalsapproval, you see an additional Annotator column in the edit test or validation results you can view in Control Center, supplementing the other roles in the fund approval hierarchy. The edits raise as a "-1" and the system reflects initial approval as Annotator (Level 0) regardless of approver role level. That is, the first Eagle user who approves an edit can only approve it at role level 0, even if that Eagle user has a high level role.
...
Not all edits selected in Control Center meet the dual approval requirements. Up until final approval, Eagle users can continue to add notes to the edit’s approval history.
About Unapproving Edits
When you use the fund approval hierarchy and approve edits, you can select the Unapprove As option to unapprove one or more edits and you can use the Unapprove All As option to unapprove all the approved edits on the page at a specified approval role level. However, when you set up your status map for use with dual approvalsapproval, you can no longer use the Unapprove All As option for cleared edits. This prevents a full reset of all edits. You must select specific edits to unapprove.
...