Hi, I have a delimited file connector acting as a disconnected app. I have accounts and entitlements already aggregated. I need to request an entitlement for an identity who already has account created. I correctly receive the manual complete task, and when I complete it as a owner, request appears as completed (and granted). However, entitlement does not appear neither in identity entitlements page, nor the account detail page.
Hi @jsosa
This is the expected behavior on ISC, So before even you mark it as completed you need to have that particular entitlement added in the file, aggregate the delimited file and then mark the manual task as completd.
If you are looking to automate this process, i would suggest to create a workflow with provisioning completed as a trigger and then filter based on the source name and use the create account API to update the delimited record information directly on the source.
Feel free to connect with me, if you need more information.
With my experience, the Provisioning Completed trigger is not fired when a manual task is completed.
An alternative solution would be to use the API Work Items | SailPoint Developer Community to identify the Manual Action work items, determine the associated action, and then perform the required operations using the Account API Accounts | SailPoint Developer Community
This is currently a limitation of the Delimited File Connector in ISC. The connector assumes that, once the manual task is validated by the source owner, the required action has already been performed on the target application.
Therefore, before validating the task, the source owner is expected to:
- Perform the required action on the target application.
- Upload the corresponding CSV file containing the action to the ISC Delimited File source account aggregation section.
Only after these steps are completed should the manual task be validated.
If you check the SailPoint Ideas portal, there may already be an enhancement request related to this limitation. If not, I would recommend submitting a new idea for consideration.
It is triggered as again the manual task completion is also a provisioning activity. you can give it a try.
@luckyn Have you tried it?
We’ve tried it multiple times in one of our integrations a while ago, and I can confirm that it does not work. We also observed that the provisioning feature cannot be enabled for a Delimited File source or has no effect.
It seemslike that this connector is handled differently from other connectors when it comes to provisioning events and provisioning-related triggers.
@baoussounda i did, So this is how you can also replicate the same.
Request an entitlement from delimited source for the identity.
Once the request is processed and manual task is generated subscribe to a Provisioning completed trigger and possibly use the webhook site or anything of your choice.
Complete the manual task on ISC. and see the provisioning completed action being triggered from ISC to your Webhook
with the above steps you can re-produce the same output.
@luckyn , you’re right.
I was mistaken. I asked the same question about two years ago, and after testing it , I confirmed that it does work here Trigger “Provisioning completed” for manual sources - Identity Security Cloud (ISC) / ISC Discussion and Questions - SailPoint Developer Community
The issue we experienced was caused by another technical limitation in the workflow logic, not by the trigger itself.
Thanks
@jsosa, there is also an existing enhancement request in the SailPoint Ideas Portal for this feature: Enable automatic account creation and | SailPoint Ideas Portal
I have been waiting for this feature from last year.