When you use a fund approval hierarchy, you can require a minimum of two unique approval users. This process is modeled after a European workflow that requires two sets of eyes to review every exception prior to final approval. You can select the dual approval option at the status map level. If you require dual approvals, where you require two Eagle users for final approval, you can set up the Annotator (Role 0) user role as first level who provides initial approval and adds approval notes that another level can review for final approval.
When you use dual approvals, the first level of approval is always the Annotator (Role 0) level. The final approval is needed from at least one other different Eagle user at one of the other levels. This ensures two sets of eyes reviewed the exception. 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.
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?
Set Up Dual Approvals
Set Up Status Maps
Set Up User Roles
Allow Administrators to Override Final Approvals
WRITERS NOTE: does this apply to Dual Approval only or to all FAH clients?
Set Up Sign-Off Approvals for Roles 1 and 2 ?????
0 Comments