Connection Points 

Connection points are where 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  Instances button in the Settings above the canvas. 

The different types of connection point are: 

• Inputs receive data into the Actionflow, 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

Inputs and Lookups

•  Input: records are pushed into the Actionflow one by one
  • Every Actionflow must have at least one  Input which causes the Actionflow to run
•  Lookup: 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 the button is moved IF YOURE IN A GRID YOU only see that data, if you are in a card container you only see that data. 

To discuss - not seeing this behaviour on my app. See screen CompaniesTestData

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