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 Page History

« Previous Version 17 Next »

In an actionflow, individual actions have connection points to receive data from the previous action. This page explains the type of connection point, and their properties.

Overview

Everything in an actionflow is connected using connection points. They are blue when connected and grey when not connected. There are two types of connections:

  •  Driving connection and
  •  Lookup connection

For information about the concepts related to wiring actionflows together using connection points, see Wiring Actionflows. 

For most action nodes, data flow is configured when you map attributes to the input connection points. For gateway nodes, you can also control the data flow by mapping to output connection points. This is because the expressions in a gateway provide the logic for which path the data flows, and different paths may require different data to pass through the gateway.

.


Connection Point Types

Icon

Connection PointRelevant toDescription

Interface Driving Connection Point

Input Interface

Output Interface

  • Defines the data attributes the actionflow is expecting as an input. This data is then used in the Actionflow using  Driving connections and remains constant.
  • Defines the data attributes the actionflow is expected to output. This data can then be mapped back onto components on the screen the action is being used.
  • Each instance of the actionflow will map in its own set of data onto the expected data inputs/outputs of the connection point.

Interface Lookup Connection Point

Input Interface

Output Interface

  • Defines the data (and events) the actionflow is expecting as an requested input. This data is then used in the actionflow using  Lookup connections and remains constant.
  • Each instance of the actionflow will map in its own set of data onto the expected data inputs.
Driving Output Connection Point

Input Data Components

 Calculate

  View

 Gateway

 Actionflow

  • A data source which drives the actionflow. Data is pushed through the actionflow using  Driving connection's.
  • Data flows from the  Driving output connection point to the  Driving input connection point.
  • Has attributes which can be mapped to any  Driving input connection point only.

Driving Input Connection Point

Output Data Components

 Calculate

  View

 Gateway

 Save Records

 Open Screen

 Open URL

 Run Analysis

 Phase

  • A data receiver. Data is received from  Driving connection's.
  • Has attributes which can be mapped to any  Driving output connection point only.
Lookup Output Connection Point

Input Data Components

  View

  • Provides lookup data to the actionflow using  Lookup connection's.
  • Any node with a  Lookup input connection point can perform a lookup to a node with a  Lookup output connection point.
  • Has lookup attributes and data attributes
    • Lookup attributes are used in filtering. They are mapped to lookup attributes on the node performing the lookup. Lookup attributes are referenced in the nodes filter using
      filter.[attributename]
      Data is flowing from the  Lookup input connection point to the  Lookup output connection point.
    • Data attributes are mapped to data attributes on the node performing the lookup. These attributes are the actual data that is being returned from the lookup.
      Data is flowing from the  Lookup output connection point to  Lookup input connection point
Lookup Input Connection Point

 Calculate

 Gateway

  • Performs a lookup to  Lookup output connection point's.
  • Has lookup attributes and data attributes
    • Lookup attributes are used in filtering. They are mapped to lookup attributes on the node being looked up to. Attributes that need to be sent to the node in order to filter the data must be added as lookup attributes.
      Data is flowing from the  Lookup input connection point to the  Lookup output connection point.
    • Data attributes are mapped to data attributes on the node being looked up to. These attributes are the actual data that is being received from the lookup.
      Data is flowing from the  Lookup output connection point to  Lookup input connection point


Todo-Fiona: There are also properties in Connection Points - same or different?

Input Connection Properties

Parent Details

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

Basic Settings

FieldDescription
NameBy default input connections are named in. Optionally, replace this with a descriptive name.
Type

Select one of: Todo-Fiona - check definitons are correct

  • Driving: where data is being used by the action node
  • Requested: when the input is coming back from a lookup

Data Attributes

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  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?

The data attribute properties has sections for Parent Details , Audit Summary and the following Basic Settings

Field

Description
NameBy default input connections are named in. Optionally, replace this with a descriptive name.
Type

Select one of the data types

  • String
  • Bigstring
  • Integer
  • Float
  • Decimal
  • Date
  • Datetime
  • Graphic
  • TrueFalse

 Audit Tab

Audit Summary

See the Common Properties page, Audit Summary section.

Output Connection Properties

Parent Details

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

Basic Settings

FieldDescription
NameBy default input connections are named in. Optionally, replace this with a descriptive name.
Expression

Todo-Fiona - standardised expression

Order

 Audit Tab

Audit Summary

See the Common Properties page, Audit Summary section.

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.

  • No labels