Question

LF Forms workflow design question - branching based on any previous user task output.

Forms

Updated October 5, 2022

asked on October 5, 2022

Good morning,

I don't think the subject of this question really captures what I am after, but here goes.

I'm trying to build a LF Forms workflow that will branch to a given path if any of a previous branched task has exited via a given action button.

This is best expained / described in my mock up diagram below.

Firstly, am I overthinking this? Is there a simpler method?
Secondly, is this actually possible?

If anyone can help point me in the right direction I would be very grateful.

Regards,

Richard.

0 0

Answer

SELECTED ANSWER

replied on October 5, 2022

Because TASK 1, TASK 2, and TASK 3 all come from an exclusive Gateway, only one of them will ever be active.
Which means, once you get to Exclusive Gateway (1) you can have it check if the Last User Action = EXTRA (/dataset/_fs_action="EXTRA") and it will work regardless of which one of the three forms had been used.
This would be a different story is TASK 1, TASK 2, and TASK 3 came from an Inclusive Gateway and thus more than one of them could be active at a time.

0 0

Replies

replied on October 5, 2022

Hi Matthew,

I see. I think the first part of my workflow is "wrong", and that your description of a "different sotry" is what I am trying to achieve.

Yes - my first merging gateway should be Inclusive.

How would I go about matching ANY of the first 3 tasks?

Thank you,

Richard.

0 0

replied on October 5, 2022

Unfortunately, the Forms routing only has variables for "Last Action" and "Last User Action", so you wouldn't be able to do it in a simple manner.

One idea - you could have a hidden field on your form that is populated either via Javascript at the time that the EXTRA button is hit - or populated via Workflow, since workflow can see the whole history of actions on the Forms instance, it would just need to check all of them for the value of EXTRA and if found, update the hidden field in Forms. Then you would have your Forms Gateway check for the value in the hidden field.

0 0

You are not allowed to follow up in this post.

Question

Question

LF Forms workflow design question - branching based on any previous user task output.

Answer

Replies

Sign in to reply to this post.