Description:
TIBCO BusinessConnect RosettaNet Protocol Hotfix 3 is now released.

This hotfix is cumulative of prior hotfixes for this version. Please note that it DOES NOT include hotfixes for the BC framework. This is a change from previous hotfix releases.

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 as well as the readme document under
    available_downloads/ActiveExchange/RosettaNet/2.8.0/hotfix-3/




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

[hotfix-3]
   - (SR_Id:1-360Z9H) This hotfix has been tested and validated against TIBCO BusinessConnect 3.6.0.

[hotfix-2]
   - (SR_Id:1-2GK9BD) Added new enhancement to extract (best-try) the proprietaryDocumentIdentifier in the payload, upon a schema validation error. Upon a schema error, a more lenient 2nd pass of the parsing of the payload document will be performed in order to attempt to extract the ProprietaryDocumentIdentifier, which will be used to return back to the TP in the corresponding Exception message.
  
   - (SR_Id:1-253J4X) The versionIdentifier inside the SignalIdentity element was incorrectly populated with the incoming action id. This issue has now been fixed. The correct versionidentifier value is read from the repository.
  
[hotfix-1]
    - (SR_ID:1-1KXMDX) Added new property into &ltBC_installation_directory>\resource\RosettaNet.cfg bcrn.pp.rawPayload: false By default, this property is set to false. If this is set to true, BCRN will forward the XML document extracted from the message "as is" to the private process, consistent with how the document was formatted by the trading partner.
    
    - (SR_ID: 1-1YQYL5) Fixed the XML document root node validation problem. BCRN will now verify the expected rootElement (e.g &ltPip3A4PurchaseOrder>) with the actual XML document root element (e.g. &ltns0:Pip3A4PurchaseOrder>) correctly without taking into account of the namespace prefix, if any.