The hotfix can be downloaded from the TIBCO Support Customer Portal Web UI,
using your username and password for the TIBCO Support Web.

Once logged on the hotfix can be found under the Downloads Menu:
AvailableDownloads/AMX_BPM/3.0.0/hotfix004

Listed below is a summary of updates included. Refer to the associated readme document for any additional information.

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

Closed Issues in 3.0.0_HF-004 (This Release)

Note: Where the closed issue is related to a TIBCO Support case, the relevant
case number (CN-xxxxxxxx) or Support Request ID (SR-xxxxxx) is given in brackets
after the Issue number.

WRM-9352 (CN-01443648)
----------------------
When a client application used the REST version of the saveOpenWorkItem
operation (in the WorkItemManagementService), the request failed if the request
body contained a type-based value for a data field defined as a complex type
(complexSpec). The request succeeded if it used an element-based value.

WRM-9343 (CN-01253006 / SR-722510)
----------------------------------
On a distributed BPM system, if the shared configuration folder (used to store
BPM properties files) is not called <SHARED_DIR>\configuration,upgrading the
ActiveMatrix BPM version could encounter problems.

WRM-9306 (CN-01244087)
----------------------
A TIBCO ActiveMatrix BusinessWorks application failed (with an 'Output data
invalid' error) when calling the openWorkItem operation from the
WorkPresentationService service. The error occurred when the work item invoked a
dynamic pageflow, because the openWorkItem response message did not contain a
formIdenitifier element, which was expected by the schema.

NOTE: If you have developed client applications that use the BPM public web
service API and that call the openWorkItem operation from the
WorkPresentationService service, you will need to modify
the WorkPresentationService schema definition used by your application to
prevent this error from occurring. To do this:

1. If your application uses:

   * a WSDL generated from the WorkPresentationService running on the
     ActiveMatrix BPM runtime, regenerate that WSDL.

   * the BPM public web service API (WSDL and XSD files) directly, updated
     versions of the wp.xsd, wp-basetypes.xsd and wpModel.xsd files are
     supplied with this Hotfix, in the 3.0.0_HF-004_wsdls archive file. (The
     updated versions make the formIdentifier element optional.)

2. Update your application to use the new wp.xsd, wp-basetypes.xsd and
   wpModel.xsd files, or the regenerated WSDL, as appropriate.
     
WRM-9295 (CN-01253006 / SR-722510)
----------------------------------
During an upgrade, the createdb-admin.sql script failed with an "ORA-28007: the
password cannot be reused" error. This occurred because the script used the
database password multiple times (via the IDENTIFIED BY clause), which was not
permitted by the database profile.

WRM-9266 (CN-01257104)
----------------------
In some situations, an expression or script was evaluated incorrectly because
the process instance was using an old value (that is, one set earlier in the
process instance's lifecycle) instead of the current value. This could lead to
unexpected behaviour - for example, a gateway following an unintended path.

WRM-9230 (CN-00719110 / SR-706408)
----------------------------------
Populating an attribute with a value containing any special characters sometimes
caused the process instance to halt, due to an error in writing the attribute
value to the BPM database.

WRM-9224 (CN-01446081, CN-01239572 / SR-740136)
-----------------------------------------------
When publishing BPM audit date to an external Enterprise Message Server (EMS),
the number of EMS message producers kept increasing, eventually causing a
resource leak. This error occurred if the amx.bpm.ec.threadpool resource
template used different values for its Core Pool Size and Max Pool Size values.
In this case, threads are created and reclaimed dynamically as required, but
reclaimed threads were not being handled correctly, causing the increase in EMS
message producers.

WRM-9282
--------
A runaway process generated a large number of tasks within a single process
instance. This resulted in the instance generating large numbers of audit events
and lots of rows in the PVM_* database tables.

Now, when the BPM runtime starts to process an event for a process instance, it
checks (and increments) how many tasks the process instance already has. If this
value equals or exceeeds a threshold the process instance halts and writes the
following warning to the BPM log file:

   [WARN] - {MAX_TASKS_PER_INSTANCE_REACHED} - Instance [pvm:xxxxx] has reached
   the maximum number of tasks allowed: [1,000].

and the following audit message:

   BX_INSTANCE_PROCESS_MAX_TASKS_REACHED  Maximum number of tasks per instance
   reached.

You can configure the threshold value (default 1000) using the
com.tibco.bx.maxTasksPerInstance JVM property. You may wish to do this if, for
example:

* your process design contains a large number of loops or tasks.
* you have long running processes, whose task count may get large even though
  the process isn't running away.

If you set a high value, your BPM system could stall if process instances reach
a runaway state, as it will take time to reach the threshold.  If you know your
task per instance count you may wish to set the threshold to a lower value.

NOTE: When this Hotfix has been applied to a BPM system, the count for all
existing process instances starts from 0 - so a process instance will only halt
if the number of tasks created after the Hotfix has been applied reaches the
threshold value.

WRM-9110 (CN-00740153 / SR-723447)
----------------------------------
An attempt to cancel a number of process instances failed if those process
instances contained large numbers of child instances (either sub-process
instances or user tasks). This occurred because the time taken to process the
cancellation exceeded a transaction timeout value, causing the transaction to
roll back. To resolve this problem, cancellation requests are now processed in
batches.

NOTE: The batch size defaults to 100, and can be configured using the
com.tibco.bx.maxCancelChildrenBatchSize JVM property. Do NOT change the value of
this property unless you are advised to do so by TIBCO Support.

WRM-8878 (CN-00807167 / SR-651541)
---------------------------------
Correlation messages were sometimes not being processed correctly when using
asynchronous Send/Receive tasks, even though the correlation id and correlation
data were identical.

WRM-8875 (CN-00807238 / CN-00778329)
------------------------------------
Correlation processing sometimes failed when one or more receivers, matching
the correlation data, referenced non-existent tasks or processes. The BPM
runtime now:
- checks for valid tasks referenced in waiting rows of the
  PVM_MSG_WAITING_RECEIVER BPM database table.
- provides extra information on INFO level logging messages.
- writes a WARN level logging message if a matching receiver is found with a
  non-existent task or process.

WRM-8874 (CN-00779900 / SR-656450)
----------------------------------
In Openspace, when listing migration rules, sometimes an exception was thrown -
for example:

   at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.
   NullPointerException at com.tibco.bx.management.BxManager.
   listMigrationRules(BxManager.java:4244) ...

This happened because, although the migration versions existed, information
about the migration versions was not complete. Now, any missing data is skipped
and themigration rules display. Any warnings about invalid rows are written to
the BPM log file.

WRM-8847 (CN-00722013 / SR-675017, CN-00717059 / SR-672597, CN-00721737 /
SR-674952)
------------------------------------------------------------------------------
When publishing BPM audit date to an external Enterprise Message Server (EMS),
connections were kept open indefinitely. This caused the number of EMS message
producers to keep increasing, eventually causing a resource leak.

WRM-8832 (CN-00779950 / SR-656630)
----------------------------------
An exception occurred when processing catch tasks for a specific throw event in
a process, if one or more of the catch tasks did not exist. Now, if any of the
catch tasks do not exist, they are skipped and the task continues processing as
normal. Any warnings about missing catch tasks are written to the BPM log file.

WRM-8876 (CN-00808116  / SR-655441)
-----------------------------------
In certain circumstances, attempting to resume a HALTED process instance
resulted in the process incorrectly going into a FAILED state. This meant
that you could not attempt another resume.

WRM-8793 (CN-00778329 / SR-651342, CN-00807238 / SR-651828)
-----------------------------------------------------------
For correlation processing, the BPM runtime now provides additional information
on INFO level logging messages to show how many matching receivers have been
found for the correlation data. For example:

   [INFO] - {BX_FOUND_WAITING_RECEIVERS_NUMBER} - Found [3] waiting receiver(s)
   for...
   ...
   [INFO] - {BX_FOUND_WAITING_RECEIVERS_NOTIFIED} - Waiting receiver has been
   notified for ID=pvm:001iap PID=204 ...
   ...

WS-1745
-------
When using the Workspace filter tool to define filters, if you entered a value
in the attribute edit mask, then clicked the button to add the expression to the
filter, nothing happened. This only happened when using Google Chrome - all
other browsers properly added the expression.

WS-1740
-------
In Workspace, a user defined as the recipient for multiple system views was only
seeing one system view (or no system views) in their view list, instead of all
the system views for which they were defined as a recipient. This problem
occurred when the recipient definitions for each system view pointed to a
different position in the organization model, but the names of those positions
were the same.

OS-3509 (CN-00723364 / SR-720563)
-------
When opening a work item, if the form's resource URL was from a different domain
to the hosting application's domain, the form failed to load.

TIBCO ActiveMatrix(R) BPM 3.0.0 Hotfix 004 is available

All Platforms

TIB_amx-bpm_3.0.0_HF-004_readme.txt