Sources using flat files and integrated to ServiceNow via Service Desk integration will result in accounts being created in the target source. Does this same behavior happen if only SailPoint Tasks are used for manual fulfillment?
Hi Robert McCoy! Thank you for your input. This appears to be related to using the product features. I’ve moved your comment to our ISC Discussions and Questions category for greater help from the community.
1 Like
Hi @rmccoy-unum
As far as I understand you are interested to know about manual task provisioning. So if in case SNOW is integrated with ISC the requested details will be passed to Source to their particular operation group via a SNOW ticket which result Source owner assign the access and upload the file again.
But in case if SNOW is not integrated then any request is raised for a new user with requested access a manual task will be opened and assigned to the source owner. Post that owner need to manually provision the access and upload the file in ISC and once aggregation task run ISC will create an account with the requested access items.
Correct me if that’s what you are looking for.
Thanks,
Prashant
No, I’m trying to understand any differentiation TO THE ACCOUNTS in a give FLAT FILE source in two scenarios. Neither source EVER receives an account file import, only an entitlement import as needed when new entitlements are needed for requests.
- A provisioning plan includes a delimited file source which is fulfilled via ServiceNow task through the ServiceDesk integration.
- A provisioning plan includes a delimited file source which is fulfilled via SailPoint tasks.
In case 1, our experience says that the list of accounts in the Flat File Source will be populated with an account after the ServiceDesk receives a successful response from the integration.
I’m curious what happens in case 2.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.