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 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 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.
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.
When a new input is connected the mapping wizard will appear. To reopen the mapping wizard:
- Right-click the input Connection Point
- Select
| Insert excerpt |
|---|
| _mappingConfigure |
|---|
| _mappingConfigure |
|---|
| nopanel | true |
|---|
|
.
| Data Name | Description |
|---|
| Selected Records | Records selected in the Input. For example multiple records selected on a grid. |
| Edited Records | Records that have been edited on the input. For example, only records which have been edited on a grid. |
| Page | All records on a page. For example a single record being edited using a form. |
| Dragged Records | Selected records that have been dragged onto a drop target. |
| Drop Target Records | Records Dropped onto a drop target. |
- Drag a record from the left (input) onto a corresponding record on the right (Input Connection Point)
- 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.
- This input is now mapped correctly into the actionflow.
- Repeat for all required inputs.
- Click Confirm Mapping.
Further information, see Wiring Actionflows.