Products | Versions |
---|---|
TIBCO BusinessEvents Enterprise Edition | 5.6.1 HF3 |
You can download this Hotfix from TIBCO Support Portal (https://support.tibco.com). You will need to provide your TIBCO Support Portal credentials. Once logged in you can download the hotfix by selecting the “Downloads” -> “Hotfixes” option, then navigate to /AvailableDownloads/BusinessEvents/EnterpriseEdition/5.6.1/hotfix-03 to download the Hotfix.
Alternatively, you can use the direct portal link to download Hotfix-03
https://support.tibco.com/s/hotfixes?id=a012L00000OEPMIQA5
================================================================================
Closed Issues in 5.6.1_HF-003 (This Release)
================================================================================
BE-27883
In the TIBCO BusinessEvents Studio, an error was encountered while opening the
HTTP channel generated from the imported WSDL.
BE-27861
In WebStudio, when the condition cell of a decision table had spaces between values and the operator, then on selecting the cell, the values are cleared.
BE-27825
The Store.getAll() function threw an exception when entities to be retrieved were not present in TIBCO ActiveSpaces 4.x store.
BE-27820
Rules were fired multiple times for the same entities in the same RTC.
BE-27796
When the same folder structure and folder names were defined in a projectlibrary and the project imported from projlib, the EAR file creation failed.
BE-27792
The custom function was not loading when the DefaultHandler class was used in it.
BE-27790
Errors were reported when WSDL files in the project referred to other schemas through the xsd:import statement.
BE-27781
In TIBCO BusinessEvents Administrator Agent UI, update to the global variables could not be deployed when the TIBCO BusinessEvents engine was running.
BE-27765
When a project was migrated to the latest product release, the older version of the custom schema, with the targetNamespace field, did not work.
BE-27748
In the TIBCO BusinessEvents Enterprise Administrator Agent UI, the project deployment status was incorrect in either of the following conditions:
- After uploading the modified EAR or CDD for the project
- After editing the global variables in the project.
================================================================================