Overview

Actionflows can use data displayed on screens. This data can be manipulated within an actionflow and can be saved onto tables. Sometimes consume data through their Connections (also known as the Input Connection Points). There are also circumstances where an actionflow does not require any input data from the screen from which it is initiated. In this case, use the event as the input for the actionflow. An event is triggered by mouse-clicks (On-Click, Double-Click)  or keyboard presses (On-Enter). Connecting an event to an actionflow means the actionflow runs in response to the event, regardless of any data suppliedand instead the Input Connection Point is configured to consume an event, such as a mouse click. All Actionflows are connected to an event that runs the actionflow,  and have at least one Input Connection Point as its driving input connection point i.e. of type Input.

Input Connection Points

Input Connection points are the interface to the actionflow. They define the inputs, lookups and outputs the actionflow is expecting, and allows values from the incoming inputs to be mapped onto these. For example, an actionflow may expect specify what data, if any, is passed through them.

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 Point Setup Wizard

When a new input is connected the mapping wizard will appear. To reopen the mapping wizard:

1. Right-click the input Click on the connector between the Input Data and the Input Connection Point.Select 

Insert excerpt
_

mappingIcon _

mappingIcon nopanel true

Mapping Properties

Data to be Used

Mappings

1. Drag a record from the left (input) onto a corresponding record on the right (Input Connection Point)
   1. If no corresponding record exists in the Input Connection point one can be added by dropping an incoming record into the empty space on the right, this causes a new record to be created.
2. This input is now mapped correctly into the actionflow. 
3. Repeat for all required inputs.
4. Click Confirm Mapping.

Further information, see Wiring Actionflows.

Input Connection Points