Insert excerpt

	_Banners
	_Banners
name	actionflow
nopanel	true

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.

Insert excerpt
_driving_connection
_driving_connection
nopanel true
: records are pushed into the Actionflow one by one
Insert excerpt
_request_connection
_request_connection
nopanel true
: 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.

Tip
Make sure you connect to the output connection point if you are returning data.

HTML Comment

hidden	true

Connection Point Types

Icon

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 Insert excerpt
_driving_connection
_driving_connection
nopanel true
s 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
Insert excerpt
_request_connection
_request_connection
nopanel true
s 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

Insert excerpt

	_action_calculate
	_action_calculate
nopanel	true

Insert excerpt

	_action_view
	_action_view
nopanel	true

Insert excerpt

	_action_gateway
	_action_gateway
nopanel	true

Insert excerpt

	_actionflow
	_actionflow
nopanel	true

A data source which drives the Actionflow. Data is pushed through the Actionflow using
Insert excerpt
_driving_connection
_driving_connection
nopanel true
s.
Data flows from the
Insert excerpt
_driving_output_connection_point
_driving_output_connection_point
nopanel true
to the
Insert excerpt
_driving_input_connection_point
_driving_input_connection_point
nopanel true
.
Has attributes which can be mapped to any
Insert excerpt
_driving_input_connection_point
_driving_input_connection_point
nopanel true
only.

Driving Input

Output Data Components

Insert excerpt

	_action_calculate
	_action_calculate
nopanel	true

Insert excerpt

	_action_view
	_action_view
nopanel	true

Insert excerpt

	_action_gateway
	_action_gateway
nopanel	true

Insert excerpt

	_action_save
	_action_save
nopanel	true

Insert excerpt

	_action_screen
	_action_screen
nopanel	true

Insert excerpt

	_action_url
	_action_url
nopanel	true

Insert excerpt

	_action_analysis
	_action_analysis
nopanel	true

Insert excerpt

	_action_phase
	_action_phase
name	phase
nopanel	true

A data receiver. Data is received from
Insert excerpt
_driving_connection
_driving_connection
nopanel true
s.
Has attributes which can be mapped to any
Insert excerpt
_driving_output_connection_point
_driving_output_connection_point
nopanel true
only.

Lookup Output

Input Data Components

Insert excerpt

	_action_view
	_action_view
nopanel	true

Provides lookup data to the Actionflow using
Insert excerpt
_request_connection
_request_connection
nopanel true
s.
Any node with a
Insert excerpt
_request_input_connection_point
_request_input_connection_point
nopanel true
can perform a lookup to a node with a
Insert excerpt
_request_output_connection_point
_request_output_connection_point
nopanel true
.
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
  Insert excerpt
  _request_input_connection_point
  _request_input_connection_point
  nopanel true
  to the
  Insert excerpt
  _request_output_connection_point
  _request_output_connection_point
  nopanel true
  .
- 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
  Insert excerpt
  _request_output_connection_point
  _request_output_connection_point
  nopanel true
  to
  Insert excerpt
  _request_input_connection_point
  _request_input_connection_point
  nopanel true

Lookup Input

Insert excerpt

	_action_calculate
	_action_calculate
nopanel	true

Insert excerpt

	_action_gateway
	_action_gateway
nopanel	true

Performs a lookup to
Insert excerpt
_request_output_connection_point
_request_output_connection_point
nopanel true
s.
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
  Insert excerpt
  _request_input_connection_point
  _request_input_connection_point
  nopanel true
  to the
  Insert excerpt
  _request_output_connection_point
  _request_output_connection_point
  nopanel true
  .
- 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
  Insert excerpt
  _request_output_connection_point
  _request_output_connection_point
  nopanel true
  to
  Insert excerpt
  _request_input_connection_point
  _request_input_connection_point
  nopanel true

Expand

title	Understanding New Terms

We have covered numerous new terms in this chapter. Let's recap on the terms we have used and what they mean.

Inbound Connection Point

Outbound Connection Point

Input Parameters

Output Attributes

Input Data

Pass-through Nodes

Join Nodes

Versions Compared

Old Version 8

New Version 9

Key

Connection Points

Inbound Connection Points

Connection Point Types

Page Comparison

Versions Compared

Old Version 8

New Version 9

Key

Connection Points

Inbound Connection Points

Connection Point Types