New Hire Order Guide Requested For with new user

[florian29]

Hi we are currently creating an Onboarding Order Guide by allowing a new user to be created, for this on the first page relevant information about the new user is filled in and then based on the input various Catalog Items are ordered. One catalog item is that a new user is created in ServiceNow and in AD, other items would be that hardware or services like accesses are ordered for the user. The forms of the other Catalog Items always need a Requested For, but I have not created a user in ServiceNow at that time, so I could use Cascade Variables to override the value. Does anyone have an idea how I can best solve this?

[Brad Bowman · Accepted solution]

You can either update the other Catalog Items to make Requested for not mandatory, or always populate this with the same dummy/system account, or the new user's manager.  Once the account has been created you can use a workflow script to find the other RITMs under the same REQ and update each requested for variable with the new value.

[florian29]

Hi Brad,

thank you for your answer, I think it is the best option to update the requested for variable with the user.

[Dasbeav]

Hey Brad, do you happen to have a screenshot of how do this? I am trying to look up the parent using "requested item record>parent>number" but I don't get any value back.

In the execution details parent just comes back blank:

[Brad Bowman]

Sorry, I'm not familiar with Flow Designer, but is there a way to point to requested item record>request rather than parent?  In a workflow script current is the RITM record, so I would use current.request.sys_id in a GlideRecord query on sc_request to get all of the RITMs with the same REQ.