Task

The Task transform can be connected to one or more inputs, and to a single output, to indicate the input and output elements that are required to resolve the point of concern.

Use the Documentation property of a Task transform to describe the details of your manual task or point of concern. The Documentation property can also contain a link to a related resource, for example a .msgmap file.

For information about the Mapping node, see Mapping node.

When you use the IBM® Integration Toolkit to convert a message map (.msgmap file) to a graphical data map (.map) file, a Task transform is created in your new graphical data map for each mapping structure that was not re-created by the conversion process. The Documentation property of a Task transform is used to describe the unconverted transform and, where possible, a suggested solution. For example:

This map transform was generated by conversion of the message mapping built in a previous version of the product.
The original transform from the converted file "example.msgmap_backup" was was "esql:concat('NativeError: ', esql:sqlnativeerror())".
The convert processing could not provide an equivalent transform. Reason: There is no supported corresponding XPath expression for esql:sqlnativeerror().
This map cannot be deployed and run until this 'Task' transform is re-implemented.
To re-implement this transform and remove the error marker on the map consider changing the 'Task' transform into a <Custom XPath Transform>.

For more information about converting .msgmap files, see Converting a message map from a .msgmap file to a .map file.