Option Pack › Option Pack Workflow › How to Configure Workflow › Define Approvers for Approval Tasks › Approver Type and Name

Approver Type and Name

The Option Pack has several default workflow resolvers. To define an approver, the type must be set first. The name field is context sensitive and changes according to the type which is selected. Also, all values provided in the name field are case sensitive.

Note: Settings in this configuration screen refer to usage of the default approval logic. Any change to the logic may lead to those values being ignored or treated differently.

Possible resolver types are as follows:

• Name

  Defines the user ID for the approver. For example, when selecting Name as the approver type, the "superAdmin" value can be set in the name field. This results in the superAdmin being the direct approver for the selected value.

• Manager

  Defines, automatically, the manager of the user who has changed to be the approver.

• Group

  Specifies that all members of the group get the approval notification, while only one must approve or reject the values. This field requires the name of a group defined in Identity Manager.

• AdminRole

  Specifies that members of the Admin role get the approval notification, while only one must approve or reject the values. This field requires the name of an admin role in the Identity Manager environment.

• AccessRole

  Specifies that all members of the role get the approval notification, while only one must approve or reject the values. This field requires the name of an access role in Identity Manager environment.

• Attribute

  Resolves the approver using a search. The search uses a single-valued attribute from the user (such as managerId) as the User's attribute and searches for all users who have the same value in the Approver's attribute (such as the %USER_ID%). Multiple users may be returned by the search, resulting in a behavior similar to a group.

Example

Approvers can be set as responsible for a particular department. The name of the department (or departments) is written to an attribute called approverForDepartment.
An attribute resolver setting defines the User's attribute as departmentNumber and the Approver's attribute as approverForDepartment. The result is that the approver becomes the person responsible for the user's department.