Insert excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
|
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:
...
- 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
node.Insert excerpt _action_screen _action_screen nopanel true Insert excerpt _table_list _table_list nopanel true
Will ask the user if they would like to create a
node orInsert excerpt _action_save _action_save nopanel true
node.Insert excerpt _action_view _action_view nopanel true
...
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 | ||||||
---|---|---|---|---|---|---|
|
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
Nodes must be connected sequentially starting from the
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
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 | ||
---|---|---|---|---|
|
...
Add another complete actionflow as a node within this actionflow. This is useful to reuse existing actionflows, or to refactor a complex workflow by
...
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 a confirmation by the user. A confirmation screen can appear with a message 'Are you sure?' with two options
|
| ||||||||
see View Node | Add a node for a data view. The actionflow uses views for additional data to use when processing |
...
records. |
| ||||||||||||||||
...
...
. |
| ||||||||
Add a node to specify decision logic. Gateways control the route |
...
that records take as they flow through the actionflow. |
| ||||||||||||||||
...
Add a node to saves the specified |
...
records to their |
...
table. |
| |||||||||||||||||
see Open URL Node | Add an action to open a specified URL. |
| ||||||||||||||||
Add tables to run analysis. |
|
...
What's next?
For details about the properties for the action nodes and their connections, see:
...
see Phase Node | Starts the phase specified by the user on the node. |
| ||||||||||||||||||
See HTTP Action | Performs a HTTP request. |
|
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|