Image Added

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

Image Added

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

Image Added

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 request attributes and data attributes
  • Request attributes are used in filtering. They are mapped to request attributes on the node performing the lookup. Request attributes are referenced in the nodes filter using

    req.[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 request attributes and data attributes
  • Request attributes are used in filtering. They are mapped to request 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 request 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

Open screen nodes can be created with or without a screen attached. This is useful if the screen has not been created yet. Open screen nodes which do not have a screen attached appear with a warning symbol to remind users that this still needs to be configured.

Image Added 

Each open screen node has 1 primary input connection point by default called 'in'. Connecting to this connection point simply opens the screen and cannot pass any data to it. Do we still need this?

Once a screen has been attached to the open dashboard node an input connection point for each form on the screen is created. Each input connection point automatically has any data fields on the form (dynamic text or form fields) added as attributes. These attributes can be mapped to and supplied with data.

Each input connection point has the following properties:

• Type
• Open Mode
• Role
• Attributes

Configure the purpose for the screen that will open

• update: opens form fields with the latest data (tnot clear, refresh)
• insert: opens the screen with form fields empty clear, not refresh)
• change: opens form fields with data (not clear, not refresh)

To set the actionflow to close the active dashboard on completion, on the top right of the canvas, tick Close Parent Dashboard.
Image Added

Add a node for a data view. The actionflow uses views to look-up additional data to use when processing stream-items.

Connect a view node to the action node that needs to look-up data via the lookup connection Image Added  icon page. A look-up connection has 2 parameters:

• attribute: the attribute in the view from which you want to look-up data. For example, the view may have the attribute staff_number that you require.
• request attribute: the data returned by the look-up. This maps to an input on the destination point.