B2B/EDI Management Release Notes for January 2026
January 24 2026
We added these features
-
Added namespace prefix configuration for XML Custom Document Standards, so you can associate prefixes with URIs for XPath expressions, simplifying condition and action authoring and maintenance. (B2B-5047)
-
You can configure the EDI Standard ID on the XML Profile Options tab to link the profile to a standard. (B2B-4886)
-
Custom Trading Partner Document Type profile options are filtered by EDI Custom Standard ID. (B2B-5048)
We fixed these issues
- When the Trading Partner configuration includes a legacy CUSTOM standard My Company without a CUSTOM trading partner, data is still routed through the EDI Custom connector. (B2B-5195)
- Fixed an issue with AS2 client certificate authorization, so you can successfully receive inbound AS2 documents from Trading Partners. (B2B-5189)
- The description for the Custom Standard Component displays in the Create Component dialog when you hover over the component type. (B2B-5169)
- Added a document property
Is Standardthat, when set toTrue, removes the standalone attribute from the RosettaNet service content body, allowing partners to properly digest PIP messages without encountering parsing issues. (B2B-3975)