Service Request - Multiple approvals

[Wade Clairmont]

Hey there,

I have created a service request that will require manager approval, then multiple approvals based upon the selections made from the 22 variables.

The issue that I am having is...... I can check the variables in the workflow, and generate an approval for each of the one specified, however, I cannot get the wait for the selected approvals to proceed past, because it is waiting for the 16 possible approvals to be completed.

Is there a way around this?   I need this to gain all approvals concurrently, then once the required ones are approved, then generate one single request.   Anything rejected will automatically reject the request which is what we need,

Any ideas?   I have attached a pic of the workflow that I currently have for reference.

Thanks in advance,

Wade

[Wade Clairmont]

That totally makes sense.   I will give it a try.

Thanks so much for your assistance.

Wade

[luba_bohad]

Hi Wade,

I have the same issue, did you manage to fix this?

Thanks

Luba

[poyntzj]

Didn't see this at the time, but you can consider the approval co-ordinator, or as rfedoruk says, scripts.

I guess you can do this with an awful lot of if statements, however, we had a routine written for us that did this and it was so hard to diagnose and maintain.

I took the scripts a little further on.

Using a table that basically has links to the existing approval groups and then a number of criteria fields

A workflow script is created that reads different parts of the forms and passes them to a sub workflow

The sub workflow then takes the input properties and calls the relevant approvals as you need.

https://community.servicenow.com/message/720937#720937

You can make this as flexible as you like.

For us it makes it easy as the table is pretty easy to maintain and can be expanded as and how you need it

Since I wrote the above linked message, the group information is now stored in the scratchpad instead of re-processing the groups (I could forsee an issue)

The scripts are now so large that if any future updates are made, it will need to call a Script Include instead of being embedded in the workflow itself

[Wade Clairmont]

Yes, we did resolve this, however had to hire consultants to complete the task.

However, from what I understand of the workflow, here is the process:

1) Create a branch to break the flow to each approval

2) Set if statement before approval to check if approval required for specific approver

3) Create approval record if required

4) Run script checking approvals

5) Tally approvals and send notification if approved, however, if any one of rejected, then send notification of approval with exceptions( some approved and some rejected)

6) If all rejected, send notification of rejection

I have included a screen shot of the partial workflow for reference.

Hope this helps!

[luba_bohad]

Thanks a lot Wade! This helped me solve my issue