TIBCO ActiveMatrix(R) BPM 2.1.0 Hotfix 007 is available.
Article ID: KB0104701
Updated On:
| Products | Versions |
|---|---|
| TIBCO BPM Enterprise (formerly TIBCO ActiveMatrix BPM) | - |
| Not Applicable | - |
Description
Description:
Product Name : TIBCO ActiveMatrix(R) BPM
Release Version : 2.1.0_HF-007
Release Date : December 2013
================================================================================
Hotfixes are cumulative. This hotfix includes all previous generally available
hotfixes for TIBCO ActiveMatrix BPM 2.1.0. It includes the issues listed in the
Closed Issues section.
================================================================================
This hotfix applies to the following products and versions:
- TIBCO ActiveMatrix BPM 2.1.0, 2.1.0_HF-001 through 2.1.0_HF-006
================================================================================
Closed issues in 2.1.0_HF-007 (This Release)
BX-3002
Extend current user process priorities (100, 200, 300 or 400) to allow 100
to 400, inclusive. This applies to all four places where user process
priority may be set:
- In the Properties view for the process (the Priority configuration is on the
Work Resource properties tab)
- In the reusable sub-process activity Properties view (the Priority
configuration is in the Lifecycle section of the General tab)
- Process.priority JavaScript property
- setPriority() process management API operation
BX-3007
Gracefully recover the QueryProcessInstance API from queries that involve
instances that no longer exist (for example, instances that have just
completed when the query was issued).
BX-3009
Improve the performance of the database lock used for message correlation.
BX-3025
Update variable(set) exception in createProcessInstance could cause an open
transaction resulting in missing process instances in the database.
BX-3066:
Allow configuration to use priority integer value in event logging.
As it is now possible to set process priorities other than the ‘suggested set’
(Low=100, Normal=200, High=300 and Exceptional=400), a new Java system property
has been introduced that causes the priority integer value (100,101,...399, 400)
to be used in the process audit log entries:
com.tibco.bx.showExtendedPriorities="yes"
To change the com.tibco.bx.showExtendedPriorities Java system property,
do the following in Administrator (a restart of the node is required as part
of the process):
1. Navigate to a nodes list.
2. Select the BPM Node. The node details display in the General tab.
3. Click the Configuration tab.
4. Click the JVM Configuration link.
5. The JVM arguments are displayed.
6. Click on Add and enter com.tibco.bx.showExtendedPriorities with value yes
7. Click Install or Sync.
8. Restart the node.
If this property is not configured (the default, or set to "no"):
* Existing process applications will continue to function unchanged in respect
to audit logging. (The audit log will use the textual terms LOW, NORMAL, HIGH,
EXCEPTIONAL as appropriate.)
* For changed/new process applications that use priority values outside of the
'suggested set', a new textual term is used in the audit log, CUSTOM(value).
If one of the ‘suggested set’ of values is used then the original textual term
is used.
FORM-6128
Locale change event fails with an error when the form has deferred, rendered
panes that are not rendered.
FORM-6150
Disabled Multi-Select OptionList does not render correctly in Internet Explorer.
FORM-6153
Bindings, computation actions and APIs on controls inside a deferred, rendered
pane throw an exception if the event occurs before the control is
rendered.
FORM-6199
Custom controls are not refreshed when inherited properties are updated.
FORM-6170
When the value in the drop down list is changed using the arrow keys (up & down),
the corresponding update events don’t get fired appropriately.
OS-1484
Deliver Openspace API as part of 2.0.0_HF-003.
OS-1967
Currently Openspace sorts on the date fields in the Work Views gadget using string
comparison which gives incorrect results.
OS-1971
To implement a reusable AuthenticationHandler where in case of successful login,
callback method 'launchApp' will be called. If login is unsuccessful, the
callback 'displayLogin' is called. The authentication handler supports three
modes of authentication which is also standard in case of the Openspace client:
- value=0 means use the existing session authentication (if any)
- value=1 means invalidate session and present login panel on reload
- value=2 means always present login panel
The default value is 1.
OS-1974
The dates displayed in the Openspace Work Views gadget should match the format
for the selected locale.
WRM-5808
Trying to filter work items on strings containing the literal single quote
character results in an exception.
WRM-5829
Improve performance by not storing work item offer sets during an allocate if
they were generated from RQL.
WRM-5843
The SecurityService APIs do not have any System Action checks because they are
all protected by the "userAdmin" System Action.
The following Security Service methods now require the user to have rights for
the System Action "userAdmin". By default this System Action allows all users
access.
- authenticateUser
- getUserPrivileges
- isActionAuthorised
- listActionAuthorisedEntities
- listAuthorisedOrgs
WRM-5825
The EntityResolverPrivateService API methods describeEntity, getNamedResource and
validateEntity all use the System Action resolveResource to test authorisation.
For example, the caller should always be able to call describeEntity to return
their own records.
However, the three named services do not currently work introspectively. This
prevents a user from viewing their own work-list unless they have general rights
to perform "resolveResource".
WRM-5901
Push Destinations incur a performance penalty even if they are not being used. To
alleviate this, introduce two new directory engine properties to allow push
destination processing to be switched off throughout directory engine, or just for
resources (leaving other Organizational Entities enabled). The default is the
current behavior (process push destinations on all entity types). The two
properties are DisableAllPushDestinations and DisablePushDestinationsForResources.
If the properties are set to 'true', read operations will be 'silent' and not
return any push destination data, even if it currently exists. Write operations
will throw an (existing) service fault.
For the executeQuery operation in Resource Query Service the database look-up, for
push-destination information, will be in a batch method, rather than queried one
resource at a time. This improves the performance when push-destinations are enabled.
An existing property, SqlBatchSize(default 50) determines the batch sizing.
The specific impacted services (APIs) are:
Exporter Service (import and export)
Org Model Service (getOrgModel, updatePushDestinations)
Entity Resolver Private Service (validateEntity and resolveResource)
Attribute Service (getPushDestinations and setPushDestinations)
Resource Query Service (executeQuery)
Org Resource Service (getResource and updateResource)
WRM-5915
A chaining pattern can have many branches all running concurrently in the process.
From the perspective of the chain pattern any work item scheduled in the chain
group can and will be chained on regardless of which branch it comes from.
For this reason, when a new item in a chain is scheduled, even if it cannot be
directly allocated to the last completing resource in the chain group, the system
waits to see if more items are scheduled rather than break the chain. This can
cause delays in the client with forms waiting 10 seconds before closing the case
where no further items exist in the chain.
A common use case for this is the "Chain where possible" implementation of the
pattern. For example, suppose there are three successive user tasks, the first
and last being offered to a "Users" group and the middle being offered to a
"Managers" groups. If a resource belongs to both groups and executes the chain
they will get all three items chained on. If a user who only belongs to the
"Users" groups executes the chain then it will break at step 2. In this
scenario the form currently waits for 10 seconds before closing, waiting for
another item in the chain that will never arrive.
A new Boolean property (called breakChainWhenNoAllocate) in the brm.properties
file sends a "The chain has broken" notification if the first item it receives
for a chain cannot be "Chained on" (i.e. allocated to the last
user that completed and item in the chain). When set to true (not the default
value) the user will see the form close almost immediately when the next item
in the chain cannot be allocated to the same user.
WS-1372
The EntityResolverPrivateService API methods describeEntity, getNamedResource and
validateEntity all use the System Action resolveResource to test authorisation.
For example, the caller should always be able to call describeEntity to return
their own records.
However, the three named services do not currently work introspectively. This
prevents a user from viewing their own work-list unless they have general rights
to perform "resolveResource".
WS-1377
When the View Wizard is opened, there is a long delay before the options to create
a User or System view are displayed. This delay is more pronounced when there are
many resources defined on the system.
WS-1379
When a sub-process is expanded, in the Events list, the nested list of sub-process
events are not sorted and are in the order that they were received from the server.
A means for defining the sort order of the sub-process events is needed.
======================================================================
NOTE: See attached Readme document for installation instructions and issues resolved in previous hotfix releases.
================================================================================
The TIBCO ActiveMatrix(R) BPM 2.1.0 Hotfix 007 can be downloaded from our support-ftp.tibco.com. You will be able to download by clicking on the link below after you provide your TIBCO Support Web username and password in the url:
ftp://username:password@support-ftp.tibco.com
Directory path:
available_downloads/ActiveMatrixBPM/ActiveMatrixBPM/2.1.0/hotfix007
================================================================================
Product Name : TIBCO ActiveMatrix(R) BPM
Release Version : 2.1.0_HF-007
Release Date : December 2013
================================================================================
Hotfixes are cumulative. This hotfix includes all previous generally available
hotfixes for TIBCO ActiveMatrix BPM 2.1.0. It includes the issues listed in the
Closed Issues section.
================================================================================
This hotfix applies to the following products and versions:
- TIBCO ActiveMatrix BPM 2.1.0, 2.1.0_HF-001 through 2.1.0_HF-006
================================================================================
Closed issues in 2.1.0_HF-007 (This Release)
BX-3002
Extend current user process priorities (100, 200, 300 or 400) to allow 100
to 400, inclusive. This applies to all four places where user process
priority may be set:
- In the Properties view for the process (the Priority configuration is on the
Work Resource properties tab)
- In the reusable sub-process activity Properties view (the Priority
configuration is in the Lifecycle section of the General tab)
- Process.priority JavaScript property
- setPriority() process management API operation
BX-3007
Gracefully recover the QueryProcessInstance API from queries that involve
instances that no longer exist (for example, instances that have just
completed when the query was issued).
BX-3009
Improve the performance of the database lock used for message correlation.
BX-3025
Update variable(set) exception in createProcessInstance could cause an open
transaction resulting in missing process instances in the database.
BX-3066:
Allow configuration to use priority integer value in event logging.
As it is now possible to set process priorities other than the ‘suggested set’
(Low=100, Normal=200, High=300 and Exceptional=400), a new Java system property
has been introduced that causes the priority integer value (100,101,...399, 400)
to be used in the process audit log entries:
com.tibco.bx.showExtendedPriorities="yes"
To change the com.tibco.bx.showExtendedPriorities Java system property,
do the following in Administrator (a restart of the node is required as part
of the process):
1. Navigate to a nodes list.
2. Select the BPM Node. The node details display in the General tab.
3. Click the Configuration tab.
4. Click the JVM Configuration link.
5. The JVM arguments are displayed.
6. Click on Add and enter com.tibco.bx.showExtendedPriorities with value yes
7. Click Install or Sync.
8. Restart the node.
If this property is not configured (the default, or set to "no"):
* Existing process applications will continue to function unchanged in respect
to audit logging. (The audit log will use the textual terms LOW, NORMAL, HIGH,
EXCEPTIONAL as appropriate.)
* For changed/new process applications that use priority values outside of the
'suggested set', a new textual term is used in the audit log, CUSTOM(value).
If one of the ‘suggested set’ of values is used then the original textual term
is used.
FORM-6128
Locale change event fails with an error when the form has deferred, rendered
panes that are not rendered.
FORM-6150
Disabled Multi-Select OptionList does not render correctly in Internet Explorer.
FORM-6153
Bindings, computation actions and APIs on controls inside a deferred, rendered
pane throw an exception if the event occurs before the control is
rendered.
FORM-6199
Custom controls are not refreshed when inherited properties are updated.
FORM-6170
When the value in the drop down list is changed using the arrow keys (up & down),
the corresponding update events don’t get fired appropriately.
OS-1484
Deliver Openspace API as part of 2.0.0_HF-003.
OS-1967
Currently Openspace sorts on the date fields in the Work Views gadget using string
comparison which gives incorrect results.
OS-1971
To implement a reusable AuthenticationHandler where in case of successful login,
callback method 'launchApp' will be called. If login is unsuccessful, the
callback 'displayLogin' is called. The authentication handler supports three
modes of authentication which is also standard in case of the Openspace client:
- value=0 means use the existing session authentication (if any)
- value=1 means invalidate session and present login panel on reload
- value=2 means always present login panel
The default value is 1.
OS-1974
The dates displayed in the Openspace Work Views gadget should match the format
for the selected locale.
WRM-5808
Trying to filter work items on strings containing the literal single quote
character results in an exception.
WRM-5829
Improve performance by not storing work item offer sets during an allocate if
they were generated from RQL.
WRM-5843
The SecurityService APIs do not have any System Action checks because they are
all protected by the "userAdmin" System Action.
The following Security Service methods now require the user to have rights for
the System Action "userAdmin". By default this System Action allows all users
access.
- authenticateUser
- getUserPrivileges
- isActionAuthorised
- listActionAuthorisedEntities
- listAuthorisedOrgs
WRM-5825
The EntityResolverPrivateService API methods describeEntity, getNamedResource and
validateEntity all use the System Action resolveResource to test authorisation.
For example, the caller should always be able to call describeEntity to return
their own records.
However, the three named services do not currently work introspectively. This
prevents a user from viewing their own work-list unless they have general rights
to perform "resolveResource".
WRM-5901
Push Destinations incur a performance penalty even if they are not being used. To
alleviate this, introduce two new directory engine properties to allow push
destination processing to be switched off throughout directory engine, or just for
resources (leaving other Organizational Entities enabled). The default is the
current behavior (process push destinations on all entity types). The two
properties are DisableAllPushDestinations and DisablePushDestinationsForResources.
If the properties are set to 'true', read operations will be 'silent' and not
return any push destination data, even if it currently exists. Write operations
will throw an (existing) service fault.
For the executeQuery operation in Resource Query Service the database look-up, for
push-destination information, will be in a batch method, rather than queried one
resource at a time. This improves the performance when push-destinations are enabled.
An existing property, SqlBatchSize(default 50) determines the batch sizing.
The specific impacted services (APIs) are:
Exporter Service (import and export)
Org Model Service (getOrgModel, updatePushDestinations)
Entity Resolver Private Service (validateEntity and resolveResource)
Attribute Service (getPushDestinations and setPushDestinations)
Resource Query Service (executeQuery)
Org Resource Service (getResource and updateResource)
WRM-5915
A chaining pattern can have many branches all running concurrently in the process.
From the perspective of the chain pattern any work item scheduled in the chain
group can and will be chained on regardless of which branch it comes from.
For this reason, when a new item in a chain is scheduled, even if it cannot be
directly allocated to the last completing resource in the chain group, the system
waits to see if more items are scheduled rather than break the chain. This can
cause delays in the client with forms waiting 10 seconds before closing the case
where no further items exist in the chain.
A common use case for this is the "Chain where possible" implementation of the
pattern. For example, suppose there are three successive user tasks, the first
and last being offered to a "Users" group and the middle being offered to a
"Managers" groups. If a resource belongs to both groups and executes the chain
they will get all three items chained on. If a user who only belongs to the
"Users" groups executes the chain then it will break at step 2. In this
scenario the form currently waits for 10 seconds before closing, waiting for
another item in the chain that will never arrive.
A new Boolean property (called breakChainWhenNoAllocate) in the brm.properties
file sends a "The chain has broken" notification if the first item it receives
for a chain cannot be "Chained on" (i.e. allocated to the last
user that completed and item in the chain). When set to true (not the default
value) the user will see the form close almost immediately when the next item
in the chain cannot be allocated to the same user.
WS-1372
The EntityResolverPrivateService API methods describeEntity, getNamedResource and
validateEntity all use the System Action resolveResource to test authorisation.
For example, the caller should always be able to call describeEntity to return
their own records.
However, the three named services do not currently work introspectively. This
prevents a user from viewing their own work-list unless they have general rights
to perform "resolveResource".
WS-1377
When the View Wizard is opened, there is a long delay before the options to create
a User or System view are displayed. This delay is more pronounced when there are
many resources defined on the system.
WS-1379
When a sub-process is expanded, in the Events list, the nested list of sub-process
events are not sorted and are in the order that they were received from the server.
A means for defining the sort order of the sub-process events is needed.
======================================================================
NOTE: See attached Readme document for installation instructions and issues resolved in previous hotfix releases.
================================================================================
The TIBCO ActiveMatrix(R) BPM 2.1.0 Hotfix 007 can be downloaded from our support-ftp.tibco.com. You will be able to download by clicking on the link below after you provide your TIBCO Support Web username and password in the url:
ftp://username:password@support-ftp.tibco.com
Directory path:
available_downloads/ActiveMatrixBPM/ActiveMatrixBPM/2.1.0/hotfix007
================================================================================
Issue/Introduction
TIBCO ActiveMatrix(R) BPM 2.1.0 Hotfix 007 is available.
Environment
Product: TIBCO ActiveMatrix BPM
Version: 2.1.0
OS:
--------------------
Attachments
Feedback
Yes
No
Powered by
