Using Workflow Approval in OIM 11gR2PS3
With the PS3 release Approval policies have been deprecated by introducing workflow policies. Request generation and approval is governed by workflow policies.
However approval policies will continue to work in case of upgrade. We can configure SOA Workflows conditionally.
This is achieved by creating Approval workflow rules on the basis of any combination of following entity and their attributes:
1. User
2. Role
3. Organization
4. Application
5. Requester
However approval policies will continue to work in case of upgrade. We can configure SOA Workflows conditionally.
This is achieved by creating Approval workflow rules on the basis of any combination of following entity and their attributes:
1. User
2. Role
3. Organization
4. Application
5. Requester
Using this you can:
1. Bypass the workflow
2. Use separate workflows per entity attributes or their combination.
3. Combining two or more conditions to assign single workflow.
1. Bypass the workflow
2. Use separate workflows per entity attributes or their combination.
3. Combining two or more conditions to assign single workflow.
These rules can be defined using following format:
IF <Entity attribute><Operator>< Entity attribute Value>
Then
<workflow><workflow name >
IF <Entity attribute><Operator>< Entity attribute Value>
Then
<workflow><workflow name >
These rules resides in the operations.
Some sample workflow rules are as follows:
1. Approval workflow rule for the Modify User operation:
IF
1. Approval workflow rule for the Modify User operation:
IF
requester.adminroles
: CONTAINS: OrclOIMUserAdminRule
THENWorkflow : Direct
Note: colons used here for sanity and should be ignored.
Here, the rule condition checks if the requester is a member of the User Administrator admin role in the beneficiary’s organization. If the condition is satisfied, then operation is performed without initiating any approval workflow
Comments
Post a Comment