/
Understanding Connection Points

Understanding Connection Points

May 14, 2025

Connection Points 

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

 button in the Settings above the canvas. 

Two screens use the same actionflow.

One actionflow expects an Area Code to calculate a distance. The screen passes the actionflow a Postcode, this is mapped into the actionflow onto the Area Code attribute using the Input Connection Point mapping.

 

A second screen can reuse the actionflow (this is referred to as an instance) and pass in a Zip Code which is mapped into the actionflow using the Input Connection Point mapping. 

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, which may contain multiple records as an array 

  • Outputs return data out of the Actionflow

Inputs and Lookups

  • 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 (

      , Double-Click), keyboard presses (On-Enter), or a 
       Scheduled Task that causes the Actionflow to run once

  • Every Actionflow must have at least one

     which causes the Actionflow to run

  • Only used 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 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.

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:

  • Clear Connection: this removes the connection point but retains the mappings within the Actionflow

  •  Connection Point: this deletes the connection point and deletes the mappings