Product Name: TIBCO ActiveMatrix(R) BPM
Release Version: 4.1.0_HF-008
Release Date: November 2018

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

Closed Issues in 4.1.0_HF-008 (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-11010 (CN-01646233)
-----------------------
Following an upgrade of ActiveMatrix BPM to version 4.1, cancelling a
sub-process caused the parent process to fail (instead of halting). This error
only occurred when cancelling a process instance that already existed on the
previous version of the ActiveMatrix BPM system. Process instances created after
the upgrade were not affected.

The following error was written to the BPM log file when the main process
instance failed:

   java.lang.NullPointerException
       at com.tibco.pvm.infra.api.impl.finder.IpmObjectFinder.findObject
       (IpmObjectFinder.java:93)
   
WRM-11006
---------
An attempt to deploy a new minor version of a process application failed because
a change to the application's service interface was incorrectly detected when no
such change had been made. See also XPD-8431 and XPD-8434.
   
WRM-10806 (CN-01611384)
-----------------------
A StackOverFlowError occurred when trying to submit a work item. (This error
occurred when the data being passed to a pageflow did not match the underlying
BOM.)

WRM-10778 (CN-01621677)
-----------------------
When a resource attribute was mapped to an LDAP attribute for which an LDAP
entry had no settings (not even null), a null pointer exception occurred if an
RQL query evaluation encountered that LDAP entry.

WRM-10776 (CN-01612932)
-----------------------
A new ec_delete_case_audit_<db>.sql stored procedure is provided in
<CONFIG_HOME>\bpm\<bpm_app_name>\<database>\ec. You can use this stored
procedure to delete audit entries associated with case data from the BPM
database (the entries in the ec_event_int and ec_case_status tables).

   ec_delete_case_audit Stored Procedure Parameters
   ------------------------------------------------
   
   ec_delete_case_audit (end_time, max_cases, batch_size, dbg)
   
   where:
   
   * end_time - is the date, in 'dd-mmm-yy' format, up to which audit entries
     should be deleted. (Default = null = delete ALL entries). For example, a
     value of '01-AUG-18' deletes entries that are older than 1st August 2018.
   
   * max_cases - is the maximum number of cases for which audit entries should
     be deleted. (Default = -1 = no limit)
   
   * batch_size - is the number of cases for which audit entries should be
     deleted before performing a commit. (Default value = 100)
     
   * dbg - switches debug mode on or off. (Default = 'False' = Off) You should
     only set this flag when advised to do so by TIBCO Support.
       
NOTE: In earlier ActiveMatrix BPM versions, case data audit entries were removed
by the ec_delete_non_instance_audit_data_<db>.sql stored procedure, which meant
that they were removed only if all the process instance entries for the same
period had already been deleted. The ec_delete_case_audit_<db>.sql stored
procedure allows you to delete audit entries for case data independently,
whether or not the process instance entries for the same period have already
been deleted.

For more information about the related ec_delete_audit_stats_data_<db>.sql and
ec_delete_non_instance_audit_data_<db>.sql stored procedures, see "Clearing
Audit and Statistical Data for Process Instances" and "Clearing Audit and
Statistical Data Not Related to a Process Instance" in the ActiveMatrix BPM
Administration guide.

WRM-10775
---------
When defining an LDAP group source for an LDAP container (using either the
Organization Browser or the DirectoryService in the ActiveMatrix BPM public
API), a 'member' attribute must be specified. The 'member' attribute holds the
collection of member identifiers (DNs) that provides the list of candidate
resources. If the LDAP server is an Active Directory server, the 'member'
attribute name can be specified as a range query. However, if the query range
specified more entries than existed on the LDAP server, no candidate resources
were displayed.

For example, if the 'member' attribute name was defined as:

  member;range=0-1000
 
and the LDAP server contained more than 1000 matching entries, the list of
candidate resources was displayed correctly. If there were only 975 matching
entries, no candidate resources were displayed. (This error occurred because the
attribute name returned from the Active Directory server contained
"member;range=0-*", to indicate the end of the results. This did not match the
expected attribute name, so no results were returned.)

With this fix, the list of candidate resources is displayed correctly even if
the range specifies more entries than exist on the LDAP server.

WRM-10586 (CN-01571053, CN-01601320)
-------------------------------------
When automatically archiving event data, OutOfMemoryError exceptions could occur
in the BPM log file when large numbers of process instances were being
processed. For example:

  [ERROR] com.tibco.pvm.system.PvmSystem - Unexpected Error processing WorkItem
  java.lang.OutOfMemoryError: Java heap space

WRM-10577 (CN-01593230)
-----------------------
When passing a parameter value in a process instance, an empty string was
incorrectly changed to a null value. When using an Oracle database, this
sometimes resulted in the process instance failing.

WRM-10479 (CN-01601488)
-----------------------
Process instances were not moving to ACTIVE state after they had been started.
They remained stuck in STARTING state.

This problem occurred when the system contained large numbers of stuck process
instances, which are automatically assigned a low priority, and normal process
instances which were being started with low priority. Work was being selected  
for processing (from the PVM_REQUEST_QUEUE database table) based on priority,
with no distinction between the type of process instance. This could result in
significant delays in starting new process instances. With this fix, requests to
start new process instances are selected first, resulting in no (or minimal)
delay.

WRM-10423 (CN-01578540)
-----------------------
After upgrading from a 4.0 version of ActiveMatrix BPM to version 4.1.0_HF-002
(or to a later 4.1.0 Hotfix), warnings about missing process instances were
written to the BPM log file. For example:

  [WARN] com.tibco.n2.ec.core.triggers.ProcessHierarchy - Could not find
  instance [pvm:0a123f3e4l]!

These warnings occurred when the following process instances completed or were
cancelled:

* any process instance that was started on the version 4.0 system prior to the
  upgrade to version 4.1.
* any sub-process instance that was started on the upgraded version 4.1 system,
  but which had a parent process instance that was started on the version 4.0
  system.

Version 4.1.0_HF-002 introduced a change to the way that process instances
lifecycle events were recorded in the BPM database. As a result, these
particular process instances were not correctly recorded as completed in the
ec_managed_obj_lifecycle database table. This resulted in the warning message in
the BPM log file, and also meant that these instances could never be purged or
archived.

With this fix, a new amxbpm_set_lifecycle_root_ids migration script is provided
to resolve this problem. The script corrects the information held in the
ec_managed_obj_lifecycle table for affected process instances, meaning that they
can be subsequently purged or archived. Migration scripts are provided in the
<TIBCO_HOME>\bpm\4.1\scripts\migration\database folder. (See "Migrating Data
Stored in Event Collector", in the TIBCO ActiveMatrix BPM 4.1 Installation and
Configuration guide, for general information about using the migration scripts
with your particular database.)

You should run this script:

* after upgrading, if you see warnings about missing process instances in the
  BPM log file.
* before attempting to purge completed and cancelled process instances.
* periodically, if you want to archive audit data about completed and cancelled
  process instances.

NOTE: You may need to run the script repeatedly, until all process instances
that were started on the version 4.0 system have completed or been cancelled.

To run the amxbpm_set_lifecycle_root_ids migration script:

1. Run install-migration-tools.sql to install the stored procedures and create
   the ec_migration table.

2. Run the amxbpm_set_lifecycle_root_ids stored procedure.

   amxbpm_set_lifecycle_root_ids Stored Procedure Parameters
   ---------------------------------------------------------
   
   amxbpm_set_lifecycle_root_ids (batch_size, max_updates)
   
   where:
   
   * batch_size - is the number of rows to update before performing a commit.
   
   * max_updates - is the maximum number of updates to perform before exiting.
           
3. Run remove-migration-tools.sql to remove the migration tools.

WRM-10405 (CN-01580927, CN-01634816)
------------------------------------
Process instances were failing (with null pointer exceptions) when checking for
pending correlation messages.  

WRM-10394 (CN-01574792)
-----------------------
In some circumstances, when a process instance was interrupted - for example, on
receiving a case data signal event, if a user task was completed at the same
time that the process instance was resumed, the process instance became stuck
and did not continue to the next task in the business process.

WRM-10345 (CN-01566830)
-----------------------
Upgrading to ActiveMatrix BPM version 4.1.0 failed when starting the
ActiveMatrix BPM application. 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 removed or commented out before upgrading.)

WRM-10339 (CN-01567925)
-----------------------
ActiveMatrix BPM uses a Resource Query Language (RQL) expression algorithm to
evaluate all RQL queries - that is, queries that originate from Dynamic Process
Participants, Performer Fields, as well as queries submitted via the
ActiveMatrix BPM public API (using the executeQuery operation in the
ResourceQueryService).

ActiveMatrix BPM 4.1.0 HF-8 introduces a new version of the RQL expression
algorithm that translates RQL expressions into SQL, resulting in much faster RQL
expression processing than using the original, in-memory method. A new
'ResourceQueryVersion' configuration parameter is provided, which specifies the
version of the algorithm to be used. If:

* ResourceQueryVersion=1: (Default) Resolves RQL expressions in memory.

* ResourceQueryVersion=2: Translates the RQL expression to SQL.

To enable use of the new version of the algorithm, add the following entry to
the <CONFIG_HOME>\bpm\<bpm_app_name>\configuration\de.properties file:

     ResourceQueryVersion=2

NOTE: RQL queries that originate from Dynamic Process Participants or Performer
Fields are registered in the BPM database. If you subsequently decide to revert
to version 1 of the RQL expression algorithm, you must use the resetQueries
operation in the ResourceQueryService of the ActiveMatrix BPM public API to
reset these queries. (ActiveMatrix BPM does not provide a user interface to
perform this operation.) The amount of time it takes to reset the queries in the
database depends on the complexity of the expressions, and the size of the
result set - but it could be hours. While that processing is taking place, RQL
result sets are based on the previous expression evaluation. See the TIBCO
ActiveMatrix BPM Developer's Guide for more information about the resetQueries
operation.

WRM-10269 (CN-01563523)
-----------------------
When Statistics Collector was processing events, a race condition could result
in large numbers of 'unique constraint (<constraintName>) violated' database
errors being written to the BPM log file.

WRM-10223
---------
A new <TIBCO_HOME>\bpm\<version>\bin\rulesinfo utility is provided, which
can be used to show, validate or test proposed modifications to the event
processing rules that are defined in the event probe and event rules files
(ec-probe-rules.xml and ec-event-rules.xml).

See "Using the rulesinfo Utility to Validate the Event Probe and Event Rules
Files" in this Readme for more information about this utility and how to use it.

WRM-10205 (CN-01557165)
-----------------------
The ec_delete_audit_stats_data_<db>.sql and
ec_delete_non_instance_audit_data_<db>.sql scripts (used to delete audit
entries and statistical data for process instances) did not delete data that had
been archived.

WRM-10193
---------
A BX_INSTANCE_TASKS_COMPLETED event now also includes the time taken for the
task to complete.

WRM-10163 (CN-01555743)
-----------------------
When attempting to deploy a global signal application on an ActiveMatrix BPM
system with 4.0.0 HF-003 applied, deployment failed with a (class cast)
exception.

WRM-10157 (CN-01553310)
-----------------------
When upgrading a global signal definition project to a new minor version,
deployment succeeded even though the project contained a parameter which had
been changed from mandatory to optional. (This is an invalid change for a minor
version - if you want to change a mandatory field to an optional one, you must
deploy a new major version of the project.) This resulted in a runtime error
when the global signal was called.

With this fix, a deployment error occurs if you attempt to upgrade a global
signal definition project to a new minor version when a mandatory parameter has
been removed or changed to optional.

WRM-9398 (CN-01446119, CN-01455654, CN-01449993, CN-01557047)
-------------------------------------------------------------
Changing the value of the pe.engineThreadCount substitution variable (on the BPM
application) to set the number of threads in the Process Engine background
thread pool had no effect. Whatever the value of pe.engineThreadCount, the
number of process engine threads remained at the default value (5).

NOTE: This problem did not occur if you used TIBCO Configuration Tool to set the
number of threads (using the "Number of Process Engine Threads" field in the
ActiveMatrix BPM: Sizing Configuration panel of the Create TIBCO ActiveMatrix
BPM Server wizard).

WRM-9355 (CN-01445771)
----------------------
A catch signal event pointing to case data stopped working. (It had been working
fine and there had been no recent changes to the system.)

WRM-9244 (CN-01251784, CN-01249908)
-----------------------------------
After upgrading from a pre-4.0 version of ActiveMatrix BPM, no process
definitions were visible when trying to create a new Process View in Workspace.

WRM-9020 (CN-00733773)
----------------------
A process containing a call to a sub-process, with invocation mode configured as
"Asynchronous Attached", was not being purged when both the process and
sub-process had completed.

WBPM-1390 (CN-01590188)
-----------------------
When using French locale, the implicit validation message provided by the
'validation_pattern' resource key:

  ''{0}'' has the wrong format for the ''{1}'' data type

did not display correctly on the form. For example:

  Le format de 'Code Postal:' n'est pas bon pour le type de données {1}'

The {1} parameter was not replaced by the text identifying the data type. (This
error occurred as a result of an incorrectly escaped single quote in the
common_fr_XX.properties file.)
 
WBPM-1368 (CN-01600017)
-----------------------
When using the Case Management application, a text field containing multiple
lines (separated by CRs) was incorrectly displayed as a single line in a form.
Now, the field is rendered correctly as multiple lines of text.

WBPM-1356 (CN-01591037)
-----------------------
In the Organization Browser, when defining an LDAP group source for an LDAP
container, clicking 'Show sample of LDAP Entities' sometimes returned no
candidate resources even though those resources existed on the LDAP server.
This problem only occurred when using an Active Directory server configured to
use a range query on the 'member' attribute. (The 'member' attribute holds the
collection of member identifiers (DNs) that provides the list of candidate
resources. If the query range specified more entries than existed on the LDAP
server, no candidate resources were displayed. See WRM-10775 for more
information.)

With this fix, the list of candidate resources is displayed correctly even if
the range specifies more entries than exist on the LDAP server.

WBPM-1333 (CN-01562785)
-----------------------
On a form, when sorting data in a grid pane, rows containing empty values were
not sorted correctly. They remained mixed in with other values instead of
appearing either at the top or bottom of the sorted data. (This error occurred
only when sorting after new rows with empty values had been added.)
 
WBPM-961
--------
In the Workapp sample application, some comments showing the use of individual
business components specified the wrong path for the "template-path" attribute.

WBPM-960
--------
In Application Management, changes made to a cloned application were not
published. (When you launched the published application the original version,
without the changes, would be launched.) This error would occur if, when
cloning the application, you used a space character (' ') in the new
application's name.

WBPM-733
--------
A custom client application displayed invalid date formatting on a work item, if
the target date set for that work item was greater than or equal to the current
date.

WS-1838 (CN-01640405)
--------------------
In Workspace, when using the case view wizard to edit an existing case view:

* the case class that was initially selected when creating the case view was not
  selected.
* the Finish button was enabled, but clicking it did nothing.

OS-3570 (CN-01574257)
---------------------
When using the Organization Browser, an attempt to fetch LDAP attributes for an
LDAP container failed if a CN entry in the LDAP contained a comma character ",".
(This resulted in an error in the URL used by the ActiveMatrix BPM REST API call
used to fetch LDAP attributes.)

OS-3567
-------
When using the Case Management application, a text field containing multiple
lines (separated by CRs) was incorrectly displayed in a form as a single line
containing the string:

   #text
   
Now, the field is rendered correctly, showing the intended content as multiple
lines of text. For example:

   Text on line 1 <CR>
   Text on line 2 <CR>
   Text on line 3

XPD-8434 (CN-01256803)
----------------------
An attempt to deploy a new minor version of a process application failed because
a change to the application's service interface was incorrectly detected when no
such change had been made. (This error only occurred following an upgrade of
ActiveMatrix BPM to version 4.1, if the existing version of the process
application was deployed on the previous version of the ActiveMatrix BPM system.
The error occurred because, on an upgrade, the WSDL Comparator unnecessarily
prevented the addition of new, incoming request activities for an existing WSDL
message.)

Deployment failed with an error like this:

   TIBCO-AMX-ADMIN-012428: A change in interface was detected for application
   service 'ExampleAppEP_Provider'. Any change in the interface must be exposed
   as a separate service. Please refer to details. Contents of Definition do not
   match.  

   Correlation set for Message '{http://example.com/example/}ExampleRequest' has
   changed.
   
XPD-8431 (CN-01644536)
----------------------
An attempt to deploy a new minor version of a process application failed because
a change to the application's service interface was incorrectly detected when no
such change had been made. (This error only occurred if the application
contained multiple receive tasks for the same web service operation.)

Deployment failed with an error like this:

   TIBCO-AMX-ADMIN-012428: A change in interface was detected for application
   service 'ExampleAppEP_Provider'. Any change in the interface must be exposed
   as a separate service. Please refer to details. Contents of Definition do not
   match.  

   Correlation set for Message '{http://example.com/example/}ExampleRequest' has
   changed.

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

Refer to the associated readme document for any additional information.