Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 19 Next »

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.

  1. From Inputs on left into the actionflow.
  2. From one node to another.
  3. 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.

The properties available for connection points vary depending on the node on which they occur. 

Input Connection Points 

Property Pane Toolbar

For information about the toolbar options, see the Common Properties page, Toolbars and Controls section.

 Properties Tab

Parent Details

If this item is within or belongs to another, its parent name is shown here. See the Parent Details section on the Common Properties page for more details.

Basic Settings

FieldDescription
NameEnter the name for the connection pint.
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.

  • Primary 
  • Component
Type

Available when Role is Component.

Specify the type of connection:

  •  Driving input connection point: there can be only one of these.
  •  Lookup input connection point: there can be multiple of these
Open Mode

Not seeing this for the INPUTS input connection

Available when Role is Component.

text

  • Insert
  • Update
  • Change Fields
Action Phasedefault

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:

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  Add New and specify the Name and Type; see Attribute.


This section has a toolbar with standard buttonsThe 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  Add New 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?


 Audit Tab

Audit Summary

See the Common Properties page, Audit Summary section.

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:

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. 

Property Pane Toolbar

For information about the toolbar options, see the Common Properties page, Toolbars and Controls section.

 Properties Tab

Parent Details

If this item is within or belongs to another, its parent name is shown here. See the Parent Details section on the Common Properties page for more details.

Basic Settings

Field

Description
NameEnter 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.

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  Show field in a large editor.

See also:


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.

 Audit Tab

Audit Summary

See the Common Properties page, Audit Summary section.

Sections on this page

Learn More

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


Terminology changes in progress

As part of the redesign of PhixFlow, we are changing the following terms:

dashboard → screen   
stream → table
stream attributes → attributes
stream item → record
stream set → recordset
stream view → view
stream item action → record-action 
stream action → table-action
driver class → database driver

Actionflow Wire Properties

Wire properties do not include the name. Todo-Fiona - check - I thought I saw where you could change its name

Basic Settings

FieldDescription
InputThe action at the start of this wire.
Input Connection Point


OutputThe action at the end of this wire.

Data Mappings

Standard text

Lookup Mappings

todo

 Audit Tab

Audit Summary

See the Common Properties page, Audit Summary section.

Learn More

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



Terminology changes in progress

As part of the redesign of PhixFlow, we are changing the following terms:

dashboard → screen   
stream → table
stream attributes → attributes
stream item → record
stream set → recordset
stream view → view
stream item action → record-action 
stream action → table-action
driver class → database driver


  • No labels