Programming Guide › Customizing Business Flows › Common Functionality in CA GovernanceMinder Workpoint Processes › Assigning Reviewers › How to Define a Set of Reviewers › The Focal Entity of a Reviewer › Node Parameters for Focal Entities

Node Parameters for Focal Entities

In certification, suggestion, and change approval nodes, the following parameters define a numerical reference for each of the entities under review:

typeEntity1

Specifies the type of entity represented by the numeral 1 in entity fields of the node. In child processes of a certification, this parameter is typically the type of entity that is the focus of the certification.

Valid values: USER, ROLE, RESOURCE

typeEntity2

Specifies the type of entity represented by the numeral 1 in entity fields of the node.

Valid values: USER, ROLE, RESOURCE

The values of these two fields must describe the two entities of the link under review.

The following parameters use these numerical indexes to specify focal entity settings for each reviewer:

mainEntities

Defines the focal entity for each reviewer in the set. This field contains a comma-separated, ordered list of the numerals 1 and 2. Each entry represents the focal entity of a reviewer in the set. There must be one value for each reviewer in the set. Null values are not allowed.

entityForApproverSourceList

Defines the focal entity for each member list specified in the ApproverSource field. This field contains a comma-separated, ordered list of the numerals 1 and 2. Each entry represents the entity that is used to search the member list for one reviewer. There must be one value for each reviewer in the set.

Note: If no member list is specified for a reviewer, two consecutive commas indicate a null entry that corresponds to the null entry for this reviewer in the ApproverSource field.

Process-level parameters contain attribute values that identify the entities under review. These task-level parameters are mapped at the node level to fields named as follows:

entityX.nameY

Where X is 1 or 2, and Y is 1,2, or 3.

Example: Entity Declaration in User-Resource Certification

The UCertURes process certifies a User-Resource link in a user certification certification. Because the certification certifies users, the user entity is designated Entity1. The following fields and values are defined in both review nodes of the process:

typeEntity1=USER
typeEntity2=RESOURCE
entity1.name1={'task.personId'}
entity2.name1={'task.resourceName1'}
entity2.name2={'task.resourceName2'}
entity2.name3={'task.resourceName3'}

The Certify node in this process defines a single reviewer who is focused on the user entity, as expressed in the following parameter value:

mainEntities=1

The Open Approval Action node in this process defines a set of two reviewers. One reviewer is focused on each entity of the link under review, as expressed in the following parameter value:

mainEntities=1,2

Example: New Role Creation

The BBNewRole process creates a role. The owner of the new role must approve its creation. The following fields and values are defined in the Open Approval Action node:

typeEntity1=ROLE
entity1.name1={'task.roleName'}

In this special case, there is only one entity under review - the new role. Only one entity type is declared.