TIBCO BusinessConnect EDI Protocol powered by Instream 6.9.0 hotfix 1 has been released.

You can download this Hot Fix from the TIBCO Product Support website using your TIBCO Support username (email address) and password under “Downloads” and then “Hotfixes”

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

           /AvailableDownloads/BusinessConnect/EDI/6.9.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 6.9.0_HF-001 (This Release)

EDIP-2832
An outbound acknowledgement was generated from TIBCO BusinessConnect for an 
inbound request group. Interchanged header values were generated from the 
Transport Profile(TP) configuration instead of the values from an incoming 
request. 

This issue has been fixed by adding a flag that enables or disables the 
creation of the outbound acknowledgement from the TP settings to an inbound
request.

Add the following Boolean properties to BusinessConnect > 
System Settings > Activated Protocol Plug-ins and Properties > tibEDI:

--edi.x12.outbound.ack.creation.fromTP: Enabling this property will override 
the interchange and group header details for an outbound acknowledgement from 
TP configuration for X12 protocol.
--edi.edifact.outbound.ack.creation.fromTP: Enabling this property will override 
the interchange and group header details for an outbound acknowledgement from TP 
configuration for EDIFACT protocol.

Note: The default value of these properties is set to TRUE, i.e., the properties
get the values from TP configuration for creating the acknowledgement. 

EDIP-2834
When the processed transaction failed to get a response from the Interior 
engines, the inbound EDI-X12 documents with multiple interchanges were moved to
the Error Directory by the Gateway Server.

EDIP-2833
TIBCO BusinessConnect failed to parse a file when the inbound EDI document 
contained unknown TP.NullPointerExceptions.

EDIP-2837
TIBCO BusinessConnect EDI Protocol powered by Instream, dropped the EDI 
transactions in translation.

EDIP-2838
In TIBCO BusinessConnect EDI Protocol powered by Instream, Outbound File Poller 
Transport failed to move the files to an Error Directory when partner systems 
were unavailable.

EDIP-2836
The inbound EDI files sent from a Gateway partner were archived under both
Gateway and X12.

EDIP-2835
When the CAQH transaction was performed by enabling the scheduled transmission 
at the responder side, the EDI 824 acknowledgement status displayed 
"ACK PENDING" instead of "COMPLETED".

EDIP-2801
TIBCO BusinessConnect engine processed outbound batching and an EDI file was 
generated successfully, but BC_SCHEDULED_TASK table record displayed the status 
"RUNNING_SENT_TO_TP" instead of "COMPLETED" for large transactions.

EDIP-2781
When multiple interchanges were triggered in an EDI file for a transaction
using Inbound File Poller method, java.lang.NullPointerException was observed 
in BusinessConnect engine IS logs.

EDIP-2843
When the inbound files were processed and sent to a private process of TIBCO 
ActiveMatrix BusinessWorks using TEXT Protocol, an audit log message did not 
display the status "COMPLETED" for REQUEST_TO_PP state.

EDIP-2787
TIBCO BusinessConnect EDI Protocol incorrectly added an extra segment delimiter 
to an element data when the element data already contained segment delimiter.

EDIP-2844
There was a silent failure in TIBCO BusinessConnect EDI Protocol in case Interchange
rejection.

EDIP-1906
EDI related validation error subject in transaction body not show the complete EDI 
raw message in TIBCO BusinessConnect EDI Protocol.

================================================================================