Programming Guide › Customizing Business Flows › Common Functionality in CA GovernanceMinder Workpoint Processes › Assigning Reviewers › Example: Forms-Based Representation of a Set of Reviewers

Example: Forms-Based Representation of a Set of Reviewers

Think of a set of reviewers as a matrix of settings. The form-based interface of the Building Blocks tab presents the set you define as a table. The following figure shows an OpenApprovalAction code block that defines a set of reviewers for a user-role link.

Each line of the table defines a reviewer.

The first three approvers reference the user entity under review, as follows:

• The first approver is always Andrew Lee.
• The second approver is selected by finding the user in the RACI configuration who is Accountable for the user entity under review.
• The third approver is the user under review, as indicated by the Self value in the Accountable Type column.

The last three reviewers reference the role entity under review, as follows:

• The fourth approver is the manager of the user in the RACI configuration who is Accountable for the role under review, as indicated by the AccountableManager value in the Accountable Type column.
• The fifth approver is selected by matching attributes of the role under review to the locally defined myRolesMemberList member list.
• The sixth approver is selected by matching attributes of the role under review to the member list specified by the flow.roleApproval.roleMemberslist parameter. If no reviewer is found, CA GovernanceMinder searches the RACI configuration for the user who is Accountable for the role under review.

A Default Manager is defined for all entries that search member lists or RACI to assign reviewers. If these methods do not find a reviewer, the review action is assigned to the default manager specified. No default manager is defined for the third approver (Accountable Type = Self) because the entity under review always exists.

None of the reviewers in this example is assigned Overrule privileges.

Weighted values are assigned to the reviewers, as indicated by the Weights value of the Condition field, and the values in the Weight column. CA GovernanceMinder concludes the review when the weighted sum of reviewers that approve exceeds the threshold value 70 shown in the Minimum Weights field.

Two automatic approval filters are defined, as follows:

• By PersonID: The Auto Approvers field lists two users who are treated as automatic approvers.
• By Node: The Auto Approvers from Activity Name field uses a process parameter to specify a node. The reviewers defined in that node are treated as automatic approvers.