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.
Click the image to view full size.
The Object drop-down shows the available
Further down, the left-hand XML tree structure shows those data source fields available for mapping
TIP: If you have selected No data source in the General tab, you must add BPA Platform formulas and variables to the left-hand data source XML tree structure before mapping.
Creating Mappings
The Call Task tool is used to trigger an external task to run. Using variables, BPA Platform data can be passed between the two tasks at run-time, if required. input field (right). Only linked fields are used in the output XML.
Note: You do not need to map data (create links) if the called task does not require any input data from this step during run-time.
BPA Platform formulas and variables can be included in the source data even when using a Task step or Custom schema The Convert Recordset to XML tool converts one or more flat-structure BPA Platform recordsets into a hierarchical XML structure. It provides "translation services" between the standard BPA Platform tools, such as Database Query (ODBC), and advanced BPA Platform tools that accept XML as their input. or Transform Data Transform Data is a Format tool that enables a new structure to be created from an existing XML or recordset data source. The output generated by this tool is ready for use in a destination system which consumes or requires XML. tool before they can be used here.
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.
The tool uses eXtensible Stylesheet Language Transformations (XSLT) to translate the received XML. The Advanced Translations (XSLT) tab shows the XSLT generated for the links created for the object and operation. Use Enable Free Type Mode to directly edit the XSLT — this is particularly useful when translating a non-standard requirement.
Refreshing the Called Task's Schema
If new task data, such as variables, are added to the called task after this step was created, you must refresh the called task's schema in order to see the new data in the InputData schema — click Schema Refresh (first ensure Update Objects and Operations is selected in the relevant global connection).
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.
Refreshing the Called Task's Schema
If new task data, such as variables, are added to the called task after this Call Task step was created, you must refresh the called task's schema in order to see the new data in the InputData schema — click Schema Refresh.
Supported Operations
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 The Convert XML to Recordset tool is used to convert XML data into a flat-format BPA Platform recordset, allowing the data to be used by recordset-only consuming tools. This could then be used to power alerts via fax, email, or SMS, create reports, power a workflow, perform FTP transfer, and so on. tool.
Use this operation if the original task requires data from the called task.
| ► | 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.