Versions Compared
Version | Old Version 27 | New Version 28 |
---|---|---|
Changes made by | ||
Saved on |
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Insert excerpt _Banners _Banners name actionflow nopanel true
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 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:
- Calculate
- Gate
- View
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.
Input Connection Points
Anchor | ||||
---|---|---|---|---|
|
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
Insert excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
|
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
Basic Settings
Field | Description | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Name | The name for the connection point. This defaults to in . | ||||||||||||||||
Type | Specify the The type of connection:
|
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.
| ||||||||||||||||
Type | Available when Role is Component. Specify the type of connection:
| ||||||||||||||||
Open Mode | Available when Role is Component. When the screen opens, specify what data fields will display.
| ||||||||||||||||
Attributes | A list of attributes available on the input connection point. These directly link to the fields available on the form.
|
HTML Comment | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Not yet implemented - and may need to be on the input connection page.
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:
|
Data Attributes
A list of attributes in other action nodes that you can map into this node.
You can 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 using expression, specify the names of the connection point and attribute with 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 tje properties related to this node and connection. This can include Name, Type, Component, Primary Key etc.
- To
- create a new attribute
- : click
andInsert excerpt _add _add nopanel true
- 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
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 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: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 its properties.Insert excerpt _add _add nopanel true - drag add an existing attribute to this list.
- double-click one of the listed connections to open its properties.
- remove attributes, select one and click Image Removed Permanently Delete. 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 | ||||||
---|---|---|---|---|---|---|
|
Output Connection Points
Anchor | ||||
---|---|---|---|---|
|
The following nodes have intput connection points:
- Calculate
- Gate
- View
Nodes without an output connection represent:
eitherThis section is not available for nodes that do not require output connections because: the node represents the end of actionflow processing: Save, Open Screen
and, Open URL, and Analysis nodes
Each .
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. For driving output connections, you can refer to an attribute in the expression using the syntax. The syntax for a driving connection is:
Code Block |
---|
connectionpointname.attributename |
The syntax for a lookup connection is:
Code Block |
---|
connectionpointnamereq.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 | ||||||
---|---|---|---|---|---|---|
|
Insert excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
|
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
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.
| ||||||||
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
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. |
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
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. |
Expression |
Data Mappings
This section has a toolbar with standard buttons.
The grid contains a list of data
To remove a mapping, use the toolbar button Delete.
Request Mappings
todo
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
Learn More
For links to all pages in this topic, see Understanding Actionflows.
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
Live Search | ||||||||
---|---|---|---|---|---|---|---|---|
|
Panel | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
Learn More
For links to all pages in this topic, see Understanding Actionflows.
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|