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/4.1.0/TIB_amx-bpm_4.1.0_hotfix001

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

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

Closed Issues in 4.1.0_HF-001 (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-9149 (SR-727733, SR-739785)
-------------------------------
When upgrading to ActiveMatrix BPM 4.1.0, the "Wait for empty queues" task
failed and an exception was written to the <CONFIG_HOME>\tct\bpmupgrade\
<timestamp>\logs\upgrade.bpm.log file. (This problem occurred when running the
"Upgrade ActiveMatrix BPM Instance Application" action from the TIBCO
Configuration Tool "Upgrade TIBCO ActiveMatrix BPM Instance" wizard, but
occurred only when upgrading a BPM system which used an Environment name other
than the default "BPMEnvironment".)

NOTE: This exception did not cause the upgrade to fail. The upgrade still
ompleted successfully with a "BUILD SUCCESSFUL" message.

WRM-9141 (SR-737365)
--------------------
Invoking a business process from a business service failed if the payload
contained an array type that referenced a BOM. The following error was written
to the BPM log file:

   "The processing instruction target matching "[xX][mM][lL]" is not allowed."

WRM-9138 (SR-721900)
--------------------
A sub-process that invoked a service task remained in "Completing" status even
though it had finished, causing the parent process to wait indefinitely. A race
condition could occur on the process instance invoking the service task, making
it appear to the parent process that the sub-process instance had not completed.
(This problem occurred only if the service task was very short-lived - for
example, a task that simply executed a script.)

WRM-9091 (SR-718742)
--------------------
Global signal tasks that used mapping scripts to access case data failed at
runtime. The mapping failed and the following error was written to the BPM
log file:

   Caused by: com.tibco.bds.services.SecurityFault: API authorization failed
 
WRM-9064 (SR-706435)
--------------------
If the LDAP connection used by a dynamic organization model extension point was
not available when the extension point was processed, that extension point was
incorrectly deleted. As a result, work items were sent to the Undelivered group
instead of to their intended recipients.

Note: The extension points were deleted even though the following properties
were set in the <CONFIG_HOME>\bpm\<bpm_app_name>\configuration\de.properties
file:

   - ExtensionPointDeleteEnabled=false
   - ExtensionPointProcessEnable=true
 
WRM-9053 (SR-705903)
--------------------
Upgrading ActiveMatrix BPM from version 2.1 to version 4.1 failed at the
"Restarting BPM Nodes" step of the "Upgrade ActiveMatrix BPM Instance
Application" configuration action. The following error was written to the
<CONFIG_HOME>\tct\bpmupgrade\<timestamp>\logs\upgrade.bpm.log file:

   {EC_LIFECYCLE_STARTUP_ERROR} - Start-up Process failed!

This error occurred because the upgrade process did not find a

   <messageIds>
   </messageIds>

block in the <CONFIG_HOME>\bpm\<bpm_app_name>\configuration\ec-probe-rules.xml
file. (This code block had been commented out before upgrading.)

WRM-9022 (SR-700751, SR-698038, SR-690958)
------------------------------------------
On ActiveMatrix BPM version 3.1.0_HF-003, deployment of an application
containing a WSDL failed, if the WSDL contained an inline "urn" namespace
schema that referred to another "urn" namespace schema in the same WSDL.
This problem affected both new applications, and applications migrated from
earlier vesions of ActiveMatrix BPM - even where that application had worked
correctly in the earlier version and the WSDL had not been changed.

WRM-8988 (SR-692454, SR-724555)
-------------------------------
Using the Case Data Query Language (DQL) findByCriteria method in a script to
search for case objects by criteria failed at runtime. The following error was
written to the BPM log file:

 [ERROR] com.tibco.bds.core.services.impl.BusinessDataServicesPrivateServiceImpl
 - [ERROR] - {BDS_GLOBAL_DATA_FIND_BY_CRITERIA_FAULT} - Fault while attempting
 to find BDS Class using Criteria...

This error occurred when performing a search against an enumeration attribute,
and occurred only if the case data model referenced by the search was very
large.

WRM-8954
--------
When using the allocateAndOpenNextWorkItem operation (from the
WorkItemManagementService in the BPM web service API), you can use the optional
workListViewId parameter to get a work view for the next work item. If multiple
calls used the same workListViewId parameter this could result in performance
degradation.
 
WRM-8919 (SR-681839)
--------------------
If a push destination for a user (resource) was mapped to a resource attribute,
which was in turn mapped to the attributes of an LDAP entity, a
DE_INTERNAL_SERVICE_FAULT error would occur when retrieving the push
destinations for that resource if the mapped LDAP entity no longer existed.
For example, this error could occur:

- in Workspace, if you clicked a position in the Organization Browser
  (to retrieve the details of all users mapped to that position).
- in the ActiveMatrix BPM web service API, when using the ExecuteQuery operation
  from the ResourceQueryService.
 
WRM-8914 (SR-722510)
--------------------
When using an Oracle database version, upgrading to ActiveMatrix BPM version 4.1
failed. The following error:

   ORA-00955: name is already used by an existing object

occurred when running the <CONFIG_HOME>\bpm\<BPMApplicationName>\database\
WorkManagerUpgrade.sql script (either manually, or when running the TIBCO
Configuration Tool "Upgrade TIBCO ActiveMatrix BPM Instance" wizard, as part of
the "Upgrade ActiveMatrix BPM Instance Application" action).

WRM-8806 (SR-661221, SR-666985)
-------------------------------
Process data was not displayed in the Audit Trail in Openspace when auditing of
process data was enabled. This occurred if only structured (BOM) data fields
were mapped to audit event data attributes. In this case, the values of the
audit event data attributes were not populated to the EC_PE_STATUS table in the
ActiveMatrix BPM database. If at least one simple data field was mapped to an
audit event data attribute, the problem did not occur.

WRM-8401 (CN-00767668, SR-610201)
---------------------------------
Installing ActiveMatrix BPM Developer Server on a Linux environment failed if an
ActiveMatrix BPM Hotfix was also applied, because TIBCO Configuration Tool was
incorrectly trying to register the host as a Windows service.

WBPM-938 (CN-00725332, SR-726455)
---------------------------------
In the Case Management application, linked cases did not display. (This problem
occurred if the case reference had an array of associations with other cases.)

WBPM-928
--------
In the Client Application Framework, the <bpm-case-actions> business component
now provides a "case-action-success" attribute:

   <bpm-case-actions
      case-ref="String"
        case-action-success="Function reference"
      [template-path="String"]>
   </bpm-case-actions>
   
The "case-action-success" attribute is optional. You can use it to define the
actions to be performed when the user selects one of the displayed case actions.

See "Business Components > Business Components Reference > bpm-case-actions" in
the TIBCO ActiveMatrix BPM Client Application Developer's Guide more
information.)

WBPM-927 (CN-00719596, SR-708182)
---------------------------------
In the Client Application Framework, all business components now support the use
of custom HTML templates.

(You specify the location of a custom template when you invoke a business
component, using the component's "template-path" attribute. See "Business
Components > Customizing a Business Component" in the TIBCO ActiveMatrix BPM
Client Application Developer's Guide more information.)

WBPM-925 (CN-00722535, SR-718011)
---------------------------------
The Case Management application failed to display the list of case instances
for a case type when there were a large number of available case instances
(around 80 or more). Instead, an error dialog was displayed, containing the
message "Request-URI Too Large".

WBPM-923
--------
In Application Management, an updated and enhanced version of the Case
Management application is provided. The updated version replaces the original
version of the Case Management application.

When you click one of the available Cases, the new version of the application
displays the <bpm-case-details-page> business component, which provides
case-specific information and options using a main pane and a right-hand
sidebar. (The original version of the application used a "Case Menu", coded
directly in the application's index.html file, to provide similar case-specific
information and options.

For more information about the application and the <bpm-case-details-page>
business component, see "Case Management Application" in the "TIBCO ActiveMatrix
BPM Client Application Developer's Guide", available from:

https://docs.tibco.com/pub/amx-bpm/4.1.0/doc/html/bpmhelp/
GUID-4C1DB190-CF2E-4926-8CBE-B6828E740CF3.html

NOTE: This updated version of the Case Management application was previously
provided as a separate sample application
(TIB_amx-bpm_4.1.0_CaseManagementApp.zip), available as part of the TIBCO
ActiveMatrix BPM Software (v 4.1.0) component on the TIBCO eDelivery site
(https://edelivery.tibco.com).

WBPM-722
--------
In the Workapp sample application, comments showing the use of individual
business components specified the wrong path for the "template-path" attribute.

WBPM-721
--------
In Application Management, when you tried to launch a cloned application it
failed with an HTTP "404 NOT FOUND" error. This error would occur if, when
cloning the application, you used a space character (' ') in the new
application's name.

WBPM-562
--------
You can dynamically change the logging level used by Application Management
when it writes messages to the BPM log file:

1. In Application Management, click Settings then expand "Debug Settings".

2. Set your chosen log level for each Application Management package. (Hover
   over the package name for a description of the package.)

3. Click "SAVE CHANGES".

WS-1743 (CN-01245846)
---------------------
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.