Using the Translation editor, you can identify one or more XSLT scripts to be used by the SRT component of ASAP at run time (the XSLT scripts must be created by a developer). These XSLT scripts enable an XML document to be transformed into another XML document of a different structure. For example, an XML document arriving at the SRT from an upstream system must be transformed into an XML document that conforms to the SRT service activation schema. Alternatively, an XML document arriving at the SRT from ASAP (for example a work order failure notification) must be transformed into an XML document format that is expected by an upstream system.
Translations can be implemented to:
Translate incoming requests from an upstream system.
Translate ASAP responses to ASAP events (such as FAILURE, COMPLETE) for return to the upstream system.
Translate outgoing ASAP events (such as FAILURE, COMPLETE) to the upstream system.
By convention, translations are contained in a single file. It is not necessary to create additional files for different upstream systems, but you may choose to do so for organizational purposes.