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 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 displays the available action nodes that can be dragged onto the actionflow canvas.

Actions can be added to actionflows in 2 ways:

  1. Dragging actions directly from the toolbar




  2. Dragging the following items from the repository using
    • Insert excerpt
      _screen_list
      _screen_list
      nopaneltrue

      Will create an 
      Insert excerpt
      _action_screen
      _action_screen
      nopaneltrue
       node.

    • Insert excerpt
      _table_list
      _table_list
      nopaneltrue

      Will ask the user if they would like to create a 
      Insert excerpt
      _action_save
      _action_save
      nopaneltrue
       node or 
      Insert excerpt
      _action_view
      _action_view
      nopaneltrue
       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 

Insert excerpt
_driving_connection
_driving_connection
nopaneltrue
. These pass data through to the next action node. Some action nodes can have  
Insert excerpt
_request_connection
_request_connection
nopaneltrue
, 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 

Insert excerpt
_driving_interface_connection_point
_driving_interface_connection_point
nopaneltrue
. 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.

IconDescriptionAvailable Connections         
Insert excerpt
_action_actionflow
_action_actionflow
nopaneltrue
Embeds an actionflow within the current actionflow.

Insert excerpt
_driving_connection
_driving_connection
nopaneltrue

Insert excerpt
_action_screen
_action_screen
nopaneltrue

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

Insert excerpt
_driving_connection
_driving_connection
nopaneltrue

Insert excerpt
_action_view
_action_view
nopaneltrue

see View Node
Add a node for a data view. The actionflow uses views for additional data to use when processing records.

Insert excerpt
_driving_connection
_driving_connection
nopaneltrue

Insert excerpt
_request_connection
_request_connection
nopaneltrue

Insert excerpt
_action_calculate
_action_calculate
nopaneltrue

see Calculate 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.

Insert excerpt
_driving_connection
_driving_connection
nopaneltrue

Insert excerpt
_action_gateway
_action_gateway
nopaneltrue

see Gateway Node

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

Insert excerpt
_driving_connection
_driving_connection
nopaneltrue

Insert excerpt
_request_connection
_request_connection
nopaneltrue

Insert excerpt
_action_url
_action_url
nopaneltrue

see Open URL Node

Add an action to open a specified URL.
Insert excerpt
_driving_connection
_driving_connection
nopaneltrue

Insert excerpt
_action_save
_action_save
nopaneltrue

see Save Node

Add a node to save the specified records to their table.

Insert excerpt
_driving_connection
_driving_connection
nopaneltrue

Insert excerpt
_action_analysis
_action_analysis
nopaneltrue

see Analysis Node

Runs analysis on the specified tables.

Insert excerpt
_driving_connection
_driving_connection
nopaneltrue

Insert excerpt
_action_http
_action_http
nopaneltrue

See HTTP Action

Performs an HTTP request.
Insert excerpt
_driving_connection
_driving_connection
nopaneltrue

Insert excerpt
_action_email
_action_email
nopaneltrue

See Email Action

Sends an Email to specified recipients. 
Insert excerpt
_driving_connection
_driving_connection
nopaneltrue

Insert excerpt
_action_json
_action_json
nopaneltrue

See JSON Action

Handles JSON data and returns record objects as defined by the configuration. 
Insert excerpt
_driving_connection
_driving_connection
nopaneltrue

Insert excerpt
_action_phase
_action_phase
namestart
nopaneltrue

see Phase Node

Starts the phase specified by the user on the node.
Insert excerpt
_driving_connection
_driving_connection
nopaneltrue

Insert excerpt
_structured_data
_structured_data
nopaneltrue