Click HERE to see how Saviynt Intelligence is transforming the industry. |
06/24/2024 09:33 AM
Hi,
All the entitlements in a request are going to sod owner approval even if they are not part of SOD. I understand this is the expected behavior.
Is there any other option/config we can do to avoid this in a Parallel or Serial workflow? So that the non sod entitlements approval doesn't go to SOD owners?
06/24/2024 10:38 AM
Hi @sakshibansal , that is not expected behavior. Most probably it would be the way workflow is written , Can you share the workflow or screenshots of it.
You would need to use If else condition like SODViolation.get('Medium') > 0 and if no violation --> go normal path else SOD Path.
Thanks,
Amit
If this answers your query, Please ACCEPT SOLUTION and give KUDOS.
06/24/2024 08:00 PM
This is known defect and getting fixed in 24.7
SOD-2855
Refer https://forums.saviynt.com/t5/identity-governance/sod-approval-workflow-issue/m-p/97338#M63749
06/25/2024 06:40 AM
Team,
Per the latest update, this fix would be available by 24.8
Thanks,
06/25/2024 09:30 PM
Entire Request with all the entitlements will be going to the Risk owners.
It is an expected behavior as per the current product behavior with the SOD owner block.
Lets hope this get ammended as per input from @adarshk
06/25/2024 09:31 PM
Its not expected behaviour, Its defect this functionality was working in Non-EIC
06/27/2024 01:14 PM
@rushikeshvartak We were getting this issue in v5.5 as well. In some of the old forums post, you mentioned that it is an expected behavior.
For reference, https://forums.saviynt.com/t5/identity-governance/sod-approver-is-getting-all-entitlements-even-thou...
06/28/2024 02:21 PM
If you want to route based on sod priority then it should go to respective owner it was working before. In previous post i stated if there is sod then full request will go for group approval as it was discussion on user group as approval and not risk owner
06/30/2024 08:49 AM
We have the similar approval workflow in v5.5 where we check SOD > 0. But instead of group owner, we have configured SOD Owner approval block, So all entitlements in a request including the ones without SOD went to SOD owner for approval. Is this an expected behavior in Non EIC version?
If not, then it was not working in 5.5, so probably a bug there as well.
06/30/2024 09:03 AM
Its expected so owner can validate all ents requested