Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »

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 the actions within an actionflow must be wired together via their connection points. The data flows from the triggering component or event, into the actionflow and then from each action to the next using  Driving connections.

 Lookup connection's are used to look up to data for use within the actionflow.

Each action node in an actionflow has different valid connections indicated by the connection points available on the nodes. There are 4 possible connection points:

  •  Driving input connection point
  •  Driving output connection point
  •  Lookup input connection point
  •  Lookup output connection point

 Driving connection's can only connect to driving connection points, from a

  •   Driving output connection point to a
  •   Driving input connection point.

 Lookup connection's can only connect to request connection points, from a

  •   Lookup output connection point to a 
  •  Lookup input connection point.

Connection points are blue when connected and grey when not connected.

Todo-Anthony  I've started this but more details is needed. Connecting wires seems to be from the action and the output connector is automatically used. I don't know how to make it connect via the lookup.

Sections on this page

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.
  5. Mappings
  6. Input connection point
  7. Input connection point attributes
  8. Confirmation Buttons

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.





  • No labels