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
   •  List Screens
     Will create an  Open Screen node.
     
     
   •  List Tables
     Will ask the user if they would like to create a  Save Records node or   View 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 connection 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.