Description:
TIBCO BusinessConnect EDI Protocol 5.3.0 hotfix 1 has been released.

You can download this Hot Fix from the TIBCO Product Support FTP server using your eSupport username and password, at

            ftp://support-ftp.tibco.com

Once you have successfully logged into the server, you will find the hotfix packages under

            available_downloads/ActiveExchange/EDI/5.3.0/hotfix-01/

Listed below is a summary of updates included. Please refer to the associated readme document for any additional information.

Closed Issues in 5.3.0-hotfix1 (This Release)

CR:1-9BCRB9

This backward compatibility defect corrects the pass-through mode for
EDI-TEXT documents sent out to the Trading Partner from Private Process.
Earlier releases of EDI allowed sending EDI-TEXT documents as pass-through.
EDI 5.3.0 had not made this change of behavior in the release notes or
the migration path. This fix is to allow customers to use EDI-TEXT as
pass-through by enabling the following property in Configuration UI.

User needs to Add the following boolean property under:
BusinessConnect-&gtSystem Settings-&gtInstalled Protocols-&gtEDI and the property:
"edi.text.outbound.passthrough.compatibility.enabled" and mark it as
checked to take effect. This backward compatibility would take effect
only for EDI-TEXT participants who has the
Participant-&gtEDI-TEXT-&gtGeneral-&gtOutbound->"Enable EDI Validation"
(a new feature added in EDI 5.3.0 which is disabled by default) is unchecked.


CR:1-98TQCH

This defect corrects unnecessary transformation of outbound XML documents
to an intermediate XML file when XML to EDI conversion and validation occurs.
This happens for every Outbound XML document and contributes to extra
processing time.

CR:1-96J259

This fix requires the hotfix correction from TIBCO BusinessConnect EDI Protocol
HIPAA Edition 5.2.0-hotfix1 to work correctly. Please install the mentioned
hotfix fix also after installing this fix.

When there are Validations Errors for HIPAA Claims at a Claim Level, ClaimID is
not getting reported for 837 Transaction Claims.

This defect corrects the issue, whereby it reports the ClaimID in the Audit Log as
well as part of the Advisory.