Additional Attributes Searching and Modifying Request Templates

18-2 Oracle Fusion Middleware Users Guide for Oracle Identity Manager ■ Modifying Approval Policies ■ Modifying the Priority of an Approval Policy ■ Deleting Approval Policies

18.1 Approval Selection Methodologies

An approval process selection methodology is an algorithm that selects the approval workflow to be initiated. Based on the request type and the approval level, the request engine decides which methodology to be used and evaluates the approval process accordingly. If no approvals are defined at the request level, it means that a default approval process is invoked. This default approval process is shipped with Oracle Identity Manager and is assigned to the administrator. If no approvals are defined at the operation level, it means that a default approval process is invoked. If no template-level approvals are defined, then it is assumed that no approvals are required at that level. The following methodologies are used: ■ Request-Level Methodology ■ Operation-Level Methodology: Organization-Based Selection ■ Operation-Level Methodology: Resource-Based Selection ■ Operation-Level Methodology: Role-Based Selection

18.1.1 Request-Level Methodology

This methodology is used for all request types at the request level of approval. The determination algorithm of the request-level selection methodology is as follows:

1. Search for all the approval policies configured for the request level and for the

request type with which the request is associated in ascending order of approval policy priority. If the approval policies matching this criteria are found, then:

a. Evaluate the approval policy rules associated with each approval policy to

determine the approval workflow. When evaluating the approval policy rules, for the first approval policy rule whose evaluation results in true, the corresponding approval workflow associated with that approval policy is selected. If automatic approval is specified in the approval policy, then request level approval is automatically approved.

b. If none of the approval policy rules are satisfied, then it is considered that no

approval workflow is configured at the request level.

2. If no approval workflow is determined, then the default request-level approval is

selected. Note: Only the users that are members of the APPROVAL POLICY ADMINISTRATORS role are authorized to create, search, modify, and delete approval policies. See Approval Policy Management on page 15-27 for more information about authorization for approval policies. Managing Approval Policies 18-3

18.1.2 Operation-Level Methodology: Organization-Based Selection

This methodology is used for all user-related request types, such as Create User, Modify User, Disable User, Enable User, and Delete User, at the operation level of approval. The determination algorithm for the organization-based selection methodology at operation level is as follows:

1. Get the users organization entity for which request is created.

2. Search for all the approval policies configured for the operation level, for the

request type associated with the request, or for all organizations in ascending order of the approval policy priority. If the approval policies matching this criteria is found, then:

a. Evaluate the approval policy rules associated with each approval policy to

determine the approval workflow. When evaluating approval policy rules, for the first approval policy rule whose evaluation results in true, the corresponding approval workflow associated with that approval policy is selected. If automatic approval is specified in the approval policy, then the request is automatically approved at the operation level.

b. If none of the approval policy rules are satisfied, then it is considered that no

approval workflow is configured at the operation level for this organization.

3. If no approval workflow is configured for that organization entity, then follow the

organization hierarchy till either the root node or the domain boundary, which is the root organization in the organization hierarchy. Repeat step 2 for each organization node.

4. If no approval workflow is determined, then the default operation-level approval

is selected.

18.1.3 Operation-Level Methodology: Resource-Based Selection

This methodology is used for all resource-related request types at the operation level of approval. The determination algorithm for the resource-based selection methodology at operation level is as follows: 1. Get the resource entity associated with the request. 2. Search for all the approval policies configured for the operation level, for the request type associated with the request, or for all resources associated with the request in ascending order of the approval policy priority. If the approval policies matching this criteria is found, then: a. Evaluate the approval policy rules associated with each approval policy to determine the approval workflow. When evaluating approval policy rules, for the first approval policy rule whose evaluation results in true, the corresponding approval workflow associated with that approval policy is selected. If automatic approval is specified in the approval policy, then the request is automatically approved at the operation level. b. If none of the approval policy rules are satisfied, then it is considered that no approval workflow is configured at the operation level for this resource. 3. If no approval workflow is determined, then the default operation-level approval is selected.