So basically, there are a number of approvers, at least 1 and up to 5 (plus the master approver). You want to send an email to all of the original approvers at once to look at the information, and approve or decline it. If at least 3 (in the case of 5 approvers) approve it, the process moves forward and the master approver now is set up to approve. The other 2 approvers receive a "it's already approved by a majority" email.
- Does the number of approvers vary?
- Do you want it parallel (like I laid out) or serial?
- What happens if an approver declines?
- Should the approvers be able to see the status/comments of the other approvers?
- Are you in Office 365 or Sharepoint 2013/2016?
- Do you also use Nintex Forms?
Hi Courtney
Thanks for your answer. To your questions:
- Does the number of approvers vary? Yes
- Do you want it parallel (like I laid out) or serial? parallel
- What happens if an approver declines? Nothing should happen. Everybod should approve or decline first. (I just added a screenshot of the actual workflow)
- Should the approvers be able to see the status/comments of the other approvers? The master approver should see it.
- Are you in Office 365 or Sharepoint 2013/2016? SharePoint 2013
- Do you also use Nintex Forms? No
Oh! I got your requirements backwards; it currently only waits for a majority but you want it to wait for all. In your flexitask, you should have an "Behavior" section, there are options there for when you want to progress. Check out the documentation here: http://help.nintex.com/en-US/nintex2013/help/#Workflow/RootCategory/Actions/Nintex.Workflow.FlexiTask.htm for more info on what each option does!
The Problem is, none of the behaviour matches our requirements. Do you have any idea for a Workaround?
Thanks
Vico
Hmm, check out this thread:
Apparently, there is not a way to wait for all approvers to respond unless you assign individual tasks, which can get tricky when you have a variable number of approvers, but is doable.
what about design like this?
if 5 approvers is your upper bound on number of approvers, you could use parallel action with 5 branches, within each branch assign a task to one of those 5 approvers.
to ensure the task is assigned only to defined approver, you could first check it with run-if.
parallel action ensures, that workflow will not proceed until all the parallel branches and finished, so in your case until all of the 5 approvers respond.
then finally assign task to master approver.
Hi Marian
Thanks for your answer. That could actually really solve my Problem. I'll try it on monday and give you Feedback.
Thanks
Vico
Hi Marian
Thanks for your help. It'sworking...!
Have a nice week.
Vico