Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 3
Next »
New features and improvements
- White spaces and special characters allowed in field names in Layouts
White space and special characters (~`! @ # $%^&*() {} [] | \\ : ; " ' - + =<> / ? . , ) are now allowed in the field names of the following layouts:- Advanced Text Layout
- Positional Layout
- Advanced Positional Layout
Bug Fixes
Following Bugs have been fixed in this release:
- While transforming an XML file into an EDIFACT, the special characters such as single quotes and colons are prefixed with “null” value in the target EDI file.
- The execution of an EDI Outbound Relationship is getting failed if it has been defined with Content based routing and namespace.
- Issue related to the EDI schema not getting validated because of the invalid character, asterisk (*).
- The Non-EDI B2B process flow fails and throws a Null error at CP_RoutingRelationship custom plugin activity when Mail is used as a target using archive option.
- In Data Mapping, the Target EDI file does not contain a single quote (') for the UNB segment when the data is transformed from EDIFACT 99A TO 95B.
- When processing a Text layout, the system throws an error while parsing a numeric data with (+) sign associated with it.
- The repository folder still contains the context info and context variable details after the successful execution of the process flow even if the Repository File Retention is set to "Delete On Success".
See also
Patch Deployment Guide