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.4.2/hotfix-06.

================================================================================
Minimum Requirements

TIBCO(R) Enterprise Administrator 2.3.0_HF-002 or later.

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

Closed Issues in 6.4.2_HF-006 (This Release)

AMBW-32330
TIBCO Business Studio displayed File [null] cannot be opened using encoding
method [ASCII] error, when the Parse Data activity got an empty file or null
data as a string input.

AMBW-32304
The automatic_mapper_if_surround functionality did not work for Nillable
optional to optional elements mapping.

AMBW-32088
A few mappers were migrated as empty activities.

AMBW-32087
The Process Property with a value as a Module Property could not be set in the
Message Selector field on the Advanced tab of the JMS Receive Message activity.

AMBW-32043
The Module Property is now supported for the Delivery Delay (msec) field on
the Advanced tab of the JMS Send Message activity.

AMBW-31955
A few processes migrated as empty scopes and the error
"Argument cannot be null" was displayed when trying to open the processes.
This occurred when the schemas were not available for some activities.

AMBW-31903
In TIBCO ActiveMatrix BusinessWorks 6.x, the trackingInfo element was not
present under the ProcessContext element.

AMBW-31882
TIBCO Business Studio displayed validation error when mapping to a choice element,
and the second option from the choice list was selected.

AMBW-31876
After migration, TIBCO Business Studio displayed the Null pointer exception
when accessing the service context.

AMBW-31849
In some cases, TIBCO Business Studio displayed WSDL import error when concrete
WSDL was imported to the other application.

AMBW-31827
During migration, multiple schemas could not be migrated separately. A single
XSD file was created for multiple processes.

AMBW-31820
The Concrete WSDL file could not be retrieved at run time for a SOAP service
deployed through a web browser by using the URL.

AMBW-31817
The nonstandard tags in SubjectDN were not displayed correctly in the
Expose Security Context field.

AMBW-31812
TIBCO Business Studio displayed the Null Pointer Exception when generating
concrete WSDLs. The Null Pointer Exception was also displayed
when the inline schema of the abstract WSDL was imported with blank namespaces
or the schema had resource files with no target namespaces.

AMBW-31807
The JMS Receive Message activity with Client Acknowledge Mode displayed incorrect
receiver count on the queue in the FTgroup mode when the EMS server was restarted.

AMBW-31752
After migration, projects failed to start at runtime due to the missing schema.

AMBW-31746
Some job data was missing for a few projects, when the projects were run
in the debug mode.

AMBW-31721
The SOAP service sent incorrect fault response values to the client when
the Set Context activity was used to set the fault response values.

AMBW-31719
TIBCO ActiveMatrix BusinessWorks failed to process schemas and displayed the cache
exception at runtime due to a chain of chameleon includes.

AMBW-31703
After migration, the port type pointed to incorrect WSDL locations though
the serialization was correct.

AMBW-31645
After migration, the output of the Invoke activity was not visible.

AMBW-31573
After migration, a few processes displayed the process inline schema namespace
collision error.

AMBW-31566
The service implementation process was not migrated correctly when the
service agent process name included a period (.).

AMBW-31553
After migration, duplicate datasources were observed in the transition
from the Invoke activity.

AMBW-31552
After migration, the XPath expression was not resolved from the Invoke activity.

AMBW-31429
After successfully validating a project, when a process was deleted and then
migrated again, the project displayed errors in other processes.

AMBW-28129
After migration, unused process properties were created in the processes.

AMBW-23943
After migration, the Accumulate Output elements of the Iterate group
were not visible.

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