Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Insert excerpt
_Banners
_Banners
nameactionflow
nopaneltrue

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:

  • Insert excerpt
    _driving_connection
    _driving_connection
    nopaneltrue
     and
  • Insert excerpt
    _request_connection
    _request_connection
    nopaneltrue

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 Types

Icon

Connection PointRelevant toDescription

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
    Insert excerpt
    _driving_connection
    _driving_connection
    nopaneltrue
    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 an requested input. This data is then used in the actionflow using
    Insert excerpt
    _request_connection
    _request_connection
    nopaneltrue
    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

Insert excerpt
_action_calculate
_action_calculate
nopaneltrue

Insert excerpt
_action_view
_action_view
nopaneltrue

Insert excerpt
_action_gateway
_action_gateway
nopaneltrue

Insert excerpt
_actionflow
_actionflow
nopaneltrue

  • A data source which drives the actionflow. Data is pushed through the actionflow using 
    Insert excerpt
    _driving_connection
    _driving_connection
    nopaneltrue
    's.
  • Data flows from the
    Insert excerpt
    _driving_output_connection_point
    _driving_output_connection_point
    nopaneltrue
     to the
    Insert excerpt
    _driving_input_connection_point
    _driving_input_connection_point
    nopaneltrue
    .
  • Has attributes which can be mapped to any 
    Insert excerpt
    _driving_input_connection_point
    _driving_input_connection_point
    nopaneltrue
     only.

Driving Input Connection Point

Output Data Components

Insert excerpt
_action_calculate
_action_calculate
nopaneltrue

Insert excerpt
_action_view
_action_view
nopaneltrue

Insert excerpt
_action_gateway
_action_gateway
nopaneltrue

Insert excerpt
_action_save
_action_save
nopaneltrue

Insert excerpt
_action_screen
_action_screen
nopaneltrue

Insert excerpt
_action_url
_action_url
nopaneltrue

Insert excerpt
_action_analysis
_action_analysis
nopaneltrue

Insert excerpt
_action_phase
_action_phase
namephase
nopaneltrue

  • A data receiver. Data is received from 
    Insert excerpt
    _driving_connection
    _driving_connection
    nopaneltrue
    's.
  • Has attributes which can be mapped to any
    Insert excerpt
    _driving_output_connection_point
    _driving_output_connection_point
    nopaneltrue
     only.
Lookup Output Connection Point

Input Data Components

Insert excerpt
_action_view
_action_view
nopaneltrue

  • Provides lookup data to the actionflow using 
    Insert excerpt
    _request_connection
    _request_connection
    nopaneltrue
    's.
  • Any node with a 
    Insert excerpt
    _request_input_connection_point
    _request_input_connection_point
    nopaneltrue
     can perform a lookup to a node with a 
    Insert excerpt
    _request_output_connection_point
    _request_output_connection_point
    nopaneltrue
    .
  • 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
      nopaneltrue
       to the 
      Insert excerpt
      _request_output_connection_point
      _request_output_connection_point
      nopaneltrue
      .
    • 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
      nopaneltrue
       to 
      Insert excerpt
      _request_input_connection_point
      _request_input_connection_point
      nopaneltrue
Lookup Input Connection Point

Insert excerpt
_action_calculate
_action_calculate
nopaneltrue

Insert excerpt
_action_gateway
_action_gateway
nopaneltrue

  • Performs a lookup to 
    Insert excerpt
    _request_output_connection_point
    _request_output_connection_point
    nopaneltrue
    '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
      nopaneltrue
       to the 
      Insert excerpt
      _request_output_connection_point
      _request_output_connection_point
      nopaneltrue
      .
    • 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
      nopaneltrue
       to 
      Insert excerpt
      _request_input_connection_point
      _request_input_connection_point
      nopaneltrue