This page provides details of the properties for the gateway node, which is part of an actionflow.
Overview
Use a
Insert excerpt |
---|
| _action_gateway |
---|
| _action_gateway |
---|
nopanel | true |
---|
|
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.
In the screenshot below, an application screen 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. todo-sarah Provide screenshot and more details once confirmation and phases have been implemented
Insert excerpt |
---|
| _property_toolbar |
---|
| _property_toolbar |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| _property_tabs |
---|
| _property_tabs |
---|
name | basic-h |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| _parent |
---|
| _parent |
---|
nopanel | true |
---|
|
Basic Settings
Field | Description |
---|
Name | Enter the name for the action node. |
Insert excerpt |
---|
| _actionflow_properties |
---|
| _actionflow_properties |
---|
name | show-name |
---|
nopanel | true |
---|
|
| Insert excerpt |
---|
| _actionflow_properties |
---|
| _actionflow_properties |
---|
name | show-text |
---|
nopanel | true |
---|
|
|
Exclusive | Control whether or not a record can go through more than one output. Insert excerpt |
---|
| _check_box_tick |
---|
| _check_box_tick |
---|
nopanel | true |
---|
|
to make a record go through the first connection point where the condition is met. Insert excerpt |
---|
| _check_box_untick |
---|
| _check_box_untick |
---|
nopanel | true |
---|
|
to make a record go through any connection point where the condition is met. |
This section has a toolbar with standard buttons. The grid contains a list of all input connection points and their type; see Gateway nodes can have:
- one
Insert excerpt |
---|
| _driving_input_connection_point |
---|
| _driving_input_connection_point |
---|
nopanel | true |
---|
|
- multiple
Insert excerpt |
---|
| _request_input_connection_point |
---|
| _request_input_connection_point |
---|
nopanel | true |
---|
|
's
- To add a new input connection point, in the section toolbar click to open a new input connection point and set its properties.
- 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
Insert excerpt |
---|
| _delete |
---|
| _delete |
---|
nopanel | true |
---|
|
.
For input connection point properties, see Input Connection Points.
Output Connection Points
This section has a toolbar with standard buttons. The grid contains a list of all output connection points.
This section has a toolbar with standard buttons. The grid contains a list of output connection points and their expressions.
- To add a new output path, in the section toolbar click to open a new output path and set the expression.
- To edit an existing output path, double-click it in the list to open its properties.
- To remove an output path, select one and in the section toolbar click Image Added Permanently Delete.
see Output Connection Points
Each output connection point has an expression that specifies the logic to control whether or not records flow to the next action node.
For driving output connections, you can refer to an attribute in the expression using the syntax:
Code Block |
---|
connectionpointname.attributename |
If the expression evaluates to true for the record flowing through the node, it will pass out that connection point onto the next node in the sequence. This can be dependent on if the gateway is marked as exclusive, see below.
Gateways can have an unlimited number of output paths.Output paths process data using expressions; see pages in the topic Expressions and PhixScripts.
Stream-items records will only pass through the output paths if the condition set in the expression is met.
Note |
Remember to check if if the gateway has been marked as Exclusive. Records will only pass through the first output path where the condition is met if the gateway is exclusive.
This section has a toolbar with standard buttons. The grid contains a list of output connection points and their expressions.
- To add a new output path, in the section toolbar click to open a new output path and set the expression.
- To edit an existing output path, double-click it in the list to open its properties.
- To remove an output path, select one and in the section toolbar click Permanently Delete.
The expression properties has sections for Parent Details , Audit Summary and the following Basic Settings:
Field | Description |
---|
Name | Enter an expression name. |
Order | Where the gateway action runs and expression for each output path, enter a number to indicate the order in which this expression will be run. Remember that an expression that generates a value should run before an expression that uses the value. The order is especially important if the gateway is marked as exclusive. |
Expression | Enter an expression which evaluates to true or false to determine if stream-items will pass through this connection point. To work in a larger pop-up window, click . See also: |
Insert excerpt |
---|
| _description |
---|
| _description |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| _property_tabs |
---|
| _property_tabs |
---|
name | access-h |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| _access |
---|
| _access |
---|
nopanel | true |
---|
|