Insert excerpt |
---|
| _Banners |
---|
| _Banners |
---|
name | actionflow |
---|
nopanel | true |
---|
|
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
...
...
available action nodes that
...
...
be dragged onto the actionflow canvas.
...
Image Added
Actions can be added to actionflows in
...
...
- Dragging actions directly from
...
...
Image Added
- 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.
...
Image Added 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
...
...
...
...
...
...
Image Added
The action nodes have connections, which are blue when connected and grey when not connected, see Wiring Actionflows
...
...
...
- 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 ...
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.
...
...
Available Connections |
---|
Insert excerpt |
---|
| _action_actionflow |
---|
| _action_actionflow |
---|
nopanel | true |
---|
|
|
...
Embeds an actionflow within the current actionflow. | |
...
...
...
...
...
...
| 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 |
---|
| _action_view |
---|
| _action_view |
---|
nopanel | true |
---|
|
see View Node | Add a node for a data view. The actionflow uses views for additional data to use when processing |
...
...
...
...
...
...
...
...
...
|
Insert excerpt |
---|
| _action_calculate |
---|
| _action_calculate |
---|
nopanel | true |
---|
| see Calculate |
...
| 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. | |
...
...
...
...
...
...
| Add a node to specify decision logic. Gateways control the route that records take as they flow through the actionflow. | |
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
save the specified records to their table. | |
...
...
...
...
...
...
| Runs analysis on the specified tables. | |
...
...
...
...
...
...
...
See HTTP Node | Performs an HTTP request. | Insert excerpt |
---|
| _driving_connection |
---|
| _driving_connection |
---|
nopanel | true |
---|
|
|
|
...
...
...
...
Sends an Email to specified recipients. | |
...
...
...
...
...
...
...
See JSON Node | Handles JSON data and returns record objects as defined by the configuration. | |
...
...
...
...
...
...
...
| Facilitates the ability to loop within an actionflow for tasks such as polling or paging through results. | |
...
...
...
...
...
action_phase | name | start |
---|
nopanel | true |
---|
|
see Phase Node | Starts the phase specified by the user on the node. | |
...
...
...
...
What's next?
For details about the properties for the action nodes and their connections, see:
...
Insert excerpt |
---|
| _structured_data |
---|
| _structured_data |
---|
nopanel | true |
---|
|