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 displays the available action nodes.

Action nodes can be dragged from the toolbar onto the actionflow canvas. 

Clicking certain action nodes in the toolbar displays the following items in the Repository:

• Click  Open Screen in the toolbar to display the list of available  Screens in the Repository. These can be dragged onto the actionflow canvas to create an  Open Screen node.

• Click   View,  Save or  Run Analysis in the toolbar to display the list of available  Tables in the Repository. These can be dragged onto the actionflow canvas to create a Save, View or Analysis node.
  
  

The action nodes have connections, which are blue when connected and grey when not connected, see Wiring Actionflows. Action nodes have

• Input connections, where data is passed into the node
• Output connections, which pass data to the next node.

Usually, connections are  Driving connection. These pass data through to the next action node. Some action nodes can have   Lookup connection, which act like a lookup. These send out a request for data, which is returned to the action node data. The table below shows the types of connections available on an action node.

Nodes must be connected sequentially starting from the  Driving interface connection point. Records will then pass through each node and be manipulated accordingly.

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	Description	How it runs	Available Connections
Actionflow See Actionflow Node	Embeds an actionflow within the current actionflow.	Once per record	Driving connection
Open Screen See Open Screen Node	Add an action to open a specified screen. If the specified screen contains a start phase button the node can then be connected to a start phase node. The buttons can be mapped to each output of the node to trigger different pathways depending on what the user clicks. For example, this method is used if the process requires confirmation by the user. A confirmation screen can appear with a message 'Are you sure?' with two options Yes - the actionflow continues to the yes output. No - the actionflow stops	Once per flow	Driving connection
View See View Node	Add a node for a data view. The actionflow uses views for additional data to use when processing records.	Once per record	Driving connection  Lookup connection
Calculate See Calculate Node Properties	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.	Once per record	Driving connection
Gateway See Gateway Node	Add a node to specify decision logic. Gateways control the route that records take as they flow through the actionflow.	Once per record	Driving connection  Lookup connection
Open URL See Open URL Node	Add an action to open a specified URL.	Once per flow	Driving connection
Save See Save Node	Add a node to save the specified records to their table.	Once per record	Driving connection
Run Analysis See Analysis Node	Runs analysis on the specified tables.	Once per record	Driving connection
HTTP See HTTP Node	Performs an HTTP request.	Once per record	Driving connection
Email See Email Node	Sends an Email to specified recipients.	Once per record	Driving connection
JSON See JSON Node	Handles JSON data and returns record objects as defined by the configuration.	Once per record	Driving connection
Loop Node See Loop Nodes	Facilitates the ability to loop within an actionflow for tasks such as polling or paging through results.	Once per record	Driving connection
Start Phase See Phase Node	Starts the phase specified by the user on the node. To add a phase node there must be more than one phase in the actionflow.	Once per flow	Driving connection