Overview

Image Modified

Actionflows can use data displayed on screens. This data can be manipulated within an actionflow and can be saved onto tables. Sometimes an actionflow does not require any data from the screen from which it is initiated. In this case, use the 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 supplied.

Input Connection Points

Input Connection points are the interface to the actionflow. They define the inputs the actionflow is expecting, and allows values from the incoming inputs to be mapped onto these.

For example, an actionflow may expect an Area Code to calculate a distance. One screen passes the actionflow a Postcode this is mapped into the actionflow using the Input Connection Point mapping.Image Removed

Image Added

A second screen can reuse the actionflow (this is referred to as a different instance) and pass in a Zip Code which is mapped into the actionflow using the Input Connection Point mapping. Image Removed

Image Added

Input Connection Point Setup

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

1. Right-click the input Connection Point

2. Select 

   Insert excerpt
   _mappingConfigure _mappingConfigure nopanel true

   .

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.