Processing conversion annotations
An annotation on a converted transform shows that although the transform is successful, you might want to review that it behaves as you expect. You can either confirm or reject the annotated transform in your graphical data map.
About this task
If you are using the scenario files, after you follow the steps in Converting the message map your MembersMFPFlow_Mapping.map file looks like the following image:
You can see that MEMBER_NAME_PART.PERSON_GIVEN_NAMES now takes the output from both an If and Else transform. Both transforms have warnings, and there is an annotation on the If transform. Follow the steps to review an annotated transform.
- In the Graphical Data Mapping editor, select the If transform that shows a conversion annotation icon. The transform properties are displayed in the Properties view.
In the Properties view, click the Documentation tab
to review details about the transform.
The If transform Documentation field advises that the
esql:trimfunction used in the previous message map, which is not a valid type in a graphical data map, is converted to an XPath
fn:normalize-spacefunction. However, the behavior might be changed, and so the text in the field suggests that you should review the transformation.
Review the transformation logic that was created by the conversion to ensure that it produces
the correct output for your application.
You can review the online documentation for XPath expressions to check how
fn:normalize-spaceworks. In the scenario, the If transform behavior is correct, so you can accept it.
In the Graphical Data Mapping editor, right-click the transform. Click
Accept to remove the warning from this transform.
Alternatively, after you review all the transforms in a converted map, you can use a menu action to accept or reject all annotated transforms. Select an area of the map so that no transform is selected and right-click the area to open the menu.
- Save your updated map.
There are still warnings on the child transforms of MEMBER_NAME_PART in the scenario map. The Graphical Data Mapping editor provides a warning here because the map's logic assumes that the input message has PERSON_NAME_PARTS present, which is defined as a choice in the message schema model with PERSON_NAME_WHOLE. For the scenario, this assumption comes from the original message map, and therefore it is valid.
To avoid this warning, and the one on the PERSON_SURNAME mapping, you can add an If or Else check for PERSON_NAME_PARTS or PERSON_NAME_WHOLE. This is an optional task, because warnings do not affect the behavior of the map. You do not have to remove the warnings to complete the scenario.