...
| 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
...
.
...
- Save
- Delete Todo-Fiona - check
- Gateway
- Open Screen
- Open URl
- Lookups
- Request Query Lookup
- Streaming Query Lookup
...
For information about connecting actionflow nodes together, see Wiring Actionflows.
Adding Action Nodes
Connection Points
To add action nodes to the actionflow, drag the icons from the toolbar to the canvas. Everything in an actionflow is connection using connection points. They are blue when connected and grey when not connected. Find all the possible connection points below.
...
Icon
...
...
Interface Driving Connection Point
...
Input Interface
Output Interface
...
...
Input Interface
Output Interface
...
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
...
...
...
Input Data Components
- Will create an
Insert excerpt _action_
- Will create an
...
screen _action_
...
screen nopanel true
...
- node.
Insert excerpt _
- node.
...
table_list _
...
table_list nopanel true
...
Will ask the user if they would like to create aInsert excerpt
...
_
...
...
Output Data Components
...
action_
...
save _action_save nopanel true
...
- node or
Insert excerpt _action_
- node or
...
view _action_
...
view nopanel true
...
Input Data Components
...
- node.
- 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 | ||
|---|---|---|
|
...
|
...
|
...
|
...
|
...
|
...
req.[attributename]...
. 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 | ||
|---|---|---|
|
...
|
...
|
...
|
...
Action Nodes
The toolbar includes the following actions that you can drag onto the canvas.
Actions can be added to actionflows in 3 ways:
...
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 | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Embeds an actionflow within the current actionflow. |
|
...
|
...
|
...
|
...
| ||||
|
...
|
...
|
...
...
see Open Screen Node | Add an action to open a specified |
...
screen |
...
Open screen nodes can be created with or without a screen attached. This is useful if the screen has not been created yet. Open screen nodes which do not have a screen attached appear with a warning symbol to remind users that this still needs to be configured.
Each open screen node has 1 primary input connection point by default called 'in'. Connecting to this connection point simply opens the screen and cannot pass any data to it. Do we still need this?
Once a screen has been attached to the open dashboard node an input connection point for each form on the screen is created. Each input connection point automatically has any data fields on the form (dynamic text or form fields) added as attributes. These attributes can be mapped to and supplied with data.
Each input connection point has the following properties:
- Type
- Open Mode
- Role
- Attributes
Configure the purpose for the screen that will open
- update: opens form fields with the latest data (tnot clear, refresh)
- insert: opens the screen with form fields empty clear, not refresh)
- change: opens form fields with data (not clear, not refresh)
To set the actionflow to close the active dashboard on completion, on the top right of the canvas, tick Close Parent Dashboard.
...
. 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. |
Connect a view node to the action node that needs to look-up data via the lookup connection 
icon page. A look-up connection has 2 parameters:
| ||||||||||||||||
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. |
|
...
|
...
|
...
Add a node to saves the specified stream-items to their stream.
...
|
...
| hidden | true |
|---|
The following icons are for post 9.0 action nodes
...
| ||||||||||||||
see Open URL Node | Add an action to open a specified URL. |
|
...
|
...
|
...
|
...
|
...
|
...
|
...
Add a node to |
...
save the specified records to their table. |
|
...
|
...
|
...
|
...
|
...
Properties
|
...
|
...
|
Basic Settings
Todo-Fiona - How do you specify the different types of gateway
...
...
An application can have many actionflows, and an individual actionflow can have many actions. This can lead to many items being listed in the repository. Use this option to omit the action from the repository.
see Analysis Node | Runs analysis on the specified tables. |
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
Todo-Fiona- 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 stream-items:
...
See HTTP Node | Performs an HTTP request. |
| ||||||||
|
...
|
...
|
...
|
...
|
...
See Email Node | Sends an Email to specified recipients. |
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
Input Connection Points
This section has a toolbar with standard buttons. The grid contains a list of the wires that pass data into the action.
To edit an existing connection, double-click its name in the list.
To add a new
...
See JSON Node | Handles JSON data and returns record objects as defined by the configuration. |
|
...
|
...
|
...
Drag add an existing attribute to this list Todo-Fiona- is this possible??
...
|
...
|
...
|
...
|
...
|
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:
...
See Loop Nodes | Facilitates the ability to loop within an actionflow for tasks such as polling or paging through results. |
|
...
|
...
|
...
Output Connection Points
Todo-Fiona
|
...
|
...
|
...
see Phase Node | Starts the phase specified by the user on the node. |
|
...
|
...
|
| Insert excerpt | ||
|---|---|---|
|
...
|
...
|
...
Pop-up Toolbar
Todo-Fiona
- Under what circumstances does the pop-up toolbar appear
- screenshot
...
Pop-up Menu
...