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.
Image Removed
Image Added
Actions can be added to actionflows in 2 ways:
- Dragging actions directly from the toolbar
- Dragging the following items from the repository using
| Insert excerpt |
|---|
| _screen_list |
|---|
| _screen_list |
|---|
| nopanel | true |
|---|
|
Will create an | Insert excerpt |
|---|
| _action_screen |
|---|
| _action_screen |
|---|
| nopanel | true |
|---|
|
node.
| Insert excerpt |
|---|
| _table_list |
|---|
| _table_list |
|---|
| nopanel | true |
|---|
|
Will ask the user if they would like to create a | Insert excerpt |
|---|
| _action_save |
|---|
| _action_save |
|---|
| nopanel | true |
|---|
|
node or | Insert excerpt |
|---|
| _action_view |
|---|
| _action_view |
|---|
| nopanel | true |
|---|
|
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 |
|---|
| nopanel | true |
|---|
|
. These pass data through to the next action node.
Some action nodes can have | Insert excerpt |
|---|
| _request_connection |
|---|
| _request_connection |
|---|
| nopanel | true |
|---|
|
, 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 connections available on an action node.Nodes must be connected sequentially starting from the
| Insert excerpt |
|---|
| _driving_interface_connection_point |
|---|
| _driving_interface_connection_point |
|---|
| nopanel | true |
|---|
|
. 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 | Available Connections |
|---|
| Insert excerpt |
|---|
| _action_actionflow |
|---|
| _action_actionflow |
|---|
| nopanel | true |
|---|
|
| Embeds an actionflow within the current actionflow. | | Insert excerpt |
|---|
| _driving_connection |
|---|
| _driving_connection |
|---|
| nopanel | true |
|---|
|
|
| Insert excerpt |
|---|
| _action_screen |
|---|
| _action_screen |
|---|
| nopanel | true |
|---|
|
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 |