Description:
TIBCO BusinessConnect EDI Protocol 2.8.0 Hotfix 4 has been released
You can download this HotFix 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
    ActiveExchange/EDI/2.8.0/hotfix-4/


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

#  BusinessConnect Audit logs have incorrect information in them even when 997 is generated correctly.
(PD_Id:1-6OUYOD, SR_Id: 1-6OH9UP)

BusinessConnect Audit Logs were reporting incorrect information when there are informational/warning/errors reported on transactions when an interchange with multiple transactions were validated. This occurs when edi.auditErrorReport.ignoreWarnInfo property is enabled to ignore reporting informational/warning validations in the audit log as well as in the Advisory.

# 837 File Fails to complete processing when there are multiple transactions that have validation errors reported.
(PD_Id:1-6R00W0, SR_Id: 1-6OZYHF)

This happens when there are multiple validation errors within a segment that causes the audit reporting to fail due to incorrect indexing when the EDI document contains an interchange with multiple transactions.

# Incorrect AK401 in 997 in SB 5.5.
(PD_Id:1-6OGWQO, SR_Id: 1-6O3FI5)

When Element PRV03(Reference Identification) is missing in 837, the AK401 is being mapped incorrectly in 997 that is generated. The 997 value was reported as 2, but the count should have started with 1, with the AK401 value of 3.

# Trailing spaces are not trimmed for the messageType field specified in the leaffields. This causes the message to not match against the operation for EDI-TEXT protocol.
(PD_Id:1-6OHBVL, SR_Id: 1-6MG965)

When the header is parsed, the trailing spaces are not trimmed for the values of the Leaffields, making the values to not match against the values in the BusinessConnect repository. E.g. when specifying the messageType field to be 16 characters long, If the operationId value is "Order" as messageType in BusinessConnect protocol repo, the EDI-TEXT parser will return "Order " which is never matched against "Order" operation defined in the BusinessConnect repository.

# No Output file is created for ediconvert when the operationid has Name Modifiers.
(PD_Id:1-6ERGFD, SR_Id: 1-6CP3G0)

When trying to verify the EDI file through ediconvert utility, if the EDI file points to a operation ID that has Name Modifiers, then there is no output file is created during the EDI to XML conversion.

# Enhancement Request to add ability to set UNB-0026 to multiple values per trading partner depending on the type of transaction being sent to the Trading Partner..
(PD_Id:1-6OJY2N, SR_Id: 1-6NRNZ7)

Enhancement Request to add ability to set UNB-0026 to multiple values per trading partner depending on the type of transaction being sent to the Trading Partner. There is a perMessage attribute (applicationRef) added to the InterchangeInfo class of the AESchema which would allow the user send UNB-0026 values on a message basis. Users should copy the ediclient.jar to the $BW_HOME/plugins/lib directory and refresh the palette.

TIBCO BusinessConnect EDI Protocol 2.8.0 Hotfix 4 has been released

Product: TIBCO BusinessConnect EDI Protocol Version: 2.8.0 OS: All --------------------