SOD owner approval generated in case of no violation

[kunal_saxena]

Hi,
We are creating a workflow wherein if a request has a SOD violation, then the request will initially go for SOD owner workflow. To implement this, we added the following condition in workflow:

If this condition is true, SOD owner approval is generated

This is working as expected. When there is a SOD violation, the request is initially sent for SOD owner approval. However, when we create another request for the same user which does not have a SOD violation, the request is sent for SOD owner approval in that case as well.

Please advise on how we can handle this. Ideally, we would only want to have SOD owner approvals for requests that have a SOD violation created as part of that request.

Thanks,
Kunal

[indra_hema_95]

Hi @kunal_saxena can you please share the screenshot's of the request history? And for a fresh users when you are requesting for non conflicting entitlements are you experiencing the same?

Regards,

Indra

[kunal_saxena]

Hi @indra_hema_95 , PFB the screenshot of request history:

We do not see this behavior for a fresh user when requesting for non conflicting entitlements.

[indra_hema_95]

Hi @kunal_saxena This request shows there is a violation in the request so it will go for SoD owner approval. If there is a violation in your request, it will go for the SoD owner approval. Do you have any request history where there is no violation but the request is still going for SoD owner approval?

Regards,

Indra

[rushikeshvartak]

• use one more if else sod eq 0 
• if true - send to manager approval
• else - send to sod owner approval

[kunal_saxena]

Hi @rushikeshvartak , We tried the steps suggested by you but the request is still going for SOD owner approval:

Example: Request for an entitlement that did not cause a violation. The request went for SOD owner approval as underlined below:

However, this request does show the pre-existing SOD violation for this user (for the same user, we had requested entitlements earlier which had triggered a SOD violation)

Thanks,

Kunal

[rushikeshvartak]

• This is expected behavior existing sod will be visible.
• and sod eq 0 condition should come first

[kunal_saxena]

@rushikeshvartak - I changed the order such that sod eq 0 condition comes first. Still, the request for a non-conflicting entitlement is going for SOD owner approval.

[rushikeshvartak · Accepted solution]

As mentioned existing sod will be visible 

below is configuration to disable [Global config - SOD ]

[kunal_saxena]

Thanks @rushikeshvartak . Disabling the setting in global config resolved the issue.