Leveraging Intelligent Recommendations for Operational Transformation. AMS Partners click HERE | EMEA/APJ Partners click HERE |
05/21/2024
06:18 AM
- last edited on
05/21/2024
10:38 AM
by
Dave
Hi Team,
After assigning access the ROLE_SAV_SODOWNER and ROLE_SOD_AUDITOR they still couldn't view the SOD violation list. Do we require any additional role access ?
Thank you,
Varsha
[This post has been edited by a Moderator to remove sensitive information.]
05/21/2024 06:25 AM - edited 05/21/2024 06:27 AM
enable preventive SOD violations on the ARS request page, follow these steps:
1. Make sure you have created the required functions and mapped the corresponding entitlements.
2. Set up the SOD Analysis function mapping for the specific ruleset.
3. Enable the "Show SOD in Request" option for the SAV role(s) of the users who should be able to see SOD violations during the access request.
4. Check the SOD configuration in the Global Config settings to ensure the "Evaluate SOD for role request" option is enabled.
5. Validate that the roles being requested in the ARS request have SOD conflicts defined in the SOD module.
6. Ensure that the requester has the necessary entitlements to trigger the SOD violations.
remove client url from sav role name
05/21/2024 06:48 AM
We are working on detective SOD
05/21/2024 10:32 AM
Does user is risk owner ?
06/03/2024 06:40 AM
yes ....We can see violation but risk code is not clickable. Attaching ss below
We need it in this way so owner can review it
06/03/2024 11:32 AM
Validated in latest version v24.5 and its working
06/04/2024 02:02 AM
Can you please ping all the access which you granted?
06/04/2024 06:00 AM
Used OOTB sod sav role