Gateway Node
- Sarah Gibson (Unlicensed)
- Zoe Baldwin
- Anthony George
- Fiona Sargeant (Unlicensed)
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 Gateway node to control the path that data records take as they flow through an actionflow. You can add several output connection points. On the output connection points, you can specify decision logic to control the path of data, record by record.
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.
Property Pane Toolbar
For information about the toolbar options, see the Common Properties page, Toolbars and Controls section.
Properties Tab
Parent Details
If this item is within or belongs to another, its parent name is shown here. See the Parent Details section on the Common Properties page for more details.
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) to make a record go through the first connection point where the condition is met. Exclusive gateways include the visual indicator of their setup: Inclusive Gateway (Multiple Paths) to make a record go through all connection points where the condition is met. Inclusive gateways include the visual indicator of their setup: |
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 Driving input connection point
- multiple Lookup input connection points
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 Add New 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 Delete.
Advanced
Field | Description |
---|---|
Prioritise Throughput Over Ordering | When enabled, records are processed in parallel to optimise performance. This means the order records are processed is nondeterministic. When disabled (default), records are processed in the order they are provided. |
Audit Tab
Audit Summary
See the Common Properties page, Audit Summary section.
Learn More
For links to all pages in this topic, see Understanding Actionflows.