| Version | Date | Notes | By |
|---|---|---|---|
| 1.0 | 2020-11-13 | Initial release | ROB |
In WeFlow™ scripting system exit components are contextual, that is to say, depending on the bpmn object the script is attached to, the available exit components may change.
Like it's entry counterpart, one case variable component per root variable is made available. While the entry case value exposes the attributes for use by the script, the exit case variable accepts attribute connections and overrites any connected attribute with the value sent, and saves that variable.

This component forcefully appends a new attribute (and the value the previous component outputed) to a variable instance. This works even if that attribute is not a part of the variable definition that generated that variable instance.

This component creates new instances of a sub variable and imediately appends it to a root variable. The input sockets provide the attribute values for the sub variable's attributes. This component can serve as the endcap of a multiple variable flow process.

This component is the only exit for gateway flow scripts. Every input socket represents one of the next bpmn objects connected to by the gateway and accepts a boolean value. If the boolean value passed in is true, then that exit one of the exits that the case will flow through next (in an exlusive gateway, the first exit to evaluate to true, will be the only one picked, the exits are evaluated one at a time from top to bottom).
You may also select a default exit, that is the exit picked if none of the input sockets evaluate to true.
