Skip to main content

Version 1.18.2.4

Release Date: September 15, 2026 Release Type: Stable Previously published as: 1.18.20 (image tag staging-1.18.20)

Splitter improvements: XPath expressions can use the namespace prefixes declared in the message, and monitoring shows the split pieces as the Splitter's output.

Backend Server​

Bug Fixes​

  • Splitter XPath resolves the namespace prefixes the message declares: A split XPath that used a namespace prefix, such as //ns:Item, failed with "Prefix must resolve to a namespace", so namespaced elements could only be split with a local-name() expression. The Splitter now registers every xmlns:prefix declaration found in the incoming XML, so the expression can use the message's own prefixes as they are. XPath behaviour is otherwise unchanged: an unprefixed name still matches only elements without a namespace, local-name() keeps working, and a default namespace cannot be addressed by a prefix. Grouped pieces under a prefixed parent element are now well-formed XML.
  • Message monitoring shows the split pieces as the Splitter's output: The Splitter row in message monitoring displayed the original document as its output. It now shows the pieces the split produced, as one document: XML pieces inside a <SplitResult count="N"> envelope, JSON pieces as an array, and other content separated by line breaks. This affects the monitoring display only; the messages passed on to the following nodes are unchanged.

Frontend Web​

New Features​

  • Namespace prefix hint on the Splitter XPath field: For the XPath split type, a hint under the XPath input explains how namespace prefixes are resolved: a prefix works when the incoming message declares it, and an unprefixed name matches only elements without a namespace. The hint adapts to the current expression and is guidance only; it does not block saving.

1.18.2.4 is a stable release. Previous: 1.18.2.3