and more in a single search tool across platforms. Read the announcement here. |
11/16/2023 05:06 AM
Hello Experts,
We have Implemented ServiceNow as Managed Application and ServiceNow as a Ticketing System. We have different connection,security system and endpoint for serviceNow account and ticketing system.
Our requirement is when a new user is onboarded, it should create a ServiceNow account and a serviceNow Ticket and in the Technical, we have create account task for serviceNow account and for the ticket.
We are seeing the issue when generating the serviceNow ticket servicenow account has not created and There is a reference field in the ticket RequestedFor that we have to populate with serviceNow account sys_id for that user
Is there a way to make sure that ServiceNow account should provision first and Ticket later? more like somewhere I can specify provisioning order ?
11/16/2023 05:26 AM
Is there a way to make sure that ServiceNow account should provision first and Ticket later? more like somewhere I can specify provisioning order ?
@ashutoshkumar16 it is not possible. Once ticket is closed then new account will be created in ServiceNow.
11/16/2023 05:33 AM - edited 11/16/2023 05:36 AM
@SumathiSomala, Thanks for your reply, but we are treating SNOW ticketing system as a different application and SNOW account creating and SNOW Ticket Creation is completly independent task.
we have this precondition that when saviynt creates a SNOW ticket, SNOW account must be present. and as both ticket creation and snow account creation is part of the onboarding process we are seeing this inconsistency where some time ticket is been created first without any user associated with it as at the time of ticket creation snow account doesnot exist
11/16/2023 06:47 AM
Hi @ashutoshkumar16 ,
Try creating another Security System/endpoint as disconnected application to handle SNOW tickets.
Have a trigger chain Job, set the order of provisioning starts with SNOW Account creation and Disconnected SNOW Ticket endpoint. by this way you can achieve your use case.
Thanks,
Hemanath J