This page is for application designers who want to define a process using an actionflow diagram. It introduces the action nodes that make up an actionflow.

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.

For information about connecting actionflow nodes together, see Wiring Actionflows.

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   View node.
     
     
     
     
     
   •  List Actionflows
     Will create an  Actionflow node. Doesn't do this yet

The action nodes have connection points, that are blue when connected and grey when not connected, see Wiring Actionflows and Connection Points.  All types of action node can have a  Driving connection which passed data through to the next action node. Some action nodes can also  have a  Lookup connection, which acts like a lookup, sending out a request for data which is returned to the action node data. The table below shows which action nodes can have a request connection.

Types of Action Node

The following table summarises the purpose of each type of action node, with a link to the reference page for the node.

Icon	More Detail	Description	Request Connection
Actionflow	Creating Actionflows	Add another complete actionflow as a node within this actionflow.  This is useful to reuse existing actionflows, or to refactor a complex workflow by	Yes
Screen	Open Screen Node	Add an action to open a specified dashboard (screen). Only use this action as the final node in an actionflow or branch of it.
View	View Node	Add a node for a data view. The actionflow uses views for additional data to use when processing stream-items.	Yes
Calculate	Calculate Action Node	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.	Yes
Delete Records		Add an action to deletes the specified stream-items passed to the node.
Gateway	Gateway Node	Add a node to specify decision logic. Gateways control the route that stream-items take as they flow through the actionflow.	Yes
Save	Save Node	Add a node to saves the specified stream-items to their stream.
Open URL	Open URL Node	Add an action to open a specified URL.
Run Analysis	Analysis Node	Add tables to run analysis.

What's next?

For details about the properties for the action nodes and their connections, see: