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

Example: Parametric Representation of a Set of Reviewers

The set of reviewers shown in the previous example is defined by the following node-level user data values:

typeEntity1=USER
typeEntity2=ROLE
entity1.name1={'task.personId'}
entity2.name1={'task.roleName'}
mainEntities=1,1,1,2,2,2
entityForApproverSourceList=1,1,1,2,2,2
approversSource=,,,,myRolesMemberList,{'flow.roleApproval.roleMembersList'}
fallbackAccountableType=,Accountable,Self,AccountableManager,,Accountable
defaultManager=DOMAIN\Lee_Andrew,{'flow.defaultManager'},{'flow.userApproval.portalUser.defaultManager'},{'flow.defaultManager'},{'flow.defaultManager'},{'flow.roleApproval.portalUser.defaultManager'}
aggregation=Weights
overruler=,,,,,
autoApprovers={'task.flowOwner'},DOMAIN\Heim,Arne
ignoreApproversFrom={'autoApproverNode'}
useApprovers=1,2,3,4,5,6

The following data fields correspond to fields and columns in the forms-based interface:

• mainEntities corresponds to the Type column.
• overruler corresponds to the Overruler column.
• approversSource corresponds to the MembersList column.
• fallbackAccountableType corresponds to the Accountable Type column.
• defaultManager corresponds to the Default Manager column.
• aggregation corresponds to the Condition field.
• autoApprovers corresponds to the Auto Approvers field.
• ignoreApproverseFrom corresponds to the Auto Approverse from Activity Name field.

The useApprovers field defines a subset of active reviewers. This field has no equivalent in the forms-based interface.