cancel
Showing results for 
Search instead for 
Did you mean: 
kalsup
Nintex Newbie

Weighted Approvals

Has anyone ever done a workflow where a task is assigned to multiple people with the possibility of multiple outcomes and the least of those wins. (weighted outcome)

For example I need to send a task to 3 people. They could answer Approved, Conditional Approved or Not Approved. I need the least of those to take over the status. 

I cannot use the majority wins cause it needs to be the lowest approval level/value that wins. 

So for example:

User A= Approved

User B= Approved

User C= Conditional Approval

Overall Status = Conditional Approval

User A= Approved

User B= Not Approved

User C= Conditional Approval

Overall Status = Not Approved

User A= Approved

User B= Not Approved

User C= Not Approved

Overall Status = Not Approved

Anyone have any idea on how to go about this?

0 Kudos
Reply
4 Replies
emha
Nintex Newbie

Re: Weighted Approvals

does all the assignee have to respond and then you decide on the least outcome?

or once the least possible outcome is received overall approval is stopped/cancelled and assignees that did not responded yet need not to respond anymore?

as well, what environment are you on? - that might have impact on solution design.

0 Kudos
Reply
kalsup
Nintex Newbie

Re: Weighted Approvals

Yes all users must respond prior to deciding outcome. 

Also we are on nintex 2016 on prem.

0 Kudos
Reply
emha
Nintex Newbie

Re: Weighted Approvals

0 Kudos
Reply
greenawayr
Nintex Newbie

Re: Weighted Approvals

I think you need to do something a little more manual here.

We did something similar where we used a request review action, sent it to all the approvers and all had to respond. In the task list we created a choice column that we placed on the task form, then, once all the approvers had responded we queried the task list for the tasks related to the item and then evaluated the values of choice column we had added to our task.

In your case, you could use a parallel branch and query the list for tasks related to that item and where the outcome is A in the first branch, B in the second branch and so forth. Then do a collection operation count on the values in each of the collections and that should tell you how many of each outcome you have and then the workflow can behave accordingly.

0 Kudos
Reply