Apply Change Approval Policy ends after first approval

Ron Legters
ServiceNow Employee
ServiceNow Employee

This customer has really complex change approvals. In our flows, we've got a bunch of things happening in parallel. We got 'Apply Change Approval Policy' that can generate as many as 10 approvals, then we've got two more that need scripting to find the approval group or user. The issue is that if the scripted approvals are approved first, as soon as one of the Approval Policy approvals approves, the CR is 'Approved'. I found another post that says if the 'Approval' field is left empty parallel approvals will wait for each other, and that helped with the scripted approvals, but I don't see anything like that on the 'Apply Change Approval Policy' action. 

Is the solution to configure the Approval Policies themselves differently?

1 ACCEPTED SOLUTION

Ron Legters
ServiceNow Employee
ServiceNow Employee

For this customer, multiple approvals are based on Conflicts, so we queried for all applicable conflicts, then did a 'For Each' conflict, and for each conflict, created a record directly in the 'Group Approvals' table.  In the next step in the Flow, we collect the Group approvals records with a 'Look Up Records' step, then a For Each action that waits for them to be complete (Active = false, which means they're either approved or rejected). Then we update the Change request accordingly.

RonLegters_0-1754321649698.png

RonLegters_1-1754321706417.png

 

View solution in original post

5 REPLIES 5

Bird1
Mega Sage

I faced the similar situation and could achieve by.

 

- In Flow Designer, there's 'Do the following in Parallel' and there's multiple of 'Change Approval Polices' action insight.

- After each of 'Change Approval Polices' action, I will add 'Update Record' action to update that Change Request record, you set Approval field as empty from there.

 

Bird1_0-1721108455092.png

 

Bird1_1-1721108471407.png