Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

Need information on global configurations for 'Request' module

suchetadineshs
New Contributor
New Contributor

Hello,


Need information on global configurations for 'Request' module: Risk Level, Criticality Level, unable Asynchronous Request Creation. 

Version:2020.X

Thanks!

5 REPLIES 5

rushikeshvartak
All-Star
All-Star

https://saviynt.freshdesk.com/support/solutions/articles/43000606856-global-configurations-for-relea... 

You can refer above link


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

Thank you for the link. I have gone through the details. Few questions:

  1. What is difference between risk level and criticality level?
  2.  We set risk level as high in our environment. As per document, it should evaluate risks with level high and very high in request. For us it is evaluating medium risks as well.
  3. what is SOD level?                                                                                                                                                   It would be helpful if you have some screen-prints of those levels from SOD module.

Thanks!

Srinivas
Saviynt Employee
Saviynt Employee

Hello,

you came across  what’s a risk  & criticality of an entitlement from above mentioned Document.
These are attributes meant to curate entitlements to provide more information about them.
Once you have populated these values on entitlement you can use them on requests to automatically approve entitlements that are not critical or risky by using Smart Review.
 
SOD level is basically to calculate and display the number of violation items in the requested items.
 
Thanks & Regards
Srinivas

Hello Srinivas,

Set global configuration for risk level as very high and criticality level as medium. 

suchetadineshs_0-1665485779415.png

Request for entitlement having high risk and medium criticality is not auto approving. 

 

suchetadineshs_2-1665486162114.png

Thanks.

This configuration is not for auto approve. for auto approve you need maintain logic in Workflow.

This is used for smart review in ARS Request to show no. of sod violations based on configuration


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.