2020.1

l
The XPath must start with =
l
The entire JavaScript statement must be enclosed in curly brackets: { ... }
l Any other curly brackets that are not part of the JavaScript code must be escaped
with a backslash.
l Single line comments (//...) in the code are not supported.
Note that since the XPath is a string, the return value of the JavaScript statement will be
interpreted as a string.
Note
Currently, XPaths that select elements based on an attribute, attribute value, node
value, node counter or node index are not supported.
l
Show all elements: When the delimiter is set to a specific element or XPath, checking
this option allows to extract information from higher-level nodes, including those that
follow the element or path. This might slow down the processing, so if you don't need any
information from the higher-level nodes that follow that specific element, it is
recommended to leave this option unchecked.
When this option is used in combination with a trigger element that is not repeated at the
same node level (in other words, it doesn't have a sibling with the same name), the entire
XML document will be shown for each record, except the trigger element, which will only
be shown for the record that is currently selected in the Data Model pane.
This could lead to a problem with some steps that use an XPath with absolute indexes,
such as a location-based Extract step. Using a dynamic index in the XPath will fix the
problem. For example, in the case of a location-based Extract step, switch to extracting
the data via JavaScript (see "JavaScript-based field" on page264); in the JavaScript
expression, replace the index of the element's parent in the XPath with record.index.
Note
The information contained in all of the selected parent nodes will be copied for each
instance of that node. For example, if a client node contains multiple invoice nodes, the
information for the client node can be duplicated for each invoice.
The DataMapper only extracts elements for which at least one value or attribute value is
defined in the file.
Page 318