Saviynt unveils its cutting-edge Intelligence Suite products to revolutionize Identity Security!
Click HERE to see how Saviynt Intelligence is transforming the industry.
Saviynt Copilot Icon

Need Clarification on SOD variables

Community_User
Saviynt Employee
Saviynt Employee
Originally posted on August 16 2019 at 19:12 UTC

1) How can we trigger SOD Risk workflow, request should be routed to different approver depending on the Risk, i.e of risk is high it should follow two level of approval, if Risk is medium then it should be routed to single level of approval. Please note that we have tried SOD workflow before and have observed that SOD violation workflow is not detected in case of Role modification although it was working fine in case of ARS.2) Can we add entitlement level attributes like Privileged, Module, Financial, Access Fields field in workflow to trigger approval based on Risk level?
This message was previously posted on Saviynt's legacy forum by a community user and has been moved over to this forum for continued exposure.
1 REPLY 1

Community_User
Saviynt Employee
Saviynt Employee
Originally posted on August 20 2019 at 11:29 UTC

I couldn't quite understand your requirement. What's your usecase here?


When someone requests for a new entitlement which causes an High Risk SoD, in case you want to have an additional approver you can do that by using expressions like the following in your workflow,

SODViolation.get('High')!=null and SODViolation.get('High') > 0


Let me know if you are looking for something different.






This message was previously posted on Saviynt's legacy forum by a community user and has been moved over to this forum for continued exposure.