Order Guide Wait for condition script assistance

[Eric Dohr]

Hi Everyone,

I am hoping someone can assist in a solution that pauses requested items from moving forward after begin, until other RITMs are completed (in the event that the request has a RITM for create a new user).  

Any creative and simple ideas that we can delay a RITM from moving forward until certain RITMs are completed (in the event the order guide calls for that item).  

High level, we have order guides that utilize catalog items that use a master workflow (see below for RITM workflow).  Right now if you use the order guide it kicks off all the RITM and ultimately catalog tasks in parallel.  This works great, except in the event that we want a primary catalog item to run first, such as a Create New User.  

I am thinking a wait for condition script would be similar to "If the request has a requested item that uses catalog item "Create New user" wait until that is closed complete? 

This way the request can be updated to the new user and scenarios such as the hardware, app approval, etc are all in the name of the requested for versus opened by.  

Appreciate everyone's help!

Eric

Below is the workflow we are using in case that helps

• Begin
• (SCRIPT PLACEHOLDER FOR WAIT) I would think
• Set values - set the RITM to pending
• If - we have a variable on the catalog item that if populated, we want the config item to be set
• Approvals (our items could require approval from manager, users, and/or groups
• • Approval - User - runs if we indicate manager approval is required
  • Approval - User - runs if we incidate business approvers (list) is required
  • Approval - group - runs if we indicate group approval is required
  • Set values - now that approvals have been received, set it to fulfillment
  • We may have 1-5 catalog tasks on a RITM.  Based on a variable it will kick off and populate the catalog tasks based on variables
  • Wait for conidition - waits for all the catalog tasks to be completed

[Mark Stanger · Accepted solution]

Here's a good solution to this problem from SNGuru.

https://www.servicenowguru.com/system-definition/order-request-items-order-guide/

[Eric Dohr]

Thanks Mark!

Well I am defnitely closer now after this, but missing one piece.  When the primary requested item does finally close, it does not set the other requested items of that parent to the state for work in progress.  the only way I have figured out how to overcome this is to manually set the requested items from open to work in progress.

Any good suggestions on a script that when that first RITM does close complete, it updates the other requested items that are stuck in the wait for condition to work in progress, thus kicking off all the rest of the activities?

[Mark Stanger]

There is a 'Run script' workflow activity script in that document showing exactly how to do that.  Is that not working for you?

[Mark Stanger]

Just checking on on this one.  Has this question been answered or is there more information I can help you with?  If it's been answered, please mark the answer above as the correct one so people know this has been taken care of.  Thanks!