Onboarding/new starter order guide and how to use requested for field when user is yet to be created

[Rob96]

Hi all

We are about to create an order guide for new starters which will bundle options for business application access and end user computing hardware. 

Currently our new starter catalog item gathers the name of the new starter in a custom variable and the request item is usually logged as requested for the person who creates it (usually the line manager). 

Our existing business application and hardware catalog items work the normal way with the person they are required for being entered in the requested for field at checkout.

My question is how do we link these in an order guide so that the follow on apps and hardware are able to collect the  requested for value after it has been created in the main new starter account creation task?

How are you achieving this if doing something similar?

[Laszlo Balla]

In general for onboarding activities, the requested for is the line manager of the new employee, or a department assistant, perhaps HR business partner, etc. Alternatively, you can get the new user account created, and either have the subsequent catalog items raised after the new employee record is there (similar to how a Lifecycle event would manage it) or raise it with requested for being the manager and simply have a process change that field later.

[Rob96]

Thanks Laszlo. I will look at a way to copy the username (once created) to the application and hardware request items.

[jtcash]

Did you ever have any luck building this out? I am working on a very similar scenario.

[Rob96]

Yes but a bit cumbersome. I then set up a sequence by choosing generate sequence to use process automation designer but the client is not using User Experience so I added a task that holds the flow until their service desk change the user in the requested for field. Once done the process automation moves the order guide forward with each RITM is now set with the new starter.