Velocity templates

If you want to transfer additional outputs to the order data record, you can use the two Velocity template specifications. In them, part of the XML order data record can be defined by textual substitutions and specific context depending rules.

IMPORTANT: If you want to change something in this area you should be familiar with XML and with XML schema as well as with Velocity templates. If a code recorded here is not a valid XML or Velocity, it can lead to problems during the processing in the PPS. Pay attention especially to the XML schema for tickets in the appendix of this document.

• The Ticket XML block generally determines further ticket components according to the defined XML schema for tickets.
• The Custom XML block enables the recording of a private custom data record, which either is a well formed XML or beyond this follows a private XML schema. If this XML schema is specified, the PPS validates this block accordingly.

So, both blocks are primarily XML data, but they can be completed in the Velocity template language via instructions. If Velocity elements are present, these text blocks will be converted into XML fragments only within the subsequent processing process, which then are transferred to ticket data records.

INFO: The designation Velocity comes from the Apache Velocity open source project, which provides the interpreter for the description language.

From the Velocity templates, the Custom-Tags as well as the User-Tags of the order can be referenced, to be able to produce specific outputs depending on them. You will find details about the Velocity template language via the following link to the online documentation of Apache Velocity. https://velocity.apache.org/engine/releases/velocity-1.5/user-guide.html