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.

Driving and Lookup Connection Points

• If you connect a node via a driving connection, records are returned individually

   to

   to the connected node and flow one by

  one 

  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

See Input Connection Points.

Connection Points 

Anchor
input input

Insert excerpt
_property_tabs _property_tabs name basic-h nopanel true

Basic Settings

Data Attributes

This section has a toolbar with standard buttons. The  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:

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 

  Insert excerpt
  _add _add nopanel true

   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

Request Attributes

Available for View, Gate and Calculate nodes, which can have Lookup connection points.

This section has a toolbar with standard buttons. The  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:

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 

  Insert excerpt
  _add _add nopanel true

   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

  .

Output Connection Points 

Anchor
output output

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:

connectionpointname.attributename

The syntax for a lookup connection is:

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_tabs _property_tabs name basic-h nopanel true

Basic Settings

Actionflow Wire Properties

Wire properties do not include the name. 

Basic Settings

To remove a mapping, right-click and select Image Modified Delete Mapping

Input Mappings

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

• Creating Actionflows

• Wiring Actionflows

For links to all pages in this topic, see Understanding Actionflows.