Task
You can use the Task transform to indicate a manual task or point of concern that might need to be resolved before a message map can be used in your solution.
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.
| Task type | Description |
|---|---|
| Error | Used to indicate a problem in your message map that must be resolved before the map is used in a solution. A Task transform of type Error is displayed in the Graphical Data Mapping editor, and in the Problems view of the Integration Development perspective. Your message map cannot be deployed if it contains one or more Task transforms of type Error. |
| Warning | Used to indicate an area of your message map that needs to be reviewed. A Task transform of type Warning is displayed in the Graphical Data Mapping editor, and in the Problems view of the Integration Development perspective. Task transforms of type Warning are ignored at run time. |
| Info | Used to contain a note or comment in your message map. A Task transform of type Info is displayed in the Graphical Data Mapping editor, and in the Problems view of the Integration Development perspective. Task transforms of type Info are ignored at run time. |
| To Do | Used to indicate an area of your message map that is incomplete. A Task transform of type To Do is displayed in the Graphical Data Mapping editor, and in the Tasks view of the Integration Development perspective. Task transforms of type To Do are ignored at run time. |
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.
Using a Task transform when you convert a legacy message map
When you use the IBM® App Connect Enterprise Toolkit to convert a legacy message map (.msgmap file) to a message map (.map) file, a Task transform is created in your new message map for each mapping structure that was not recreated 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>.