...
| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|
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 anInsert excerpt _action_
...
screen _action_
...
node.screen nopanel true
...
todo - How do you specify the different types of gateway
...
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 | ||
|---|---|---|
|
...
|
...
|
...
|
...
|
...
. These pass data through to the next action node
...
. Some action nodes can have Insert excerpt _
...
request_
...
connection _
...
request_
...
connection nopanel true
...
todo - find out if this can be renamed to something else unless it really relates to existing stream item actions.
Available for save actions. Select the specific change to make to the data records
- Either: todo
- Insert: create a new record in the stream (table).
- Update: change part of the record in the stream (table).
- Delete: delete the data record from the stream (table). todo - check about delete node, Adam think sit may be going away.
...
, 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 | ||||||
|---|---|---|---|---|---|---|
|
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 | ||
|---|---|---|---|---|
|
...
|
...
|
...
|
...
|
...
| Embeds an actionflow within the current actionflow. |
|
...
|
...
| ||||||||
|
...
Input Connection Points
todo -
separate properties so should be on its own page.
Should this have a description
Save does not have input connection points, although delete does.
Input properties has sections for Parent Details , Audit Summary and the following Basic Settings and Data Attributes.
Basic Settings
...
Select one of: todo - check definitons are correct
- Driving: where data is being used by the action node
- Requested: when the input is coming back from a lookup
Data Attributes
This section has a toolbar with standard buttons. The grid contains a list of the attributes that will pass through the input wire to this action. PhixFlow automatically lists the attributes that pass into the action when the actionflow is wired to an input with attributes. You can also:
...
To remove attributes, select one and click 
Permanently Delete. todo - check icon and label. What does this do? prevent them being passed through?
This has its own properties todo - separate properties so should be on its own page. Should this have a description?
...
Basic Settings
...
Field
...
Select one of the data types
- String
- Bigstring
- Integer
- Float
- Decimal
- Date
- Datetime
- Graphic
- TrueFalse
...
Calculate Action Expressions
Calculate actions process data using expressions; see pages in the topic Expressions and Scripts.
This section has a toolbar with standard buttons. The grid contains a list of the expressions that the calculate action will perform. To add a new expression:
...
To remove attributes, select one and click Permanently Delete. todo - check icon and label.
This has its own properties todo - separate properties so should be on its own page. Should this have a description?
...
Basic Settings
...
Field
...
Select tof the data types
- String
- Bigstring
- Integer
- Float
- Decimal
- Date
- Datetime
- Graphic
- TrueFalse
...
Enter an expression. To work in a larger pop-up window, click 
.
See also:
...
...
Output Connection Points
dfd
...
Access Permissions section is available for gateway actions.
...
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
|
| ||||||||||||||||||||||||
see View Node | Add a node for a data view. The actionflow uses views for additional data to use when processing records. |
| ||||||||||||||||||||||||
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. |
| |||||||||||||||||||||||||
see Open URL Node | Add an action to open a specified URL. |
| ||||||||||||||||||||||||
Add a node to save the specified records to their table. |
| |||||||||||||||||||||||||
| Runs analysis on the specified tables. |
| |||||||||||||||||||||||||
See HTTP Node | Performs an HTTP request. |
| ||||||||||||||||||||||||
See Email Node | Sends an Email to specified recipients. |
| ||||||||||||||||||||||||
See JSON Node | Handles JSON data and returns record objects as defined by the configuration. |
| ||||||||||||||||||||||||
See Loop Nodes | Facilitates the ability to loop within an actionflow for tasks such as polling or paging through results. |
| ||||||||||||||||||||||||
see Phase Node | Starts the phase specified by the user on the node. |
|
| Insert excerpt | ||
|---|---|---|
|
...
|
...
|