Follow-On Topics

Related Topics

# About the Mapping Tab

The Mapping tab is used to select the task to run. However, you do not need to map data if the called task does not require any input data. ## Selecting a Task The Object drop-down shows the available tasks. The Operations drop-down shows the operations available for the selected Object:
|  | RunSync — Runs the called task when called by the original task; the original task waits for the called task to complete before continuing. Parameter-type variables can be used to pass data between the tasks; with RunSync operations, the original task cannot complete until the data is passed back.
The data passed back is store in the output XML of the original task. This in turn can be consumed by another step capable of processing XML, such as the Convert XML to Recordset tool. Use this operation if the original task requires data from the called task. | Click the image to view full size.

|  | Queued — Queues the second task but continues to run the original task to completion; both tasks run independently of each other. Data can be passed to a parameter-type variable in the called task. However, this operation does not allow data to be passed back as the original task has already completed running before the second task initialises.

Use this option when only triggering a task to run, with or without data from the originating task.

## Mapping to the Called Task

You create links by clicking and dragging a data source field (left) onto its corresponding called task input field (right) in the Design tab. The called task input pane also contains any task variables from the called task that can accept data from the original task. You can add parameter-type variables to the data source pane to make them available for mapping . Only mapped fields are included in the output XML.

Each operation has an additional field, `SupplementaryReference`, which allows for traceability when transferring data from one place to another. When mapped, the data resides locally at runtime. It is added to the output, and creates a record for reference purposes only — you can choose to map any field to `SupplementaryReference` to assist with checking where the data originated from or at what time the data transfer occurred, for example.

NOTE:

Only Parameter-type variables can be processed by the Call Task tool. Datafile and Password type variables are not supported; nor are variable arrays.

Copyright © 2018 Quadrant Software B.V. All rights reserved.