Approvals are combining if approver is in more than one approval group

Jacob23
Mega Guru

Hi,

I have an issue that seems to be out of the box. My company's change process requests multiple approval groups at upond CR submission. These groups may contain the same person in multiple groups for one CR.

The issue that happens is that if ServiceNow sees that you are an approver in more than one group it will see your approval as ONE overall approval, rather than two individual approval sets.

 

See the below screenshots where you can see I created two approval groups under one approval action in a flow. I also added in Help Desk group.

System administrator is in the test groups and user 1 is in helpdesk

Jacob23_0-1668526933034.png

You can see the 3 approval groups added:

Jacob23_6-1668527385268.png

 

Then in the approvers section you only see one approval for the system administrator who is the only person in both test groups.

Jacob23_5-1668527281309.png

If I got directly to the sysapproval_group table I can see all 3 approval groups.

Jacob23_7-1668527408720.png

However, when I approve the 1 approval for system administrator, it will also approve the other test group pending approval.

Jacob23_8-1668527489265.png

Jacob23_9-1668527498931.png

Jacob23_10-1668527516229.png

With my process at my company the approval groups indicate a seperate part of the process that has been completed, so all approval groups have to be isolated.

We did have a custom action created for this, but due to the upgrade from Tokyo this broke in our Dev environment. I am trying to fix this now but it is a massive script, so I am wondering if someone has come across this and has an easy fix.

5 REPLIES 5

Mike_R
Kilo Patron
Kilo Patron

Since this appears to be upgrade/Tokyo related, it's recommended that you open a case with SN support.

I did open a case with them, sadly if you have anything custom it is out of scope of their normal support.

I do not have this issue in my PDI.

Each group approval is treated as a separate approval. See example

 

Mike_R_0-1668544800931.png

 

 

Since you mentioned you had the issue with Change, have you looked into using Change Approval policies rather than configuring the approvals in the flow?

instanceName.service-now.com/chg_policy_approval_list.do?sysparm_query=active%3Dtrue&sysparm_view=

 

https://docs.servicenow.com/en-US/bundle/tokyo-it-service-management/page/product/change-management/...

This looks interesting. I will give it a read and see if it is a good replacement. My manager was able to resolve the issue with our custom action. For some reason any action that handles a array but its value is empty it breaks in the tokyo release. Somehow, in previous releases servicenow was able to handle null arrays and continue with the rest of the workflow.