Quantcast
Channel: Nintex Connect: Unanswered Threads
Viewing all articles
Browse latest Browse all 2462

Flexi Task 'All must agree on outcome' Clarification

$
0
0

After putzing around for quite some time with the flexi action and it's outcome behavior, I have come to a conclusion that I need to verify, just so I know I'm not going crazy here....  I guess the root of my inquiry here revolves around the purpose of the 'All must agree on outcome' functionality.

Scenario:

You assign a flexi task with two outcomes (Approve and Reject)   you then set that flex task to require that all participants agree on a specific outcome (let's go with Approve.)  So the task is then created with three people and one of them goes in and sets the item to Reject.   This is not the required outcome so the Flexi Task dies and the additional people are not required to provide any additional input.

Issue:

When this happens, the workflow doesn't go down the 'reject' leg of the flexi task, it merely restarts the state in which the task exists thus recreating the task.  Adding the 'other' branch from the advanced options allows you to perform an action on the failed task (like sending an email or switching states) but it would seem to me that the reject branch (or any branch other than the desired outcome) are utterly inaccessible.   So my question is, what's the point in having any outcomes other than the desired one?  When choosing the 'all must agree on outcome' option, you're really left with a binary decision, and the negative side of that binary decision (the 'other' branch)   isn't an option...   Even if everyone agreed that the decision should be to choose the 'Reject' option, because the first person rejected it, the other two don't even get a chance to throw their two cents in becase the task has already died.  So there is no point in adding more than two outcomes to this task(and one of those by default should be 'other) because your actionable decisions are either the desired outcome or everything else.  There is also no point in showing those additional outcomes on the workflow because they are completely inaccessible.(what one would see with the scenario above is a reject leg, an approve leg, and an other leg)

I feel like I'm missing something here and would like to get to the bottom of the intended use of this option within the flexi task so that I can properly use it going forward.


Viewing all articles
Browse latest Browse all 2462

Trending Articles