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.
WRITERS NOTE: need more info for clarity. If an Annotator of level 2 and a final reviewer of level 4 look at it, exactly what do they do? What error severities occur when defined at different levels? What do the two people do when they use the system? Do they both approve or does only one approve?
WRITERS NOTE: if you do NOT use dual approval, do you still see the Annotator column populated in all edit test results?
About Setup for Dual Approvals
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 approvals:
- Status Map. Edit a status map to allow it to use dual approvals. For more information, see Create a Status Map That Uses Dual Approvals.
- 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.
- Approval of Sign-Off Results. Consider your usage of the right to approve sign-off results. In User Administration, the Allow Approval of Sign-Off Results option allows you to approve Sign-Off edits (Transaction, Valuation, and Audit Sign off edits). This option is similar to the option that allows you to clear prior period edits. Users with these rights can clear status sign-off edit tests
WRITERS NOTE: does this Sign-Off option apply to Dual Approval only or to all FAH clients? Does the UA option relate to the new sign-off tests?
About Approving Raised Edits
When you use dual approvals, the edits raise as a "-1" and the system reflects initial approval as Annotator (Level 0) regardless of approver role level. Because all edits need at a minimum a role level of 1 for final approval, this prevents a role level 0 Annotator from final approving any edits. Approval at the user role level that is equal to the edit test tolerance level acts as final approval and triggers a check for another unique approval user. If another approval user exists, the edit clears. If one does not exist, the final approval fails with a warning: Not all edits selected 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 approvals, 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.
Add Comment