Gateway Node
This page is for application designers who need to configure functionality for components or events. It explains the properties for the gateway node, which is part of an actionflow.
Overview
Use a
Example
Sometimes there is a threshold in your data that affects the way you want to process it. For example, you might want someone to approve orders over £1000, whereas orders below this value can be placed without approval.
The application screen, below, lists the orders pending approval.
The actionflow for this requires a gateway node to capture orders with a value of £1000 or more so that it can send these to the person authorised to approve them.
Basic Settings
Field | Description |
|---|---|
Name | Enter the name of the action node. |
Exclusive | Control whether or not a record can go through more than one output. Exclusive Gateway (Single path)
Inclusive Gateway (Multiple Paths)
|
Description | We recommend that you always enter a description to explain the purpose of this item. |
Rules
Field | Description |
|---|---|
Rule | The expression to be evaluated. If the condition is met, the record will go through the connection point or points (depending on if the gateway is exclusive or inclusive, see above). |
Output | The name of the output connection point. |
Order | The order the rules should be evaluated in. |
Input Connection Points
This section has a toolbar with standard buttons. Gateway nodes can have:
one
multiple
s
The grid contains a list of all input connection points and their type.
To add a new input connection point, in the section toolbar click
to open a new input connection point and set its properties; see Input Connection Points.To edit an existing input connection point, double-click it in the list to open its properties.
To remove an input connection point, select one and in the section toolbar click
.
Advanced
Field | Description |
|---|---|
Prioritise Throughput Over Ordering |
Learn More
For links to all pages in this topic, see Understanding Actionflows.