Change Model approach - seqential approvals

[stevejarman]

Is anyone able to offer any guidance/best practice for implementing sequential approvals under the Change Model (Change Approval Policies) approach to Change Management?

e.g. in the Assess stage, we want "Group 1" to approve the change, THEN "Group 2", THEN "Group 3" - i.e. if Group 1 hasn't approved it, don't even bother asking Group 2 yet.

By default, adding multiple approvals like this to the Change Approval Policy (regardless of the Order setting) will ask everyone at once, within a given Stage (e.g. Assess).

Would you approach setting up the "wait" in the Change Approval Policy, or must the Flow be customized to perform it somehow?

[Community Alums]

HI @stevejarman ,

You can go with Approval Coordinator workflow activity , it will look something like this :

Drawback for this is approach is that it sends out the approvals all at once.

You can go with this approach :Dynamic number of approvals

Mark my answer correct & Helpful, if Applicable.

Thanks,

Sandeep

[stevejarman]

Well the other issue is that OOTB, the Change Model "system" uses Flows instead of Workflows, and the Workflows only kick in when using mixed Legacy Change (i.e. Change Model = Empty clause).

Also - that drawback of "it sends out the approvals all at once" is that main thing I don't want to do 🙂

[stevejarman]

Has anyone worked with Change Models and knows how to achieve this? Sticking as close to OOTB as possible (i.e. using the Flows, not creating Workflows), but having the Change Approval Policy execute "sections" sequentially vs all at once?

[stevejarman · Accepted solution]

For reference, have solved this one. In brief, you need to:

* Set "Policy Inputs" on your Change Approval Policy to act as flags (True/False variables) on "batches" of approvals - e.g. "Round 1 Approvals Complete" or whatever names make sense in your situation.

* In you "Decisions", include these flags in the conditions - e.g. one condition might be "State is Assess and Round 1 Complete is False", and the next might be "State is Assess and Round 1 Complete is True".

* Copy and modify the OOTB Flow for the Normal Change Assess (or whatever you're working on) and shuffle it around to include multiple assessments of the Approval Policy.

In "Round 1" your flag (in my example here I called it "Peer Review") will be false.

In the "Round 2" Action, you'll check it to True in order to filter for the second round Decisions in the Change Approval Policy.