Mule
X12 and EDIFACT Connectors Release Notes - Mule 3
Support Category: Premium
1.4.3
Octuber 6, 2020
Fixed Issues
EDIFACT EDI Connector:
None in this release.
X12 EDI Connector:
-
Downgraded the Scala compiler version to 2.11.7 for compatibility with the Scala version used by DataWeave.(SE-17730)
Compatibility
Application or Service | Version |
---|---|
Mule 3.6.0 and later |
|
X12 |
003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, and 006020 |
HIPAA |
005010X212, 005010X214B3, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, and 005010X279A1 |
1.4.2
July 28, 2020
Fixed Issues
EDIFACT EDI Connector:
None in this release.
X12 EDI Connector:
Upgraded the Scala Compiler version to 2.12.10 and log4j version to 2.11.0 (CONN-6439).
Compatibility
Application or Service | Version |
---|---|
Mule |
Mule 3.6.0 and later |
X12 |
003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, and 006020 |
HIPAA |
005010X212, 005010X214B3, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, and 005010X279A1 |
1.4.1
1.3.4
April 2019
Fixed Issues
EDIFACT EDI Connector:
-
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)
X12 EDI Connector:
-
Added support for integer value types for implied decimal format. (SE-11494)
-
Multiple HIPAA transaction sets in a group are now correctly handled. (SE-9043)
-
Identified the ISA segment when it’s the cause of a write error. (SE-10796)
-
Changed the shaded package name for debugger compatibility. (SE-10796)
-
Added the transaction set information to the error message for "schema not found". (SE-7935)
Compatibility
EDIFACT EDI Connector v1.3.4 is compatible with the following:
Application/Service | Version |
---|---|
Mule |
Mule 3.6.0 and later |
EDIFACT |
d93a, d95b, d96a, d97a, d98b, d99a, d99b, d00a, d01b, d02a, and d03a |
X12 EDI Connector v1.3.4 is compatible with the following:
Application/Service | Version |
---|---|
Mule |
Mule 3.6.0 and later |
X12 |
003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, and 006020 |
HIPAA |
005010X212, 005010X214B3, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, and 005010X279A1 |
1.3.2
August 3, 2018
This release adds support for HIPAA X222A1 and X224A2 837 transaction sets.
Compatibility
X12 EDI Connector v1.3.2 is compatible with the following:
Application/Service | Version |
---|---|
Mule |
Mule 3.6.0 and later |
X12 |
003010, 003020, 003030, 003040, 003050, 003060, 003070, 004010, 004020, 004030, 004040, 004050, 004060, 005010, 005020, 005030, 005040, 005050, and 006020 |
HIPAA |
005010X212, 005010X214B3, 005010X217, 005010X218, 005010X220A1, 005010X221A1, 005010X222A1, 005010X222A2, 005010X223A2, 005010X223A3, 005010X224A2, 005010X224A3, and 005010X279A1 |
1.3.0
November 7, 2017
Fixed Issues
-
X12 corrected an error in formatting values for the ISA10 and GS05 time fields.
-
X12 corrected a serialization-related error causing an exception scala.MatchError: None.
-
EDIFACT changed parser to interpret UNOY syntax identifier as UTF-8 encoding by default, for consistency with writer code.
New Features
-
X12 HIPAA support, including Type 1 and 2 validation.
-
X12 error reporting - added information for error type (interchange, group, transaction, segment, or element) and interchange/group/transaction set identifiers; all error reports now included in the root level map.
-
X12 now includes all versions from 003010 to 005050, and 006020.
-
X12 added validateBeforeWrite configuration parameter to check for errors in data before writing to the output stream, instead of checking while the data is being written; if one or more fatal errors are found an exception is thrown from the write operation without any data being written.
-
X12 added ackAllSets configuration parameter to generate a separate AK2/AK5 (997) or AK2/IK5 (999) acknowledgment for every transaction set; by default, only transaction sets with errors are specified in the acknowledgment.
-
EDIFACT added receiveEncodingOverride configuration parameter to allow the user to specify the receive character encoding
-
EDIFACT added support for UNOW syntax identifier in parser, interpreting this as UTF-8 encoding.
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.
-
Add interchange information (with sender and receiver reversed) to X12 TA1 interchange acknowledgments generated by parsing.
-
Support sending X12 messages with only TA1 interchange acknowledgments, no transaction data.
Fixed Issues
-
Corrected some off-by-one errors in reporting data errors for both X12 and EDIFACT, and some segment off-by-one errors for EDIFACT.
-
Changed loop/group keys in data, eliminating position numbers previously used at start of key.
-
Corrected loop position tracking and reporting in X12 ACK3/IK3, ACK4/IK4 segments (997/999 functional acknowledgments).
-
Correct check for data present when reading a composite to work correctly when first value of composite is empty.
-
Abort parsing of EDIFACT message if the initial UNA/UNB cannot be read (since there’s no way to know the delimiters being used for message).
1.0.2
March 9, 2016
Fixed Issues
-
Changed identifiers for X12 loops with numeric values as names, using the number as part of the identifier (rather than the identifier of the first segment in the loop).
-
Correct handling of X12 repeating group inside LS/LE wrapper.
-
Fix issue causing X12 parser IllegalStateException "Illegal structure at position…".
1.0.1
1.0.0
Sept 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 loops 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:
-
X12 binary segments are not supported, are not included in schema definitions, and cause errors.
-
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. (as of version 1.3.0, X12 HIPAA validation supports mandated code values)
-
X12 syntax rules and EDIFACT dependency notes are not currently enforced for either reading or writing. (as of version 1.3.0, X12 HIPAA validation supports syntax rules)
-
EDIFACT groups are not supported.