XML generated for an outbound integration (e.g. a Send Purchase Order message via INET_TRANS) breaks when a description or address field happens to contain characters like &, <, or > — how do you systematically strip or escape these before they reach the XML output?

All FAQ questions / Integrations and APIs

Answer

Create a Transformer file and attach it to the relevant Routing Address — the transformer runs on the outbound message and can strip or properly escape special characters like &, <, and > before the file is generated, rather than needing to sanitize the source data itself at the point of entry.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Integrations and APIs questions