You have been redirected from an outdated version of the article.
Below is the content available on this topic. To view the old article click here.
Decision
The Decision element allows to split execution paths by deciding for a path depending on the given condition elements.
Name |
Description |
Prev |
Accepts a connection from a Next socket |
Condition |
Accepts a connection from a Result socket |
Next If True |
Connects to a node’s Prev socket. Executed when condition is true |
Next If False |
Connects to a node’s Prev socket. Executed when condition is false |
Search results for "Decision"
Comparison
Name | Description |
DataSources | Accepts multiple DataTarget connections. Data that will be compared. |
ValueSource | Accepts DataTarget connection. Value that given data will be checked against. |
Operation | Defines boolean operator to be applied. |
Result | Connects to a logic node DataSource or a Decision Condition |
Decision
The Decision element allows to split execution paths by deciding for a path depending on the given condition elements.
NotEmpty
Name | Description |
DataSources | Accepts multiple DataTarget connections |
Result | Connects to a logic node DataSource or a Decision Condition |
Condition
Name | Description |
DataSource | Accept another element’s DataTarget |
ScriptSource | Accepts another element’s DataTarget . Can be used to dynamically supply a script |
Script | Supplies script given for evaluation. Only used when ScriptSource is not connected |
DataTarget | Connects to a logic node DataSource or a Decision Condition |
ExceptionHandler | Connects to an ExceptionHandler’s HandledNodes socket |
And
Name | Description |
DataSources | Accepts multiple logic node DataTarget connections |
Result | Connects to a logic node DataSource or a Decision Condition |
Or
Name | Description |
DataSources | Accepts multiple logic node DataTarget connections |
Result | Connects to a logic node DataSource or a Decision Condition |
NotNull
Name | Description |
DataSources | Accepts multiple DataTarget connections |
Result | Connects to a logic node DataSource or a Decision Condition |
Not
Name | Description |
DataSources | Accepts multiple logic node DataTarget connections |
Result | Connects to a logic node DataSource or a Decision Condition |
Logic Elements
Logic elements are a special group of components that are used to construct logic expressions used in conjunction with other flow elements. Examples of this are Decision or Filter elements.
Execution Flow
When a flow is called, execution will begin at it’s starting element. In case of no entry point being set or no elements being contained, the flow will simply return a null result. Otherwise the Flow Engine will evaluate the starting element and then proceed with the evaluation of the element connected to the initial element as next element. This continues until there is no more next element available, an error has been thrown or the evaluated element is a Return element, in which case the result of the element’s evaluation will be returned. Although this sums up the general execution flow of a Flow, there are notable exceptions to this in the form of specialized elements. For example a Decision element will branch into two execution paths and choose one based on the connected conditional elements. Likewise, a Loop element will enter a different execution path for each element and finally proceeds with the original next element.
Connection Types
Green connections between elements represent the execution flow. Blue connections between elements represent the Flow of data. Orange connections represent conditional and logic Flows that are used in conjunction with Decision elements. Brown connections represent connections between flow elements and their exception handler element.