Versions Compared

Key

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

Insert excerpt
_Banners
_Banners
nameactionflow
nopaneltrue

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

Insert excerpt
_actionflow_instances
_actionflow_instances
nopaneltrue
 button in the Settings above the canvas

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 ALSO CAN RECIEVE ON CLICK OR A SCHEDULE TASK
  • Lookups retrieve data, when called, passing in all data as a single recordset (array) 
  • Outputs return data out of the Actionflow

Inputs and Lookups

Insert excerpt
_input
_input
namecaps
nopaneltrue

  • Data Required: where data causes the Actionflow to run records are pushed into the Actionflow one by one ALSO CAN RECIEVE ON CLICK OR A SCHEDULE TASK which cause it to run once.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 (
      Insert excerpt
      _actionflow_on_click
      _actionflow_on_click
      nopaneltrue
      , Double-Click), keyboard presses (On-Enter), or a 
      Insert excerpt
      _taskplan_icon
      _taskplan_icon
      nopaneltrue
       Scheduled Task that causes the Actionflow to run once
  • Every Actionflow must have at least one
    Insert excerpt
    _input
    _input
    namecaps
    nopaneltrue
     which causes the Actionflow to run

Insert excerpt
_lookup
_lookup
nopaneltrue

  • all 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.

Tip

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

DO WE NEED TO ADD HOW TO REMOVE CONNECTION POINTS? AND THE CONSIDERATIONS?

HTML Comment
hiddentrue

Connection Point Types

Icon

Connection PointRelevant toDescription

Interface Driving

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

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

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 

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 

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 

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