Three outcomes on a Flexi-Task with multiple approvers

C
Badge +1

Good morning All!

Thanks in advance to all who might have a response for me.  Here's the scenario:

We have a flexi-task going out to two approvers.  There are three possible outcomes--Approve, Reject, and Approve with Exceptions.  Various actions need to complete after each outcome, but that's easy enough.  The trouble comes when trying to utilize the 3rd branch "Approve with Exceptions."

Here are the task specifics:

Both approvers must agree on Approve.

A single rejection will "kill" the other task.

If any one approver selects Approve with Exceptions then the item is approved (comments are logged with the exceptions).

Here is the issue:

With two outcomes the resolution is easy enough.  We have the outcome and outcome achieved in two separate variables, which we evaluate later to perform some post-approval actions.  With the third branch, as we know, the task outcome becomes null and unable to be evaluated.  I tried setting this variable to the desired value AFTER the flexitask, but it seems like that is disallowed.  I also tried assigning numeric values to outcomes, just in case the text values were being mishandled.  Then I tried utilizing the "Other" branch with some logic, but honestly I didn't really see the value so I gave up on that pretty quickly.  Now I'm attempting to store each outcome in a collection and then applying some actions to those returns, but I'm not sure that I'm on the right track.

Does anyone have an example of a working flexi-task with three outcomes and the same approval requirements...or any ideas???

Thanks so much!!1

2 replies

C
Badge +16

Hi Christian Marin​

I would suggest you have two standard outcomes of approve and reject.  I would suggest you edit the flexi task form and add an additional field in there where the approver can detail the exceptions.  that way you can follow the approval branch and store the exceptions at the same time it is responded to - would that work?

C
Badge +1

Hi ‌

Sorry for the delayed reply, haven't been on in a while.  So the issue here was that the team for which this was built wanted a visual representation of the approved with exception outcome, so merely changing a state field to "approved" was not going to work--even if there were exceptions detailed in the comments.

What I wound up doing was this: (and this works for any flexitask with more than two outcomes where one "equates" to another.)  Since "Approved" and "Approved with Exceptions" had identical behaviors I simply stored the outcome of the task in a variable and set that variable to "Approved" when the "Approved with Exceptions" outcome was achieved.

Sounds so easy now that I think about it--hopefully it can help someone out in the future.  I appreciate your input on this one.

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings