This content has been marked as final. Show 7 replies
Two simple ways of doing it.
1. Make one approval workflow with two stages in serial in the task and attach that to OIM at operational level while set the template level and request level to auto approve.
2. Another is to create two approval workflows (which you already did) and attach them to the request level and operational level while keeping the template level as auto approve.
There can be other combinations as well depending upon on your exact use case.
Thanks for your reply.
Now I have 4 levels of approval.
Beneficiary Manager Approval --> HOD Approval --> IT Infrastructure Head Approval --> MD Approval.
Template level approval is set to Auto Approval.
I have created an Approval Policy at request level for Beneficiary Manger. Its priority is 1.
Similiarly for HOD, IT Infra Head with priority 2 and 3 respectively.
MD Approval is at Operational level.
Now when a request is raised, it is going to Beneficiary Manager and then to MD. It is skipping HOD and IT Infra Head approval.
Can you please tell how to define this flow of approval so that request goes from Beneficiary Manager Approval --> HOD Approval --> IT Infrastructure Head Approval --> MD Approval ??
Thanks in advance.
Looks like you have created 4 approval workflows and you have created separate Approval policies for all the workflows.
Why can't you create 2 approval workflows
1st one with Beneficiary approval --> assign this workflow as requests level approval policy
2nd one with the rest of the approvals --> assign this workflow to the operational level approval policy
Sorry had been off for sometime and did not see this.
Approval policy priority is used only to determine which 'one' of them would be picked during runtime, thus if you have 2 policies at one stage with different priorities, then the one with least priority would be picked up.
As another OP suggested, you can have 2 different approvals or why not move the manager approval to template level and utilize it and then merge the HOD, IT Infra Head into one approval at request level and then the MD Approval at operational level?
With operational level you need to understand that it would kick of multiple (n X n) child requests to the MD Approval if there are n number of resources requested for n number of users in a single request while at template and request level there would just be one request. Validate that with your requirements and you can select the approach you want.