Hello Team,
We disabled "Enable Recalculate SOD (Beta)" under global configuration to raise a new user account request with a violation, and it went for two levels of risk owner approval.
After disabling the option, the recalculate SOD button is not available on the request approval page and hence can't be utilized to refresh SOD violations on the request approval page if the violating role is removed prior to Risk Owner 2 approval. SOD violations appeared as expected on the request approval page for Risk Owner 2.
Once we removed the SOD violating role and the request was approved by Risk Owner 2 (without SOD recalculation), we observed that the request went to Risk Owner 1 for approval. On the request approval page for Risk Owner 1, SOD violations were appearing (though the SOD violating role was removed prior to approval by Risk Owner 2).
After Risk Owner 1 approved the request, access was provisioned as expected, and no violation appeared in the SOD workbench.
Our concern is that when Risk Owner 2 approves the request and the violating role is removed before the approval, then on the Risk Owner 1 approval page, the violation should be removed, but here it remains the same as on the Risk Owner 2 approval page. For Risk Owner 1, it creates confusion about whether a violation is there or not.
As of now, we are using a serial-type workflow.
Do you have any resolutions to avoid this confusion?
Regards,
Satyam
