Approvals of other groups are set to no longer required when I reject approval for one group for approval policy! Need Help!!

[Laukik1]

Hello Experts,

I need help in understanding and solving the below scenario.

In the oob normal change workflow at assess state where approval policy is used, I've created another decision, now there are 2 approvals which get triggered based on the decisions, one to Hardware group and other to Database group.

Now on rejection of Database approvals, my hardware approvals are turning to no longer required. Ideally, I want the other approvals to happen as well, and not just take decision on one set of approval. How can I make it work using the approval policy only.

I've attached the screenshots and steps in brief, please let me know if further clarification is required .

[Mark Manders]

I think you need to ask yourself why you want the first approval at all. You are trying to create a flow that asks for approval but if the approval is denied, it still can go on? Why ask for approval at all? What's the business case? 

Since it's OOB, you need to check the OOB approval engine that simply says 'approval = rejected, let's not bother anyone else anymore' and change that to your flow, but be aware that this is one that also works on other records needing approval. But I'm curious about the why of this requirement.

[Laukik1]

Hello Mark,

Thank you for the reply.

I need to incorporate some additional approvals in the same policy. Which are dynamic and based on true/false conditions. You can take these as additional approvals when certain conditions are met.

Now as these are additional approvals, they are mandatory with the normal approvals that are triggered. Now when a normal approval rejects my extra approvals show up as no longer required, which is not the case, I need these one's to be in requested (Since I have a functionality to reset only rejected approvals in place)

Thanks,

Laukik

[Mark Manders]

In that case you need to dive into the OOB functionality behind it and make sure you don't break other processes while doing so. ServiceNow uses the concept of 'approval denied = not approved'. You also need to get into the states/stages, so you still have the correct information on the record.