Connection Points

Connection points can be inbound or outbound.

Inbound connection points receive data coming into the Actionflow
Outbound connection points return data out of the Actionflow

Inbound Connection Points

There are two types of inbound connection point - Driving and Lookup. Every Actionflow must have only one driving input, which causes the Actionflow to run.

Driving connection: records are pushed into the Actionflow one by one
Lookup connection: all records are pulled as a single dataset but only when the connection is referenced in an expression inside the node. Records are then returned as a single dataset, which may contain multiple records, which are returned as an array

The input/data available to be mapped onto the Connection Points of an Actionflow depends on where the instance of the Actionflow is being called from. For example, if a screen has a grid of data and a card container, an Actionflow on a button which exists on this screen will have access to both sources of data.

To select the source of data, click the input box under Connections.

Connection Point Types

Connection Point	Relevant to	Description
Interface Driving	Input Interface Output Interface	Defines the data attributes the Actionflow is expecting as an input. This data is then used in the Actionflow using Driving connections and remains constant. Defines the data attributes the Actionflow is expected to output. This data can then be mapped back onto components on the screen the action is being used. Each instance of the Actionflow will map in its own set of data onto the expected data inputs/outputs of the connection point.
Interface Lookup	Input Interface Output Interface	Defines the data (and events) the Actionflow is expecting as a requested input. This data is then used in the Actionflow using Lookup connections and remains constant. Each instance of the Actionflow will map in its own set of data onto the expected data inputs.
Driving Output	Input Data Components Calculate View Gateway Actionflow	A data source which drives the Actionflow. Data is pushed through the Actionflow using Driving connections. Data flows from the Driving output connection point to the Driving input connection point. Has attributes which can be mapped to any Driving input connection point only.
Driving Input	Output Data Components Calculate View Gateway Save Open Screen Open URL Run Analysis Phase	A data receiver. Data is received from Driving connections. Has attributes which can be mapped to any Driving output connection point only.
Lookup Output	Input Data Components View	Provides lookup data to the Actionflow using Lookup connections. Any node with a Lookup input connection point can perform a lookup to a node with a Lookup output connection point. Has lookup attributes and data attributes Lookup attributes are used in filtering. They are mapped to lookup attributes on the node performing the lookup. Lookup attributes are referenced in the nodes filter using filter.[attributename] Data is flowing from the Lookup input connection point to the Lookup output connection point. Data attributes are mapped to data attributes on the node performing the lookup. These attributes are the actual data that is being returned from the lookup. Data is flowing from the Lookup output connection point to Lookup input connection point
Lookup Input	Calculate Gateway	Performs a lookup to Lookup output connection points. Has lookup attributes and data attributes Lookup attributes are used in filtering. They are mapped to lookup attributes on the node being looked up to. Attributes that need to be sent to the node in order to filter the data must be added as lookup attributes. Data is flowing from the Lookup input connection point to the Lookup output connection point. Data attributes are mapped to data attributes on the node being looked up to. These attributes are the actual data that is being received from the lookup. Data is flowing from the Lookup output connection point to Lookup input connection point