New hire - unknown in SNOW / Requested For

[LionelM]

Hello,

We're implementing SNOW with ITSM module. As an example, we want to allow managers to request for a new email , new AD account and new PC for a new hire (who is unknown in serviceNow when he request it). This will be in a single Order Guide.

Our user provisionning is AD sync, so it will be created in SNOW after AD account is created.

What would be the smartest move to handle the "Request For" in delivery module for exemple, for a unknown or external user ?

Based on the "new hire" order guide, we could add variables for first name/last name ... but when we arrive in the Delivery Module, we see a "Requested for" where the user does not exist.

Should we ask the manager, before any new Hire, to make a first request to create a local user in SNOW ? This seems tedious

[Dr Atul G- LNG]

Hi @LionelM 

1st thing first, its not SNOW, its NS or ServiceNow.

So in this , case you must create the user and then log a request via Order Guide. 

[LionelM]

Company has a lot of new hires, and we (as IT) don't know their identity (first name, last name). A lot of the managers want to simply ask for new accounts and hardware for people unknow in ServiceNow and AD.

We can't rely on HR infos to create them beforehand

[LionelM]

Hello,

As IT, we cannot create this users in advance as we don't know them. Only the managers have the identity infos like name and department (we cannot rely on HR for this beforehand).

Should we ask managers to go into a user record producer, THEN make their order guide ? 

Or ask them to make a request to create new user, wait for creation, then make a "new hire" order guide ? 

We can't be the only company facing that, it seems like a simple case

[Dr Atul G- LNG]

Hi @LionelM 

Agree on your point, in this case need to create user first and then order it. Or the manager can put his/ her name as requested For and later when employee join, transfer the asset to new user.