Click HERE to see how Saviynt Intelligence is transforming the industry. |
09/12/2023 11:49 AM - last edited on 09/13/2023 07:48 AM by Dave
I am working with a basic workflow with SOD approval required.
If I build the workflow without the SOD step (highlighted in red) the workflow works perfectly in Parallel workflow type. If I add the SOD section I have to switch to serial per documentation. When switched to Serial mode, There is an error when submitting the request due to access and manager approvals.
What is the CORRECT method for having a workflow that combines SOD escalation with a manager and access approval task. The goal is to have this workflow For security systems with or without SOD policies applied.
Workflow xml attached
[This post has been edited by a Moderator to add attachment.]
Solved! Go to Solution.
09/19/2023 09:26 AM
@JEllis It should work with the serial workflow type as well. Did you try to create a new workflow with type serial and check? Also, what errors are you seeing when you change it to serial? Might be something to do with the parameters or configs.
09/19/2023 12:31 PM
@JEllis For your first condition, entitlement.allowner.contains(user.username) eq true should route to Access Approval and if its false should route to Manager Approval but in your workflow its vice a versa. Also you don't need to add eq true in the condition. Can you change that and check?
09/21/2023 05:00 PM
There is a conflict in what is supported in Series and Parallel. The work around that I used for this case was to use parallel and do a manual assignment to user group.
There needs to be an enhancement to allow SOD owner on SOD violation approval on Parallel workflows.