Mule
EDIFACT Connectors Release Notes - Mule 3
Support Category: Premium
The EDIFACT EDI connector lets you convert EDIFACT messages to and from DataWeave-compatible representations using lists and maps.
1.3.4
April 2019
Fixed Issues
-
Fixed the infinite loop when missing a UNT segment. (SE-10442)
-
Added a specific error message when missing a UNT segment. (SE-10442)
-
Added support for integer value types for implied decimal format. (SE-11494)
-
Corrected escape character handling on read. (SE-9795)
-
Eliminated NPE when space value is set for a delimiter character. (SE-11312)
-
Changed the shaded package name for debugger compatibility. (SE-10796)
1.3.0
1.2.1
September 28, 2016
New Features
-
Added support for inline components in ESL schema definitions.
-
Added support for writing DataWeave-compatible types.
-
Improved overlay handling, allowing segments to specify only modified components and change component type
-
Support writing repeating composite.
Fixed Issues
-
Corrected some off-by-one errors in reporting data errors, and some segment off-by-one errors.
-
Changed group keys in data, eliminating position numbers previously used at start of key.
-
Correct check for data present when reading a composite to work correctly when first value of composite is empty.
-
Abort parsing of message if the initial UNA/UNB cannot be read (since there’s no way to know the delimiters being used for message).
1.0.1
1.0.0
September 21, 2015
New in This Release
This release contains many improvements, including:
-
Support for reading/writing multiple versions of the same transaction type within a single message
-
Additional EDIFACT message types d03A and d95B
-
Improved structure usability with DataWeave and MEL by including "Loop" in the key name for groups and using underscores instead of spaces. You will need to update your integrations appropriately for this (see below).
-
Improved validation logic on writing.
-
Many bug fixes
Migration Guide
All of your transformations and expressions that references parts of the EDI message structure must be updated for the following changes:
-
The "Transactions" list has been changed to "TransactionSets" and now has an additional level for the version of the transactions.
-
Example: payload.Transactions."850" now becomes payload.TransactionSets.v5010."850"
-
-
All keys no longer have spaces - instead they have underscores
-
Example: payload."0100 PO1" becomes payload."0100_PO1"
-
-
Any segment that is a loop
-
Example: payload.Detail."0100 PO1" becomes payload.Detail."0100_PO1_Loop"
-
Known Issues
The following issues apply to all versions:
-
EDIFACT packages (containers for binary data) are not supported, and cause errors if you attempt to use them.
-
EDIFACT interactive exchanges (using UIB header segment and UIZ trailer segment) are not supported.
-
Code values are not currently verified for either reading or writing.
-
EDIFACT groups are not supported.