Workflow - Multiple Approvers Who All Must Complete Review

Question

I am trying to build a workflow that tracks approval of a document by multiple parties with a workflow state transition that does not occur until all assigned reviewers have approved or rejected a document. 
 For example, I would like to create an approval that looks like the workflow below. Unless I'm missing something, the OOB configuration will trigger a state transition only when all assigned reviewers have approved an assignment or when only 1 reviewer has rejected an assignment. If one reviewer rejects an assignment, the assignment disappears from the other reviewers queue. 
 Is there a way to make this workflow without needing a Reviewer 1, Reviewer 2, Reviewer 3... Reviewer n property on the metadata card? 
 Thanks!!

Joonas Linkola · Answer

Thanks, got it now. I think you need to create a separate assignment for each approver to do this. If the issue you are struggling with is that there can be 1 &ndash; N approvers, it might make sense to create the assignments programmatically: you would have one multi-select Reviewers property and when the document moves to the Submit for Approval state, your script/code would create an assignment for each user in that list (instead of using the built-in workflow actions for creating the assignments).

Joonas Linkola · Answer

On second thought I don't think my suggestion would work after all: if even one of those reviewers would reject their own assignment, the object would move to the next step if an automatic state transition was configured for the rejection case. 
 Here's a new attempt: 
 - Create one separate assignment using the built-in workflow state action, picking up the reviewers from the Reviewers multi-select property (if it's okay that the comments are collected to the same assignment) 
 - Do NOT use the normal automatic state transition option for approved/rejected assignments but instead the option "Trigger the state transition once the conditions in a user-defined script are fulfilled" 
 - Script the logic for moving the object forward in the workflow when all reviewers have either approved or rejected the assignment 
 Sorry for the confusion and I hope that makes sense

Joonas Linkola · Answer

You are correct, the built-in behavior for group assignments is that if one assignee rejects, then the whole assignment is immediately rejected. 
 I'm just wondering why this wouldn't work in your case. Looking at your workflow diagram, the document will return to Draft state if all approvers didn't approve &ndash; couldn't you just return there immediately after one approver rejects? This would save the other assignees who hadn't yet had time to review the document some work since the assignment disappears from their task list. Or what is the exact use case and requirement here, perhaps I'm missing something?

Workflow - Multiple Approvers Who All Must Complete Review

Top Replies