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 the download the hotfix by selecting the “Downloads” -> “Hotfixes” option. Then go to the AvailableDownloads/BusinessWorks/6.7.0/hotfix-03.


================================================================================
Closed Issues in 6.7.0_HF-003 (This Release)

AMBW-44017
TIBCO ActiveMatrix BusinessWorks throws an error  when mapping the JDBC Query activity's output
to the Iterate group.

AMBW-43437
For REST application deployed on an AppNode, the bw-flowlimit-executor-provider threads are
not destroyed and keep on increasing even after starting and stopping an application.

AMBW-43407
Non-default namespace can not map to empty URI
Set the -Dbw.xml.jsonrest.multiple-ns.removensprefix=true property as a VM argument in
TIBCO Business Studio for BusinessWorks.
This property removes all non default prefixes from the xml and uses only default namespace
prefix for all namespaces and ensures that a non default namespace is never bound to an empty URI.

The Render XML activity adds an extra namespace xmlns="" at the root level of the schema.
Set the -Dbw.xml.rootPrefixFilter.suppressEmptyURI=true as a VM argument in
TIBCO Business Studio for BusinessWorks.
This property removes all instances of xmlns="" from the xml when
the Format Using Default Namespace Prefix check box is selected on the General tab of
the Render XML activity.

AMBW-43337
If there are multiple versions of a same application deployed on same AppSpace but on different
AppNodes and if you try to start a particular AppInstance of the application, then an AppInstance
of some other application starts.
This issue occurs only when you do not perform a refresh action on Admin UI.

AMBW-43327
The SQL Direct and JDBC Query activities are timed out after few iterations with the TeraData
custom database driver.

AMBW-43253
Empty tag is not generated for optional-nil elements.

Now, a new Treat optional-nil elements as optional elements check box is added on
Window > Preferences > Mapper page. Select the check box and clean the workspace.

After cleaning the workspace, you get some XSLT out-of-sync errors on the Problems tab.

Use the Quick Fix option to resolve those errors and execute the project again to generate empty tags
for the optional-nil elements.

AMBW-43218
On running an application, the Activity output data validation error is displayed when the JDBC Query
activity is used with the Iterate group.

AMBW-43206
If you hit a particular endpoint of a REST service using the Send HTTP Request activity, the activity
fails with the java.lang.RuntimeException: java.io.EOFException error instead of the 401 Unauthorized
error.

AMBW-43167
Transition condition with boolean value is not evaluated correctly against String true.

Add the new -Dbw.xml.comparable.legacy.booleanStringEquality=true property as a VM argument
along with the -Dbw.engine.use.transition.xpath.expression.lang.1.0=true property in
TIBCO Business Studio for BusinessWorks

AMBW-42860
TIBCO ActiveMatrix BusinessWorks consumes a large memory heap and throws the out of memory
error when you read a file using the Java Invoke activity.

AMBW-42717
If the Get JMS Queue Message activity is configured with the TIBCO EMS Explicit Client acknowledge
mode and the activity is added in a loop, then the unacknowledged messages are not processed
because the activity times out.

Add the -Dbw.getjmsactivity.buffer.timeout.miliseconds = <value in milliseconds> property as a
VM argument in TIBCO Business Studio for BusinessWorks.

This value is then added to the value specified for the timeout field on the Input tab of
the Get JMS Queue Message activity and increases the timeout value of the activity to process the
unacknowledged messages as well.

AMBW-42519
The process id value for an AppNode present in the output of an API server URL does not change
even if you restart the AppNode.

AMBW-41937
TIBCO ActiveMatrix BusinessWorks does not display expected elements, if any, when an unexpected
element is encountered while validating an XML document against a schema

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