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 21 Next »

This page is for application designers who want to define a process using a workflow diagram, and then connect elements of the diagram to PhixFlow dashboards and actions in an application. This page describes properties

Overview

An actionflow diagram is made up of a series of nodes. Each node represents a specific action. By configuring different actions and wiring them together you can create complex functionality. This section describes the properties of the different action nodes. This page introduces the following nodes and how to connect them:

Adding Action Nodes

The toolbar includes the following action nodes that you can drag onto the actionflow canvas.

 

Actions can be added to actionflows in 3 ways:

  1. Drag actions from the create section in the toolbar


  2. From existing action nodes
    Users can create new actions from connections from existing actions.


  3. Dragging the following items from the repository using
    •  List Screens
      Will create an  Open Screen node.

    •  List Tables
      Will ask the user if they would like to create a  Save Records node, 
      Error rendering macro 'excerpt-include' : No link could be created for '_action_view_driving'.
       node or 
      Error rendering macro 'excerpt-include' : No link could be created for '_action_view_request'.
       node.




    •  List Actionflows
      Will create an  Actionflow node. Doesn't do this yet

Connection Points

Everything in an actionflow is connected using connection points. They are blue when connected and grey when not connected. Find all the possible connection points below.

Icon

Connection PointRelevant toDescription

Interface Driving Connection Point

Input Interface

Output Interface

  • Defines the data attributes the actionflow is expecting as an input. This data is then used in the Actionflow using  Driving connections 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 Request Connection Point

Input Interface

Output Interface

  • Defines the data (and events) the actionflow is expecting as an requested input. This data is then used in the actionflow using  Lookup connections and remains constant.
  • Each instance of the actionflow will map in its own set of data onto the expected data inputs.
Driving Output Connection Point

Input Data Components

 Calculate

Error rendering macro 'excerpt-include' : No link could be created for '_action_view_driving'.

 Gateway

 Actionflow

  • A data source which drives the actionflow. Data is pushed through the actionflow using  Driving connection's.
  • Data flows from the  Driving output connection point to the  Driving input connection point.
  • Has attributes which can be mapped to any  Driving input connection point only.

Driving Input Connection Point

Output Data Components

 Calculate

Error rendering macro 'excerpt-include' : No link could be created for '_action_view_driving'.

 Gateway

 Save Records

 Open Screen

 Open URL

 Run Analysis

 Gateway

  • A data receiver. Data is received from  Driving connection's.
  • Has attributes which can be mapped to any  Driving output connection point only.
Request Output Connection Point

Input Data Components

Error rendering macro 'excerpt-include' : No link could be created for '_action_view_request'.

  • Provides lookup data to the actionflow using  Lookup connection's.
  • Any node with a  Lookup input connection point can perform a lookup to a node with a  Lookup output connection point.
  • 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  Lookup input connection point to the  Lookup output connection point.
    • 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  Lookup output connection point to  Lookup input connection point
Request Input Connection Point

 Calculate

 Gateway

  • Performs a lookup to  Lookup output connection point'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  Lookup input connection point to the  Lookup output connection point.
    • 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  Lookup output connection point to  Lookup input connection point

Action Nodes

IconDescriptionConnection Points
Create

 Actionflow

Add another complete actionflow as a node within this actionflow.  This is useful to reuse existing actionflows, or to refactor a complex workflow by moving part of the logic to its own node.

 Driving input connection point

 Driving output connection point

 Lookup input connection point

screen Screen

Add an action to open a specified dashboard (screen). Only use this action as the final node in an actionflow or branch of it. 

 Driving input connection point
Error rendering macro 'excerpt-include' : No link could be created for '_action_view_driving'.


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

 Driving input connection point

 Driving output connection point


Error rendering macro 'excerpt-include' : No link could be created for '_action_view_request'.
Add a node for a data view. The actionflow uses views to look-up to additional data to use when processing stream-items. Lookup output connection point

 Calculate

Add an action to manipulate the data that is passed to the calculate action. In the calculate action, write an expression using one or more of the 115+ functions available in PhixFlow.

 Driving input connection point

 Driving output connection point

 Lookup input connection point

 Delete Records

Add an action to deletes the specified stream-items passed to the node.

 Driving input connection point
 Gateway

Add a node to specify decision logic. Gateways control the route that stream-items take as they flow through the actionflow.

 Driving input connection point

 Driving output connection point

 Lookup input connection point

 Save

Add a node to saves the specified stream-items to their stream.

 Driving input connection point
 Open URLAdd an action to open a specified URL. Driving input connection point
 Run AnalysisAdd tables to run analysis.

 Driving input connection point

 Driving output connection point

Taptbc

 Driving input connection point

 Driving output connection point

For more detail of each actionflow node, see below.


What's next?


  • No labels