• 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 nopanel true

  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.

• 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 nopanel true

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

Input Data Components

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

  Insert excerpt
  _driving_connection _driving_connection nopanel true

  's.
• Data flows from the

  Insert excerpt
  _driving_output_connection_point _driving_output_connection_point nopanel true

   to the

  Insert excerpt
  _driving_input_connection_point _driving_input_connection_point nopanel true

  .
• Has attributes which can be mapped to any 

  Insert excerpt
  _driving_input_connection_point _driving_input_connection_point nopanel true

   only.

Output Data Components

• A data receiver. Data is received from 

  Insert excerpt
  _driving_connection _driving_connection nopanel true

  's.
• Has attributes which can be mapped to any

  Insert excerpt
  _driving_output_connection_point _driving_output_connection_point nopanel true

   only.

• Provides lookup data to the actionflow using 

  Insert excerpt
  _request_connection _request_connection nopanel true

  's.
• Any node with a 

  Insert excerpt
  _request_input_connection_point _request_input_connection_point nopanel true

   can perform a lookup to a node with a 

  Insert excerpt
  _request_output_connection_point _request_output_connection_point nopanel true

  .
• 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 nopanel true

     to the 

    Insert excerpt
    _request_output_connection_point _request_output_connection_point nopanel true

    .
  • 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 nopanel true

     to 

    Insert excerpt
    _request_input_connection_point _request_input_connection_point nopanel true

• Performs a lookup to 

  Insert excerpt
  _request_output_connection_point _request_output_connection_point nopanel true

  '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 nopanel true

     to the 

    Insert excerpt
    _request_output_connection_point _request_output_connection_point nopanel true

    .
  • 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 nopanel true

     to 

    Insert excerpt
    _request_input_connection_point _request_input_connection_point nopanel true