- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sunday
Change Approvals Flow
1. Peer review
2. Change Manager
3. Cyber,Ops,Architecture (do the following in Parallel)
4.CAB
In Part 3 It Creates the three separate approvals for each group and I have setup the approvals setting anyone approves or rejects. But it seems to be treating the three groups as One group and If one approves from one group it skips to step 4. I want to be able to treat each group as seperate but want to not have the groups wait on each other.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sunday
This is how I ended up solving it. See attached screenshots
1. Clear the Approval field in the Ask for Approval
2. If Approved I need to update the Change Approval fields back to Requested
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sunday
Current version is Yokohama
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sunday
Hi @markdart ,
When you use Ask for Approval with multiple groups at once, Flow Designer treats all approvers as a single approval set. then The “Anyone approves” setting applies to the entire set, not each group individually.That’s why the flow moves to the next step after a single approval anywhere.
as per my understanding you want Each group to have its own separate approval.
so Create separate approvals for each group
instead of passing all three groups into one Ask for Approval action, create three separate Ask for Approval actions:
Ask for Approval → Cyber
Ask for Approval → Ops
Ask for Approval → Architecture
in flow
using the action or the sub flow you can call this three approvals at the same time.
now your approval will now be independent.
use wait until or if condition , we can wait until approvals are completed.
After the parallel approvals complete, you can continue to CAB step.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sunday
Hi @markdart
For bringing approvals in change , you should use change approval policies, In Change approval policy define your approvers (change manager ,cyber ,ops ) Accordingly.
and in change flow, these policies will be called
for assess to authorize transition in change model write the following script as transition condition
(function (current) {
var gr = new GlideRecord('sysapproval_approver');
gr.addQuery('sysapproval', current.sys_id);
gr.addQuery('state', 'rejected');
gr.query();
if (gr.hasNext()) {
return false; // Block transition if rejections exist
}
// Check for pending approvals
var rechange = new GlideRecord('sysapproval_approver');
rechange.addQuery('sysapproval', current.sys_id);
rechange.addQuery('state', 'requested');
rechange.query();
// Allow transition only if no pending or rejected approvals exist
return !rechange.hasNext();
})(current); The above script will ensure that all approvers have approved
if my response proves beneficial to you then kindly mark as helpful & Accept as Solution
Warm Regards
Sumit Yadav
Technical Consultant
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sunday
HI I did have separate ask for approvals in the "do the following in parallel" I did read another article mention to clear the Approval field so it doent get set o the Change. But what i found is that after the first Group approval it still sets the Change Approval field to Approved but does actually let me approve on the other two groups before it creates the Cab approval. I am now getting an error on the Cab approval "Change model 'Normal' prevented state transition from Assess to Scheduled"
