You can download this HotFix from the 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 go to the AvailableDownloads/BusinessWorks/6.10.0/Hotfix-05.

Refer to the attached 6.10.0 hotfix-05 readme for a complete list of defects addressed in this hotfix.

================================================================================
6.10.0_HF-005 (This Release)

New Features

AMBW-44404
Support is now added for converting Path, Query and Header Parameters defined 
with "pattern" keyword in Swagger 3.0.0 file to corresponding Pattern 
restriction in XSD. This is applicable only for top-down service created with 
Swagger 3.0.0 JSON file.
Note: The pattern should be defined with $ref in the swagger file 
and should not be declared inline.

Changes in Functionality

AMBW-51984
With this fix, the users are presented with a choice of schema option of 
"message" or "faultactor, faultstring and faultcode" at the input 
for undeclared fault. For the older projects, the user must reselect 
the fault under General tab of the Reply activity to see the option.

Closed Issues

AMBW-52839
Throwing NullPointerException instead of actual Fault details of 
called Function/Procedure in SQL Direct Activity.

AMBW-52805
The application component starts and stops correctly when auto-start is 
disabled and Appspace is configured in FTGroup mode.

AMBW-52780
Users can now filter the properties and update the values.

AMBW-52744
When an XML Content is sent using com.tibco.bw.rv.bw5Compliance system property
set to true with BW6 RV Publisher activity, observed TibrvMsg type 
mismatch and tampered body/payload.

AMBW-52743
When an XML Content is sent using com.tibco.bw.rv.bw5Compliance system property
set to true with BW6 RV Request Reply activity, observed TibrvMsg type 
mismatch and tampered body/payload.

AMBW-52742
When an XML Content is sent using com.tibco.bw.rv.bw5Compliance system property
set to true with BW6 RV Request Reply/ Publish activity, 
Subscriber activity faults with output data validation error.

AMBW-52590
While invoking a REST service defined with required/mandatory 
Request Header Parameters error was not thrown if the request headers 
were not passed in the request. Now request header validation is taking place
and 400 Bad Request error is thrown.

AMBW-52498
The RenderJSON activity was appending ".0" to the output values of 
Double data type greater than 7 Digits.
To resolve this we have to set the system property 
bw.xml.double.c14n.spec.nonconformant=true, along with the already
existing system property bw.xml.double.minimizeC14N=true, 
to generate non-scientific representation of double values 
greater than 7 digits.

AMBW-52449
Unable to deploy an application from TIBCO Business Studio for 
BusinessWorks using a Deployment server.

AMBW-52407
A "REST Schema to XSD Schema conversion error" is thrown at design time 
when you Generate XSD Schema or create a REST service from 
OAS 3.0.0 Swagger JSON file.
Now, the properties that contain neither a 'type' nor '$ref' property 
are resolved as anySimpleType in the XSD schema. 
You can handle empty models present under "responses". 
You can also create REST Reference Binding and invoke the service. 
Also, the Swagger UI is loading correctly.
The following are a few known issues that are to be 
observed and resolved in the future release:
- oneOf/allOf with $ref and inline schema. Here, the inline schema is 
  not supported. Hence, the Input on Reply activity of PATCH operation 
  is empty and cannot be invoked at runtime.
- When there are multiple success codes excluding 200, then one of the 
  success codes get replaced with 200 when displayed on the Swagger UI.
- "BadRequestException: Invalid JSON request" error is thrown if we hit 
  a REST service's POST operation from Swagger UI with a request body 
  composed of nested allOf and oneOf properties, which is not supported.
Workaround: Use REST Reference Binding as a client in BW to invoke 
            the REST service.

AMBW-52317
The Send HTTP Response activity does not preserve double quote characters (")
in the filename parameter when the Content-Disposition header is passed 
as an inline value in Dynamic Headers.

AMBW-52270
The component starts and stops correctly when auto-start is disabled and 
Appspace is configured in weighted/not weighted FTGroup mode.

AMBW-52248
The application failed to start if the REST service was created using a 
swagger 2.0 JSON file having properties declared as empty {} and contain 
neither a 'type' nor '$ref' property.
Now, the properties that contain neither a 'type' nor '$ref' property are 
resolved as anySimpleType in the XSD schema.
We need to set the system property bw.rest.convert.nested.json=true, 
for rendering the response if the value provided is an object for 
the empty element. The value for such an element has to be sent in 
string format i.e. with escape characters in the input.
Use third party clients like Swagger UI to invoke the service if 
the JSON object/array is expected for empty element.

AMBW-52235
The issue with applications using the 'JMS activities": 
They are not working after an EMS failover, or if the EMS server 
is unavailable for a few minutes and then restarts.
We've implemented a fix that successfully addresses the 
EMS reconnection problem.

AMBW-52102
There was a mismatch in application status displayed on TEA. This has
been fixed.

AMBW-51493
Application hangs and throws ClassCastException in TIBCO BW when using
com.tibco.bw.rv.bw5Compliance with TibrvXml type mismatch in RV Listener.

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

You can also download the hotfix using the below link:

https://support.tibco.com/s/hotfixes

TIBCO BusinessWorks 6.10.0 Hotfix-05 is available