- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-04-2024 06:55 AM
We are having an issue with one of our Flows. At a certain step in the Flow, it will ask for approval from 3 teams (groups). We only need one person from each group to approve/reject in order for the Flow to proceed to the next step/action.
Here is how the "Ask for Approval" step is currently configured in our Flow:
Here is an example of what the Approvals look like (from the Approvers table) once they are created:
It shows 5 records, as two of the groups have two members, and one only has one member.
If exactly one person from each of the 3 groups approves, everything works exactly as expected, and the view above will then look like this:
The other 2 approval records are automatically change to "No Longer Required" (ServiceNOW OOTB functionality), as someone from that group has already approved, and my Flow Design proceeds to the next step/action, exactly as it should.
However, things do not work properly if there is a rejection. Here is another example. Here is the before image:
If two of the groups approve, but one rejects, here are what those records look like afterwards:
So even though each of the 3 group approvals have been addressed, for some reason ServiceNow does not change the remaining 2 "Requested" records to "No Longer Required", as it should. So the Flow Design never proceeds to the next step/action and is "stuck".
Why aren't these two records being updated to "No Longer Required"? Do we need to configure this differently? Breaking out the Approvals into three separate "Ask for Approval" actions (one for each group) isn't really an option, as the team requesting this wants all three to happen concurrently to help expedite the time it takes to turn these requests around.
Thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-04-2024 07:13 AM
Hi @jmiskey
please take a look at the following article which explains how to tackle different approval scenarios with Flow Designer and also yours is described there: https://www.servicenow.com/community/workflow-automation-articles/flow-designer-approvals-overview-w...
Maik
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-04-2024 07:13 AM
Hi @jmiskey
please take a look at the following article which explains how to tackle different approval scenarios with Flow Designer and also yours is described there: https://www.servicenow.com/community/workflow-automation-articles/flow-designer-approvals-overview-w...
Maik
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-04-2024 07:30 AM
Are you suggesting to set it up like this (image from your linked article)?
That could possibly work, though from my understanding is that it will reject it right away if anyone rejects, and not wait for the other two approvals to be completed. I just have to see if the team requesting this is OK with that. They initially said that they wanted all 3 approvals to be addressed before moving on.
Or are you suggesting trying to do something with "Decision Builder"? To be honest, that is the first time I have ever seen it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-04-2024 07:40 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-04-2024 08:37 AM
Thank you. They were agreeable to the proposed solution, so I am all set.
I am not sure I understand why my original way did not work as expected, but we have a working solution now.