We’ve implemented a workflow similar to the one in the below and are using it to revoke access against a SAP Source. The only real difference is our filter on the data into the loop. It works generally pretty well but for some of the access the account is locked during revocation and causes other items to fail, this is primarily due to the “Loop” function working in parallel (I missed this part during dev).
My question is, is there any way to do a better loop within workflow? My issue would be solved if there was a sequential loop.
My goal is to revoke all access thats not applied as birthright once a user leaves the org.
Please be sure you’ve read the docs and API specs before asking for help. Also, please be sure you’ve searched the forum for your answer before you create a new topic.
Hello Jesvin, I tried searching developer but missed that one. It would likely do the trick, let me look into it.
Thank you.
This email and any attachments transmitted with it are confidential and are only for the use of the intended recipient. If you are not that person, you have received this email in error. Please delete the email and any attachments and please tell the sender that the email was delivered to you by mistake. Distribution, forwarding, printing, copying or use the contents of the email is strictly prohibited and may be unlawful.
As a note, The information in the linked article says it won’t work work access. We attempted to pass the users IdentityID and the access through but were unsuccessful to get all the data through.
I hope we get a proper sequential look at some point from sailpoint in the workflows.
Please be sure you’ve read the docs and API specs before asking for help. Also, please be sure you’ve searched the forum for your answer before you create a new topic.