AnsweredAssumed Answered

How to stop Approval Workflow from firing

Question asked by Paul Cherrier on Jun 25, 2019
Latest reply on Mar 17, 2020 by Mostafa Helmy

Like • Show 0 Likes0
Comment • 2

I am trying to create two different approval workflows for the same Corporate directory: one for explicit access (one of entitlements) and one for roles.

How do I stop the explicit access approvals from triggering during a Role request (add/ remove entitlements + add/remove users)?

Role Request

CorpAD Approval - Explicit Access Approval Workflow (want this one to stop for role requests)

CorpAD Role Approvals

No one else has this question

Outcomes

2 Replies

Jamie Pryer Mar 11, 2020 6:58 AM
Mark Correct
Correct Answer
Mostafa Helmy - any thoughts on this one?
Like • Show 0 Likes0
Actions
Mostafa Helmy Mar 17, 2020 10:27 AM
Mark Correct
Correct Answer
It's not easy to answer this question right away without seeing all your workflow settings and understanding the full request and workflow flow.

That being said, here are a few guidelines:
If you attach a workflow to a Business Source through the "Request” tab, then it will always be called. So you should either:
Use one workflow with different logic flows if you want to attach it to a Business Source.
Not attach any workflow to any Business Source to ensure that the workflow always uses then workflows specific in the Approval Phase node.

It doesn't make sense to have an approval workflows that approves only "Roles” be assigned to a "Directory” since Directories cannot contain Roles.
Like • Show 0 Likes0
Actions

How to stop Approval Workflow from firing

Outcomes

Related Content

Recommended Content