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  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, it's parent name is shown here. See the Common Properties page, Parent Details section for more details.

Basic Settings

FieldDescription
NameEnter the name for the action node.
Show in the Repository

An application can have many actionflows, and an individual actionflow can have many nodes. This can lead to many items being listed under Actionflow in the repository. Use this option to omit the node from the repository.

 Tick to display this node in the repository.

 Untick to omit this node from the repository.

Exclusive

Control whether or not a record can go through more than one output. 

 Tick to make a record go through the first connection point where the condition is met.

 Untick to make a record go through any connection point where the condition is met.

Input Connection Points

This section has a toolbar with standard buttonsGateway 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.

Output Connection Points

This section has a toolbar with standard buttonsThe grid contains a list of all output connection points.

  • To add a new output path, in the section toolbar click  Add New to open a new output path and set the expression; see Output Connection Points.
  • 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  Delete.

Description

We recommend that you always enter a description to explain the purpose of this item.

 Audit Tab

Audit Summary

See the Common Properties page, Audit Summary section.


Sections on this page

Learn More

For links to all pages in this topic, see Understanding Actionflows


Terminology changes in progress

As part of the redesign of PhixFlow, we are changing the following terms:

dashboard → screen   
stream → table
stream attributes → attributes
stream item → record
stream set → recordset
stream view → view
stream item action → record-action 
stream action → table-action
driver class → database driver