This page is for application designers who need to configure functionality for components or events. It explains the properties for the input and output connection points. Connection points wire together inputs, nodes and outputs in an actionflow.
Overview
Use the input and output connection points on nodes in an actionflow to wire the nodes together.
- From Inputs on left into the actionflow.
- From one node to another.
- From a final actionflow node to the Outputs on the right of the actionflow.
- For input connection points, map which attributes to pass into the node.
- For output connection points, specify an expression to determine ??? passed onto the next node.
| Note |
|---|
The properties available for connection points vary depending on the node on which they occur. |
| 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 the name for the connection pint. |
| Action Phase |
| Role | Available for View and Open Screen nodes. todo-Fiona: more infor does something get set to component based on the instance input? By default this option is set to Primary. |
| Type | Available when default |
| The following properties are available for view nodes and 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 | Not seeing this for the INPUTS input connection Available Available when Role is Component. text - Insert
- Update
- Change Fields
|
| Action Phase | default |
When the view or 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
A list of attributes in other action nodes that you can map into this node.
You can refer to these attributes in an expression using the syntax:
| Code Block |
|---|
connectionpointname.attributename |
Lookup Attributes are available when Type is Lookup.
Double-click on an attribute in the list to display the properties related to this node and connection. This can include Name, Type, Component, Primary Key etc.
To add a new attribute, click
and specify the
Name and
Type; see
Attribute.
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:
- create a new attribute: click and set its properties. Todo-Fiona - why would this be useful
- drag add an existing attribute to this list Todo-Fiona - is this possible??
- double-click one of the listed connections to open its properties.
- remove attributes, select one and click
Permanently Delete. Todo-Fiona - check icon and label. What does this do? prevent them being passed through?
Output Connection Points
Each output connection point has an expression that specifies the logic to control whether or not records flow to the next action node.
For driving output connections, you can refer to an attribute in the expression using the syntax:
| Code Block |
|---|
connectionpointname.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 pop-up 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. |