Connection Points
Connection points are where data data, or interactions, are passed into and out of an Actionflow. It is the connection points that create a separation between the Actionflow and instance where it is being used which in turn allows Actionflows to be reusable.
For example, an Address Cleanser Actionflow that takes in a single line of unstructured address data from an Input Connection Point, then returns a structured address to an Output Connection Point. This Actionflow can be reused by connecting in different address data. Each combination of connections is referred to as an Instance, that can be viewed by pressing the | Insert excerpt |
|---|
| _actionflow_instances |
|---|
| _actionflow_instances |
|---|
| nopanel | true |
|---|
|
button in the Settings above the canvas.
The different types of connection point are:
- Inputs receive a mouse click (no data), a scheduled task or data into the Actionflow and records are read in one-by-one
- Lookups retrieve data, when called, passing in all data as a single recordset (array)
- Outputs return data out of the Actionflow
| Insert excerpt |
|---|
| _input |
|---|
| _input |
|---|
| name | caps |
|---|
| nopanel | true |
|---|
|
- Data Required: where data causes the Actionflow to run records are pushed into the Actionflow one by one
- Data Not Required: where the Actionflow does not require any data from the screen from which it is initiated, use the event as the input
- An event is triggered by mouse-clicks (
| Insert excerpt |
|---|
| _actionflow_on_click |
|---|
| _actionflow_on_click |
|---|
| nopanel | true |
|---|
|
, Double-Click), keyboard presses (On-Enter), or a | Insert excerpt |
|---|
| _taskplan_icon |
|---|
| _taskplan_icon |
|---|
| nopanel | true |
|---|
|
Scheduled Task that causes the Actionflow to run once
- Every Actionflow must have at least one
| Insert excerpt |
|---|
| _input |
|---|
| _input |
|---|
| name | caps |
|---|
| nopanel | true |
|---|
|
which causes the Actionflow to run
| Insert excerpt |
|---|
| _lookup |
|---|
| _lookup |
|---|
| nopanel | true |
|---|
|
- All records are pulled as a single recordset but only when the connection is referenced in an expression inside the Actionflow
- Records are then returned as a single recordset (array), which may contain multiple records
The data sources available to be mapped into the Connection Point 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. However, if an action is embedded in a grid, this will only have access to the data displayed in the grid.
To select the source of data, click the input box under Connections.
| Tip |
|---|
Ensure the Output Connection Point is mapped if the Actionflow needs to return data. |
Removing Connection Points
To remove a connection point, right-click and select:
| Insert excerpt |
|---|
| _remove |
|---|
| _remove |
|---|
| nopanel | true |
|---|
|
Input: this removes the connection point but retains the mappings within the Actionflow| Insert excerpt |
|---|
| _delete |
|---|
| _delete |
|---|
| nopanel | true |
|---|
|
Connection Point: this deletes the connection point and deletes the mappings
| HTML Comment |
|---|
|
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
| 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 |
|---|
|
|
|
