Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

Connection Points 

Connection points are the point at which data is passed into and out of an Actionflow. It is this point that creates a separation between the incoming or outgoing data and the Actionflow itself that allows Actionflows to be reusable. For example, an 'Address Cleanser' Actionflow that takes in a single line of unstructured data from an Input Connection Point, then returns a structured address to an Output Connection Point. This Actionflow can be reused across the application to pass in and receive address data.


The different types of connection point are: 

  • Inputs receive records into the Actionflow one-by-one
  • Lookups retrieve data when called, passing in blocks of data as a single dataset (array) 
  • Outputs return data out of the Actionflow

Inputs and Lookups

  •  Inputrecords are pushed into the Actionflow one by one
    • Every Actionflow must have only one  Input which causes the Actionflow to run. 
  •  Lookupall 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 (array), which may contain multiple records

The datasources 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. 

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

Ensure the Output Connection Point is connected if the Actionflow needs to return data.


  • No labels