Creating an eText Template 4-35
Negates the IN operator.
Reference to XML Extract Fields and XPATH Syntax
XML elements can be used in any expression. At runtime they will be replaced with the
corresponding field values. The field names are case-sensitive.
When the XML extract fields are used in the template, they must follow the XPATH
syntax. This is required so that the XML Publisher engine can correctly interpret the
There is always an extract element considered as the context element during the XML
Publisher formatting process. When XML Publisher processes the data rows in a table,
the level element of the table is the context element. For example, when XML Publisher
processes the data rows in the Payment table, Payment is the context element. The
relative XPATH you use to reference the extract elements are specified in terms of the
For example if you need to refer to the PayeeName element in a Payment data table,
you will specify the following relative path:
Each layer of the XML element hierarchy is separated by a backslash "/". You use this
notation for any nested elements. The relative path for the immediate child element of
the level is just the element name itself. For example, you can use TransactionID
element name as is in the Payment table.
To reference a parent level element in a child level table, you can use the "../" notation.
For example, in the Payment table if you need to reference the BatchName element, you
can specify ../BatchName. The "../" will give you Batch as the context; in that context you
can use the BatchName element name directly as BatchName is an immediate child of
Batch. This notation goes up to any level for the parent elements. For example if you
need to reference the RequesterParty element (in the RequestHeader) in a Payment data
table, you can specify the following:
You can always use the absolute path to reference any extract element anywhere in the
template. The absolute path starts with a backslash "/". For the PayeeName in the
Payment table example above, you will have the following absolute path:
The absolute path syntax provides better performance.
The identifiers defined by the setup commands such as define level, define sequence