OIM 11g R2 PS2 (11.1.2.2.) : OOTB Composites , Approval Policies and Disconnected App Provisioning
In this post, I will talk about something which I did not notice on first glance while working with OIM 11g R2 PS2. Well the change basically is that the all the OOTB approval policies don't come with the product and it is basically a blank slate to start with. OOTB there will be no approval policies in OIM that you will see.
But if you do an disconnected application provisioning it will go through "Request Level Approval" and "Operational Level Approval" next.
On further investigation I found out that approval workflows are hard coded in in process task adapters if I chose the Application Instance as Disconnected.
"ManualProvisioningStart" has the name of workflow attached "DisconnectedProvisioning!1.0" which gets directly invoked on create,enable,disable,modify etc. operations.
By default all connected applications will not go through any approvals since no approval policies.
We can still leverage existing 12 SOA approval workflows available on SOA Server.
But if you do an disconnected application provisioning it will go through "Request Level Approval" and "Operational Level Approval" next.
On further investigation I found out that approval workflows are hard coded in in process task adapters if I chose the Application Instance as Disconnected.
"ManualProvisioningStart" has the name of workflow attached "DisconnectedProvisioning!1.0" which gets directly invoked on create,enable,disable,modify etc. operations.
By default all connected applications will not go through any approvals since no approval policies.
We can still leverage existing 12 SOA approval workflows available on SOA Server.
- 2 certification related
- AutoApproval
- BeneficiaryManagerApproval
- DefaultOperationApproval
- DefaultRequestApproval
- DefaultRoleApproval
- DefaultSODApproval
- OAACGRoleAssignSODCheck
- ProvideInformation
- RequestorManagerApproval
- DefaultSODApproval
- DisconnectedProvisioning.
Also as was mentioned all self assign role/resource etc have been deprecated along with resource related request types.
Comments
Post a Comment