See information about the latest product version
After: the converted graphical data map
After you update the message map, you should review and amend the transforms in the graphical data map so that it behaves in the same way as the original message map.
The following image shows the converted graphical data map configuration for the map named MembersMFPFlow_Mapping.map:

The transforms are updated as part of the solution, so that even though the transforms are now of a different type, they behave in the same way as in the message map. You can test this by following the steps in Verifying the solution after you follow the steps for Implementing the solution.
Graphical data maps use all standard XPath 2.0 functions and allow user-written functions in Java and ESQL. Message maps used basic XPath 1.0, some proprietary built-in ESQL mapping functions, and user-written Java and ESQL functions.
Not all ESQL functions can be directly translated to XPath equivalents, but these functions are resolved in the scenario solution. In the screen capture, you can observe these changes to the following elements:
- MEMBER_NAME_PART.PERSON_GIVEN_NAMES is now
set by using standard XPath expressions to check whether the input
message has non-white-space characters in PERSON_MIDI_NAME.
The Graphical Data Mapping editor provides a warning here because
the map's logic assumes that the input message has MEMBER_NAME_PARTS present,
which is defined as a choice in the message schema model with MEMBER_NAME_WHOLE.
For this scenario, the original message map author has assumed that
the input data will always include MEMBER_NAME_PARTS,
so the warning can be ignored on the same assumption.
To avoid this warning, and the one on the PERSON_SURNAME mapping, you can add an If / Else check for MEMBER_NAME_PARTS or MEMBER_NAME_WHOLE.
- MEMBER_AGE_GROUP is set by using a call to a user-written ESQL function ageRange(). This is unchanged.
- MEMBER_INT_GROUP is set by using an If / Else construct, which continues to use a standard XPath expression for the transform condition.
- MEMBER_COMMENT1 is now set by using standard XPath expressions that replace the previous proprietary ESQL functions in the Message Mapping editor.
- MEMBER_COMMENT2 and MEMBER_COMMENT3 are set by calling user-written ESQL functions commentPart2() and commentPart3(). It was necessary to add an XPath conditional expression to prevent the commentPart3() ESQL being invoked when the input data is fewer than 48 characters long. This corrects a difference in behavior for user ESQL functions that can return an ESQL NULL value. For more information on ESQL changes in mapping, see Changes in behavior in graphical data maps converted from message maps.
You can now re-create these changes by using either your own files or the scenario files that are provided by following the steps as part of Implementing the solution.