/
Understanding Actionflow Node Connections

Understanding Actionflow Node Connections

Jul 10, 2024

 

In an Actionflow, individual actions have connection points to receive data from the previous action. This page explains the type of connection point, and their properties.

Overview

Everything in an Actionflow is connected using connection points. They are blue when connected and grey when not connected. There are two types of connections:

  •  and

For information about the concepts related to wiring Actionflows together using connection points, see Wiring Actionflows. 

For most action nodes, data flow is configured when you map attributes to the input connection points. For gateway nodes, you can also control the data flow by mapping to output connection points. This is because the expressions in a gateway provide the logic for which path the data flows, and different paths may require different data to pass through the gateway.

Connection Point Properties

For information on the options on the 

, see Connection Points.

Connection Point Types

Icon

Connection Point

Relevant to

Description

Icon

Connection Point

Relevant to

Description

Interface Driving Connection Point

Input Interface

Output Interface

  • Defines the data attributes the actionflow is expecting as an input. This data is then used in the Actionflow using

    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 Connection Point

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

    s and remains constant.

  • Each instance of the actionflow will map in its own set of data onto the expected data inputs.

Driving Output Connection Point

Input Data Components

  • A data source which drives the actionflow. Data is pushed through the actionflow using 

    s.

  • Data flows from the

     to the
    .

  • Has attributes which can be mapped to any 

     only.

Driving Input Connection Point

Output Data Components

  • A data receiver. Data is received from 

    s.

  • Has attributes which can be mapped to any

     only.

 

 nodes have the following special properties for their input connections.

Lookup Output Connection Point

Input Data Components

  • Provides lookup data to the actionflow using 

    s.

  • Any node with a 

     can perform a lookup to a node with a 
    .

  • 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 

       to the 
      .

    • 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 

       to 

Lookup Input Connection Point

  • Performs a lookup to 

    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 

       to the 
      .

    • 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 

       to 

Learn More