Overview
Use the input and output connection points on nodes in an actionflow to wire the nodes together.
- From the Inputs pane on left, into the actionflow.
- From one node to another within the actionflow.
Hover your mouse pointer over a node and click Add Output to add an connector to another node. - From a final actionflow node to the Outputs pane on the right of the actionflow.
Connection points available depend on the purpose of the node.
- Output connection points:
Nodes without an output connection represent:
- either the end of actionflow processing: Save, Open Screen and Open URL nodes
- or processing out of the actionflow: Analysis node.
When you wire nodes together, you need to map which attributes pass through to the next node. To change the mapping, click on the connector to open the Mapping window.
Node properties have sections for Input Connection Points and Output Connection Points on the node. Double-click on a listed connection point to open its properties.
Note |
---|
The properties available for connection points vary depending on the node on which they occur. |
Driving and Lookup Connection Points
- If you connect a node via a driving connection, records are returned individually to the connected node and flow one by one through the remainder of the actionflow.
- If you connect a node via a lookup connection, the records are returned as an array within one recordset. Nodes wired via lookup connection points require both:
- Data Attributes: add attributes from the view. PhixFlow looks-up data from these attributes.
- Request Attributes: when the actionflow runs, PhixFlow returns the data to these attributes.
The following sections explain the properties for input and output connection points.
See Input Connection Points.
Insert excerpt |
---|
| _property_toolbar |
---|
| _property_toolbar |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| _property_tabs |
---|
| _property_tabs |
---|
name | basic-h |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| _parent |
---|
| _parent |
---|
nopanel | true |
---|
|
Basic Settings
Field | Description |
---|
Name | The name for the connection point. This defaults to in . |
Type | The type of connection: Insert excerpt |
---|
| _driving_input_connection_point |
---|
| _driving_input_connection_point |
---|
nopanel | true |
---|
| : wire nodes via one driving input connection point Insert excerpt |
---|
| _request_input_connection_point |
---|
| _request_input_connection_point |
---|
nopanel | true |
---|
| : the following nodes can have a one or more lookup connection points: Calculate, Gate and View.
|
The following properties are available for open-screen nodes only. |
---|
Field | Description |
---|
Role | Specify whether the actionflow will provide data to the view or screen being opened. - Primary: selected by default.
The view or screen opens regardless of data. - Component:
The actionflow provides data to the view or screen when it opens.
|
Type | Available when Role is Component. Specify the type of connection: Insert excerpt |
---|
| _driving_input_connection_point |
---|
| _driving_input_connection_point |
---|
nopanel | true |
---|
| : there can be only one of these. Insert excerpt |
---|
| _request_input_connection_point |
---|
| _request_input_connection_point |
---|
nopanel | true |
---|
| : there can be multiple of these
|
Open Mode | Available when Role is Component. When the screen opens, specify what data fields will display. - Insert: data fields are empty, ready for the application user to add new data.
- Update: data fields display latest changes.
- Change Fields: data fields display data.
|
Attributes | A list of attributes available on the input connection point. These directly link to the fields available on the form. - Primary connection points display the screen properties as attributes.
- Component connection points display attributes available on the associated form.
|
HTML Comment |
---|
Not yet implemented - and may need to be on the input connection page. Each open screen node has 1 primary input connection point by default called 'screen'. Available when Input connection point Role is Primary, optionally set: Field | Type | Default Values if not set | Description |
---|
Height | Number |
| Sets the height of the screen | Width | Number |
| Sets the width of the screen | Top | Number |
| Sets the top position of the screen relative to the window | Left | Number |
| Sets the left position of the screen relative to the window | Maximised | Boolean | whatever is set on the screen properties | - True will open the dashboard in its maximised state.
- False will open the dashboard in its minimised state and will use the above properties.
|
When you connect an open screen node to a screen, PhixFlow automatically adds an input connection point for each form on the screen. The input connection point is automatically set to: - Role Component.
- Attributes: all data fields and dynamic text fields are added.
This means you can map to the attributes and pass data to them.
|
Data Attributes
This section has a toolbar with standard buttons. The grid contains a list of the attributes that will pass through the wire into this node. All nodes can have a driving input connection, which passes data records one-by-one into the node.
To refer to these attributes in an expression, specify the names of the connection point and attribute with the syntax:
Code Block |
---|
connectionpointname.attributename |
Double-click on an attribute in the list to display tje properties related to this node and connection. This can include Name, Type, Component, Primary Key etc.
- To create a new attribute: click and set the Name and Type; see Attribute.
- To add an existing attribute to this list, open the list of attributes and drag one onto the grid.
- To open its properties, double-click one of the listed attributes.
- To remove an attribute, select one and click
Insert excerpt |
---|
| _delete |
---|
| _delete |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| _structured_data |
---|
| _structured_data |
---|
nopanel | true |
---|
|
Request Attributes
Available for View, Gate and Calculate nodes, which can have Lookup connection points.
This section has a toolbar with standard buttons. The grid contains a list of the attributes that you want to lookup from another table. Lookup connections pass a complete set of records into the node.
To refer to these attributes in an expression, specify:
Code Block |
---|
req.attributename |
Double-click on an attribute in the list to display its properties related to this node and connection. This can include Name, Type, Component, Primary Key etc.
- To create a new attribute: click and set the Name and Type; see Attribute.
- To change its properties, double-click an attribute in the list; see View Attribute
- To delete an attribute, right-click and select
Insert excerpt |
---|
| _delete |
---|
| _delete |
---|
nopanel | true |
---|
|
.
Insert excerpt |
---|
| _structured_data |
---|
| _structured_data |
---|
nopanel | true |
---|
|
Output Connection Points
This section is not available for nodes that do not require output connections because: the node represents the end of actionflow processing: Save, Open Screen, Open URL, and Analysis nodes.
For all other nodes, the output connection point has an expression that specifies the logic to control whether or not records flow to the next action node. The syntax for a driving connection is:
Code Block |
---|
connectionpointname.attributename |
The syntax for a lookup connection is:
Code Block |
---|
req.attributename |
If the expression evaluates to true for the record flowing through the node, it will pass through the connection point onto the next node in the sequence.
Insert excerpt |
---|
| _property_toolbar |
---|
| _property_toolbar |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| _property_tabs |
---|
| _property_tabs |
---|
name | basic-h |
---|
nopanel | true |
---|
|
Insert excerpt |
---|
| _parent |
---|
| _parent |
---|
nopanel | true |
---|
|
Basic Settings
Field | Description |
---|
Name | Enter a name for the output connection point |
Order | Enter a number to indicate the order in which this expression will be run. Remember that an expression that generates a value must run before an expression that uses the value. Tip |
---|
The order is very important for exclusive gateway nodes, as the records pass through the first output connection that meets the expression condition. |
|
Expression | Enter an expression that evaluates to true or false to specify whether or not records pass through this connection point. To work in a larger popup window, click Insert excerpt |
---|
| _editor_expand |
---|
| _editor_expand |
---|
nopanel | true |
---|
|
. See also: |
Note |
---|
Gateways can have an unlimited number of output paths. If the Gateway Node is Exclusive records only pass through the first output path where the expression condition is met. |
Actionflow Wire Properties
Wire properties do not include the name.
Basic Settings
Field | Description |
---|
Input | The name of the node at the start of this wire. |
Input Connection Point | The name of the connection point. |
Output | The name of the node at the end of this wire. |
Output Connection Point | The name of the connection point. |
To remove a mapping, right-click and select Delete Mapping
The left grid contains a list of attributes available from the input.
Output Mappings
The right grid contains a list of attributes available to map to in the output.
Learn More
For links to all pages in this topic, see Understanding Actionflows.
Insert excerpt |
---|
| _terms_changing |
---|
| _terms_changing |
---|
nopanel | true |
---|
|