Versions Compared

Key

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

Insert excerpt
_Banners
_Banners
nameactionflow
nopaneltrue

This page is for application designers who need to configure actionflows. This page explains how to wire together individual actions in an actionflow.

Overview

All actions within an actionflow must be wired together via their connection points. Data flows from the triggering data component or event into the actionflow, and then from each action to the next using connections.   Connection points which are connected appear as blue and are grey when disconnected. There are two types of connections that can be used in actionflows,

Insert excerpt
_driving_connection
_driving_connection
nopaneltrue
 and

Insert excerpt
_request_connection
_request_connection
nopaneltrue
's.

Driving Connections

Driving connections push records through the actionflow one by one.

Records pass from a

  • Insert excerpt
    _driving_output_connection_point
    _driving_output_connection_point
    nopaneltrue
     to a
  • Insert excerpt
    _driving_input_connection_point
    _driving_input_connection_point
    nopaneltrue
Connection points which are connected appear as blue and are grey when disconnected.

Lookup Connections

Lookup connections are used to look up to data for use within the actionflow. Records are returned as a single dataset. This dataset may contain multiple records which are returned as an array.

Records pass from a

  •  
    Insert excerpt
    _request_output_connection_point
    _request_output_connection_point
    nopaneltrue
     to a 
  • .
    Insert excerpt
    _request_input_connection_point
    _request_input_connection_point
    nopaneltrue

Live Search
spaceKey@self
additionalnone
placeholderSearch all help pages
typepage

Panel
borderColor#00374F
titleColorwhite
titleBGColor#00374F
borderStylesolid
titleSections on this page

Table of Contents
maxLevel3
indent12px
stylenone


Adding Wires

To add a wire to an actionflow diagram:

  1. Hover your mouse pointer over an action.
  2. PhixFlow displays a pop-up connector icon.
  3. Click the icon and drag.
  4. Drop the connector
    Option 1: drop onto empty canvas. 
     - PhixFlow opens the pop-up toolbar.  Select which type of action you want to use next.
     - Enter a name for the new action.
    Option 2: drop onto an existing action
  5. PhixFlow opens the Mapping window.
Option 1: Create the next action from the wire

Option 2: Wire to an existing action

Mapping Connection Points

Instance inputs connect to the input interface in order to pass data to the Actionflow. Attributes are mapped via these connections to use in the actionflow using the mapping window.

  1. Data selection
    This option appears when connecting a multi-record data bound component such as a grid or a card component. The user can define what data to bring into the actionflow. The options include
    • Selected
      The user selected records on the grid or card component
    • Edited
      All records the user edits 
    • Page
      The entire page of the grid, card component or form.
  2. Mapping options
    Contains buttons to quickly map attributes from the source to target and to clear any mappings already present.
  3. Output connection point
    Displays the source output connection point details in the form object name > output connection point name
  4. Output connection point attributes
    Displays the attributes available from the output connection point. These could be from a variety of nodes depending if the source is a pass through node. The source output connection point is displayed in the source column. Attributes can be created here on some nodes using 

    Insert excerpt
    _add
    _add
    nopaneltrue
    .

    Note

    Pass through means that any attributes that are not directly mapped to a node, but are connected via a driving or lookup connection, can be used in the mapping of subsequent nodes.


  5. Mappings
    The arrows represent which source attributes are mapped to which target attributes. Target attributes can only be mapped to one source attribute. Source attributes can be mapped to multiple target attributes.
  6. Input connection point
    Displays the target output connection point details in the form object name > input connection point name. 
  7. Input connection point attributes
    Displays the attributes available from the input connection point. These attributes can be created in multiple ways
    • Using 
      Insert excerpt
      _add
      _add
      nopaneltrue
    • Dragging attributes from the source output connection point attributes onto the grid. This creates input connection point attributes and maps them automatically.



  8. Confirmation Buttons
    Closes the popup once mapping has been completed by the user.

Example

The steps to create a mapping between a data input and an interface connection point are outlined below:

  1. Drag from the input (event or data) to the desired interface connection point. (Driving or request)
  2. PhixFlow then opens the mapping window.
  3. Drag the attributes from the Input Connection (Left) onto the Connection Point (Right)
    1. Ensure the type of data is the same i.e. we cannot map a text field onto a date field as they are not compatible.
  4. Create Target Attributes (Optional): drag an attribute on the left to the white space on the right, this will automatically create an attribute of the same name and type.
  5. Confirm the mapping. Now the "Output Connector" will be blue to indicate it has been mapped .
  6. Repeat these steps for any additional mappings required.