The newly added access request submitted trigger (not seeing any documentation/announcements for this) doesn’t work.
Upon trying to save/enable the workflow, it says it required an “access request approved” step to be in the workflow. I think this is unnecessary and there’s no reason for it to require that, but that’s a separate discussion.
Even after adding an “access request approved” action to the workfow, the same error still persists.
I’m guessing the new Adaptive Approvals features are going out to sandbox tenants now. This is super exciting (as someone who got to do some early testing, it’s a very welcome capability). See the ‘Approval Policy’ action to use with this trigger (and then you’ll be able to set that workflow as the approval for access items once once the workflow is enabled). Hopefully, the team will publish the documentation soon. But it should make more sense once it’s out.
Oh man I hope this “Approval Policy” action isn’t a required step. I’ve also been waiting a long time for this and I was really hoping this trigger would just be “Fire and Forget” so we can do whatever we want with the info. This is already looking to be more limiting than I’d hope.
Also this is actually production I’m referring to, this and a new option for adaptive approvals in the access profile approval configuration have showed up.
I’m surprised the document hasn’t been published yet. But this isn’t for fire and forget. It will allow you to dynamically build approval policies based on the context of the request (who requested, who is the target, what is requested, etc.) or even automatically decide an outcome such as auto-approve/deny based on the workflow—a feature I know a lot of us have been asking for.
“or even automatically decide an outcome such as auto-approve/deny” OK now this is awesome to hear, it was looking like this piece wasn’t going to be possible and that’s what I was most worried about. Thank you for clarifying that.
The documentation doesn’t go live until after the feature is live in production (ridiculous), it’s an official SailPoint policy for how they handle documentation.
Since it says “Adaptive Approvals Required” in the access request configuration on the access profile, I’m worried that this will be an extra module we will need to pay for rather than just being part of workflows. Do you know if that’s the case?
I agree - but I figured they’d publish it today since it’s in the tenants haha!
Since it says “Adaptive Approvals Required” in the access request configuration on the access profile, I’m worried that this will be an extra module we will need to pay for rather than just being part of workflows. Do you know if that’s the case?
I do not know to be honest - don’t see any changes here yet: SailPoint Customer Agreements Definitions and Additional Terms - SailPoint Product Documentation
well this certainly isn’t encouraging… I really hope this is part of “workflows” since it’s just a new workflow trigger and action…
I am also trying to use this trigger to TRAP the access request to check if the access request submitted is from SailPoint request centre or from ServiceNow catalog as the request centre cant be hidden but error msg is telling me to add approval policy which is not helpful.
Any idea if this later worked for you @benjaminoriold or anyone?
I am currently facing similar error when i try to save my workflow.
You can hide access items in the request center using Segment. Basically you can hide Roles, Access Profiles and Entitlements
The problem is that they for some reason are trying to sell this trigger to us. It’s not working because you haven’t paid for it. See: New Capabilities: Atlas Enterprise Edition
Feel free to leave a comment on that thread and upvote the other ones complaining about it to help us push for this to be part of workflows as is, rather than an upcharge which it should definitely not be.
No it will not. You can’t use that “Access Request Submitted” trigger at all without paying extra for it according to SailPoint 
awesome isn’t it. You probably see now why a lot of us are very upset about this in that other thread.
This is just a pure money grab for a feature that should have been standard OOTB
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
