Change CIs approvals
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-28-2014 12:13 PM
I have a requirement where on a change workflow i need to add approvals from the affected CIs added to the request.
I have created a new field called 'Change Approvers' on the cmdb_ci table which is a glide list and refers to the user table (not group). So I query the affected CI table and query the CIs of the change request and push them as individual approvers into one activity.
The approval activity waits for each approver to approve.
But i need to by pass (put other approval to 'no longer required') the approval even if one from the list approves for that CI but still wait for the other CI change approval list approvers to approve.
(Basically when one from the 'change approver' list of CI approves the other users in that CI 'change approver' list should become no longer required but the Approval list of the other affected CI should still be requested)
i have attached the script and the field screen shot for more clarity.
Please help me as soon as possible. Any work around would help. let me know if more additional information is required.
- Labels:
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-29-2014 01:43 AM
Hi Jijoe,
I am just thinking.....in the workflow itself, you can query the Affected CIs list, fire the Approvals for the first CI, then get approvals or rejections, check for if there are any more CIs, if not, move to next step, if yes, repeat the above process.
This way all the approvals might not get fired at the same point of time, and they would be per CI (this process would consume much time), but your target could be achieved.
Thanks,
Subhajit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-29-2014 06:38 AM
Hi Subhajit,
That is a good approach, but as you mentioned there would be a time issue, imagine if there are 10 affected CIs and the approvals are going to be fired individually the process will take forever.
Thanks alot for the thought though
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-29-2014 01:54 AM
This is why we used Group Approvals per CI, because once someone from that CIs group approves, that particular group approval record is marked approved but it still has to wait for the other groups added from the other CIs...
I think you would have to change the 'wait for' on the approval activity to 'Condition based on script' and then use a script to parse through each approval by unique CI. If I get a few minutes this morning will think about the script, but that's what I think you need to do. (or use approval groups )
below is an example of it being customised, unfortnuately not for your exact use case:
Custom Transitions for the Approval - User Activity - ServiceNow Wiki
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-29-2014 06:43 AM
The issue is that i can not possibly make it a group field, but yes am planning to go ahead and create temporary groups on the workflow for the CIs and delete them immediately the Change request has processed to the completed state.
Let me see how it works.
Thanks, buddy.