TIBCO ActiveMatrix® BPM 4.0 Release Notes

TIBCO ActiveMatrix® BPM Release NotesSoftware Release 4.0.0November 2015Document Updated: December 2015

Two-Second Advantage®

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCHEMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY(OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THEEMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANYOTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.

USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS ANDCONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTEDSOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THECLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOADOR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE)OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USERLICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THESOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, ANDYOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BEBOUND BY THE SAME.

This document contains confidential information that is subject to U.S. and international copyright lawsand treaties. No part of this document may be reproduced in any form without the writtenauthorization of TIBCO Software Inc.

TIBCO, Two-Second Advantage, TIBCO ActiveMatrix BPM, TIBCO Administrator, TIBCO BusinessStudio, TIBCO Enterprise Message Service, TIBCO General Interface, TIBCO Hawk, TIBCO iProcess,TIBCO JasperReports, TIBCO Spotfire, TIBCO Spotfire Server, and TIBCO Spotfire Web Player areeither registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or othercountries.

Enterprise Java Beans (EJB), Java Platform Enterprise Edition (Java EE), Java 2 Platform EnterpriseEdition (J2EE), and all Java-based trademarks and logos are trademarks or registered trademarks ofOracle Corporation in the U.S. and other countries.

All other product and company names and marks mentioned in this document are the property of theirrespective owners and are mentioned for identification purposes only.

THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOTALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASEDAT THE SAME TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWAREVERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM.

THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.

THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICALERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESECHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCOSOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S)AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.

THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY ORINDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE,INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.

Copyright © 2005-2015 TIBCO Software Inc. ALL RIGHTS RESERVED.

TIBCO Software Inc. Confidential Information

2

TIBCO ActiveMatrix® BPM Release Notes

Contents

TIBCO Documentation and Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Important Installation and Upgrade Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Core Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Application Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Client Application Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Work Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

TIBCO Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Openspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Deprecated and Removed Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Migration and Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Upgrading Pre-TIBCO ActiveMatrix BPM 2.2 to TIBCO ActiveMatrix BPM 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Upgrading TIBCO ActiveMatrix BPM 2.2 and Later to TIBCO ActiveMatrix BPM 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

TIBCO ActiveMatrix BPM Version 3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

TIBCO ActiveMatrix BPM Version 1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Initializers and Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Configuring the Business Data Services (BDS) Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Upgrade Script Issue with Openspace GlobalHubPolicy Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Upgrading the Oracle JDBC Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Openspace Upgrade Script and Data Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Workspace Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Core Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Work Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Process Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

TIBCO Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

Openspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55

Runtime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

TIBCO Hawk ActiveMatrix Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

3


Core Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Work Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Process Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

TIBCO Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75

Openspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

4


TIBCO Documentation and Support Services

Documentation for this and other TIBCO products is available on the TIBCO Documentation site:

https://docs.tibco.com

Documentation on the TIBCO Documentation site is updated more frequently than any documentationthat might be included with the product. To ensure that you are accessing the latest available helptopics, please visit https://docs.tibco.com.

Product-Specific Documentation

Documentation for TIBCO products is not bundled with the software. Instead, it is available on theTIBCO Documentation site. To directly access documentation for this product, double-click thefollowing file:

TIBCO_HOME/release_notes/TIB_amx-bpm_version_docinfo.html

where TIBCO_HOME is the top-level directory in which TIBCO products are installed. On Windows,the default TIBCO_HOME is C:\tibco. On UNIX systems, the default TIBCO_HOME is /opt/tibco.

The following documents for this product can be found on the TIBCO Documentation site:

● TIBCO ActiveMatrix BPM SOA Concepts● TIBCO ActiveMatrix BPM Concepts● TIBCO ActiveMatrix BPM Developer's Guide● TIBCO ActiveMatrix BPM Web Client Developer's Guide● TIBCO ActiveMatrix BPM Tutorials● TIBCO ActiveMatrix BPM Business Data Services Developer Guide● TIBCO ActiveMatrix BPM Case Data User Guide● TIBCO ActiveMatrix BPM Event Collector Schema Reference● TIBCO ActiveMatrix BPM - Integration with Content Management Systems● TIBCO ActiveMatrix BPM SOA Composite Development● TIBCO ActiveMatrix BPM Java Component Development● TIBCO ActiveMatrix BPM Mediation Component Development● TIBCO ActiveMatrix BPM Mediation API Reference● TIBCO ActiveMatrix BPM WebApp Component Development● TIBCO ActiveMatrix BPM Administration● TIBCO ActiveMatrix BPM Performance Tuning Guide● TIBCO ActiveMatrix BPM SOA Administration● TIBCO ActiveMatrix BPM SOA Administration Tutorials● TIBCO ActiveMatrix BPM SOA Development Tutorials● TIBCO ActiveMatrix BPM Application Management Guide● TIBCO ActiveMatrix BPM Client Application Developer's Guide● TIBCO Openspace User's Guide● TIBCO Openspace Customization Guide● TIBCO ActiveMatrix BPM Organization Browser User's Guide (Openspace)

5




● TIBCO ActiveMatrix BPM Organization Browser User's Guide (Workspace)● TIBCO ActiveMatrix BPM Spotfire Visualizations● TIBCO Workspace User's Guide● TIBCO Workspace Configuration and Customization● TIBCO Workspace Components Developer Guide● TIBCO ActiveMatrix BPM Troubleshooting Guide● TIBCO ActiveMatrix BPM Deployment● TIBCO ActiveMatrix BPM Hawk Plug-in User's Guide● TIBCO ActiveMatrix BPM Installation: Developer Server● TIBCO ActiveMatrix BPM Installation and Configuration● TIBCO ActiveMatrix BPM Log Viewer● TIBCO ActiveMatrix BPM Single Sign-On● Using TIBCO JasperReports for ActiveMatrix BPM

How to Contact TIBCO Support

For comments or problems with this manual or the software it addresses, contact TIBCO Support:

● For an overview of TIBCO Support, and information about getting started with TIBCO Support,visit this site:

http://www.tibco.com/services/support

● If you already have a valid maintenance or support contract, visit this site:

https://support.tibco.com

Entry to this site requires a user name and password. If you do not have a user name, you canrequest one.

How to Join TIBCOmmunity

TIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts. It is aplace to share and access the collective experience of the TIBCO community. TIBCOmmunity offersforums, blogs, and access to a variety of resources. To register, go to the following web address:

https://www.tibcommunity.com

6


http://www.tibco.com/services/support

https://support.tibco.com

https://www.tibcommunity.com

Important Installation and Upgrade Notes

To upgrade to TIBCO ActiveMatrix BPM 4.0, TIBCO ActiveMatrix Platform 3.3.0 Hotfix 11 ismandatory.

For more information on upgrade, see Upgrading Pre-TIBCO ActiveMatrix BPM 2.2 to ActiveMatrixBPM 4.0 and Upgrading TIBCO ActiveMatrix BPM 2.2 and later to TIBCO ActiveMatrix BPM 4.0

TIBCO ActiveMatrix® Binding Type for REST 3.3.0 HF01 is a minimum requirement if using RESTservice invocation tasks from BPM processes. This is required on runtime and design-time.

The following table lists a number of known issues in TIBCO ActiveMatrix Platform 3.3.0 that affectTIBCO ActiveMatrix BPM version 4.0. Contact TIBCO Support for up to date information on theseissues and their resolution.

Key Summary/Workaround

AMRP-5232 Summary: A form fails to load and an java.io.IOException: write beyondend of stream Error" error is reported. This error only occurs on systemswhere TIBCO ActiveMatrix Platform 3.3.0 Hotfix 10 has been applied, and iscaused by an HTTP compression issue.

Workaround: To avoid this problem, disable the use of HTTP compression bythe BPM runtime. To do this, add the following property:java.property.com.tibco.amf.hpa.tibcohost.jetty.disableCompression=true

to the CONFIG_HOME\tibcohost\Admin-enterpriseName-adminServerName\data_version\nodes\BPMnodeName\bin\BPMNode.tra file.

Support for this property was introduced in TIBCO ActiveMatrixPlatform 3.3.0 Hotfix 012.

AMX-15224 Summary: If you upgrade from TIBCO ActiveMatrix BPM version 2.1.0 toversion 4.0, the upgrade fails on the first attempt on the upgrade-admin step.

Workaround: Re-run the upgrade. The upgrade process completes successfully.

The following issues are resolved by TIBCO ActiveMatrix Platform 3.3.0 Hotfix 012, which you canobtain from TIBCO Support.

Key Summary

AMX-15212,SDA-451

Summary: On a system where TIBCO ActiveMatrix Platform 3.3.0 Hotfix 10 hasbeen applied, you cannot deploy a Decisions Service project from TIBCOBusiness Studio.

Workaround: Export the Decisions Service project as a DAA and deploy it fromActiveMatrix Administrator.

This issue is resolved by TIBCO ActiveMatrix Platform 3.3.0 Hotfix012.

7


Key Summary

AMX-15258 Summary: A process application containing a service task that calls a BPMservice (that is, invokes any public BPM API operation) may not work asexpected after upgrade to TIBCO ActiveMatrix BPM version 4.0. In somecircumstances, the application may not work at all.

Workaround: None.


AMX-15265 Summary: On a system where TIBCO ActiveMatrix Platform 3.3.0 Hotfix 10 hasbeen applied, upgrading TIBCO ActiveMatrix BPM to version 4.0 fails whenyou try to upgrade the ActiveMatrix BPM database. The following error isdisplayed:Error moving LDAP connections to the application: The max connection pool size is invalid. It can only allow a number OR a substitution variable.

(This error occurs because the upgrade sends a string value for the maxPoolSizeparameter for the sslServer resource template, but this value is now an integeras a result of a change in TIBCO ActiveMatrix Platform 3.3.0 Hotfix 10.)

Workaround: Before upgrading, use ActiveMatrix Administrator to change theMax Pool Size parameter for the sslServer resource template (type SSL ServerProvider) from Default to 20.


AMRP-5306 Summary: On TIBCO ActiveMatrix BPM version 4.0, .zip files or .pdf files thatare uploaded to the CMIS repository may be corrupted. Content is lost and thefiles cannot be opened if they are downloaded.

Workaround: None.


8


New Features

This release introduces new features for the following components:

● Core Components● Clients

Core ComponentsThis section describes the new features for Core Components.

Application ManagementA new Application Management user interface is available that is used to manage your ActiveMatrixBPM client applications.

With Application Management you can upload application files, edit the files, then test and verify yourchanges without having to deploy the complete application to an ActiveMatrix BPM server.

Using Application Management you can customize your applications, and make layout, markup andstyle sheet (CSS) changes.

Once you have verified your application, simply publish your application to make it availableimmediately to your users. Once your application is published, it automatically provides support fordevices, such as, Smart Phone, Tablet and PC. Once an application is published, you can dynamicallymodify it using Application Management.

A localization service enables you to provide one or more languages to applications that are developedusing application management. You can quickly and easily add new locales by dragging and droppinga language pack to your application. You can dynamically customize and modify locale information foryour application.

Application roles are used to define the access control for applications. Users can access an applicationitself or a feature/component within that application, based on the application roles you assign them -for example: user, administrator, supervisor.

My Work Application

My Work Application is available as part of Application Management. My Work Application presentsan integrated, fully functional client application. It is called "workapp" in the Application Managementuser interface. This application provides an example user interface to the business components andbusiness component services (which are part of the Client Application Framework). You can use MyWork Application out-of-the box, or clone and customize it, depending on your own requirements. Youcan also customize logos and other visual elements. For example, you can keep the service logic of thework list, but completely change the appearance of the layout. This allows you to rapidly develop userinterfaces for your business without the need to handle API interactions. See the "myWorkAppDemonstration" video available on the ActiveMatrix BPM product page on the TIBCO Documentationsite.

Component Showcase

The Component Showcase application is available as part of Application Management. The ComponentShowcase application demonstrates the use of individual business components and component services(which are part of the Client Application Framework). It is called "component_showcase" in theApplication Management user interface. Component Showcase uses the same business components andcomponent services as My Work Application. However, whereas My Work Application presents anintegrated, fully functional client application, Component Showcase breaks that functionality downinto a number of stand alone examples, which you can use to more easily understand how they work,

9


or as the basis for your own development. See "Component Showcase Application" in the TIBCOActiveMatrix BPM Client Application Framework Developer Guide for more information.

Client Application FrameworkThe Client Application Framework is used to create and manage lightweight BPM applications usingindustry-standard technologies, such as Bootstrap CSS, AngularJS, and JavaScript.

The Client Application Framework consists of, and uses, the following elements:

● Business Components - Business components are used to render BPM-related controls in anapplication. These can be used as building blocks to create a client application.

Business components are BPM-specific components, implemented as AngularJS directives, that canbe embedded in an application as HTML elements.

● Component Services - Component services are used to perform BPM-related functions that wouldrequire several calls to the lower-level objectAPI. They can be used to extend or change existingbusiness components, or to build new custom components.

Component services are fully functional AngularJS services that can be consumed by AngularJSclients. They make it much easier to perform certain BPM functions that require the use of multiplecalls when done directly from the objectAPI - for example, opening a work item or displaying aform from a pageflow can be done with a single call using component services.

● ObjectAPI - The ObjectAPI provides services that contain functions for all available ActiveMatrixBPM functionality. Object API is a client side API written in Javascript to consume BPM serviceseasily from a web client. Typically, you will use business components and component services tobuild an application, as those require less effort. However, not all ActiveMatrix BPM functionality isavailable by using business components and component services. If that additional functionality isneeded, the ObjectAPI can be used to access it.

Work Manager

Reduced Use of XA Transactions

Use of XA transactions in TIBCO ActiveMatrix BPM has been reduced, producing significantperformance improvements. As part of this change:

● The node types used by BPM have changed. The following table shows the pre-version 4.0 nodetypes and their version 4.0 equivalents.

Pre-version 4.0 Node Type Version 4.0 Node Type

BPM BPM

Web Components Client

Process Manager Server

Work Manager Server

If you are upgrading from a pre-4.0 version BPM system that includes BPM nodes of node type WebComponents, Process Manager or Work Manager, these node types will automatically beconverted as part of the upgrade process to version 4.0 node types. (Web Components nodes areconverted to Client node type. Process Manager and Work Manager nodes are converted to Servernode type.) The upgrade process could potentially take a significant amount of time because of thework involved in this conversion.

10


● Process Engine and Event Collector now share the use of the common (DataSource andDataSourceDirect) database connection pools with other BPM components, instead of having theirown pools. As there are now fewer connection pools you should review and, if necessary, increasethe number of connections per pool if you are upgrading from a pre-4.0 version BPM system. SeeTIBCO ActiveMatrix BPM Installation and Configuration for more information about how to do this.

Archiving Messages

ActiveMatrix BPM now enables you to archive events, which are messages that record its activity. Thisis useful as it means that these messages are no longer visible in the ec_event view. This can improvethe responsiveness of the ec_event view when performing queries against it. See TIBCO ActiveMatrixBPM Administration Guide for more information.

Calling a REST Service from a Process

You can now access REST Services from TIBCO Business Studio. You can create a REST Services projectto define REST Services. You can then invoke these using a service task of type REST Service. TIBCOActiveMatrix® Binding Type for REST 3.3.0 HF01 is a minimum requirement if using REST serviceinvocation tasks from BPM processes. This is required for ActiveMatrix BPM and recommended forTIBCO Business Studio. See "Calling a REST Service" in the TIBCO ActiveMatrix BPM ImplementationGuide for more information.

Case Data Signal Event Handlers

Case data signal event handlers allow a process to subscribe to a particular case object that the processuses. The process will then be notified if that case object is modified, and can take appropriate action torespond to the change. See "Notifying a Process That a Case Object It Uses Has Been Modified" in theTIBCO ActiveMatrix BPM Case Data User's Guide for more information.

TIBCO DocumentStore

There is an "internal CMS" -- the TIBCO DocumentStore -- that is installed only with the TIBCOActiveMatrix BPM Development Server. When an ActiveMatrix BPM Development Server is installed,the TIBCO DocumentStore is automatically installed on the server. The DocumentStore is an "internalCMS" that can be used to work with, and test, case folder functionality in a development / testenvironment. If case folders are to be used in the production system, an external CMS must be installedwhen moving to the production system. The DocumentStore cannot be used in a productionenvironment. See "TIBCO DocumentStore" in TIBCO ActiveMatrix BPM Case Data User's Guide for moreinformation.

ClientsThis section describes the new features in Forms, Openspace and Workspace.

TIBCO FormsThis section describes the new features in TIBCO Forms.

Data Fields Now Support Length and Decimal Places Properties

Data fields now support the Length and Decimal Places properties. Previously, only form parameterssupported the Length and Decimal Places properties. With this release, these properties may also be setfor data fields.

● Length is used only for Text, Integer and Decimal types.● Decimal places is used only for the Decimal type.

Please see TIBCO Forms User's Guide for more information.

11


Openspace

The Openspace Case Management gadget has been updated to support ad-hoc searches. Ad-hocsearches enable you to create a one-off search, based on one or more top-level attributes of a case class.

Ad-hoc search simplifies the search criteria selection by showing only top-level attributes of the caseclass. You can also save your ad-hoc searches as parameterized searches. For example, you may want toperform many searches that use the same case attributes but different filter criteria. By saving yoursearch as a parameterized search, you can retrieve only the attributes you want. The Case Summaryview is enhanced to display case summary fields selected in design time. See TIBCO Openspace User'sGuide for more information.

Workspace

● Previously, when creating case views, they had to be placed in a category. Now you can createuncategorized case views.

● The Case View Results dialog now includes columns for attributes as defined in the Case Summaryin TIBCO Business Studio, rather than just a column for the case reference. This also includes a newShow Case Reference selection on the View menu on the Case View Results dialog that is a toggleto show case reference in the list, if desired.

Also as part of this enhancement, the term "data view" has been changed to "case view" in theWorkspace application to be more descriptive of the information in the view.

● The following process instance states are now shown in the process instance list for sub-processesthat were cancelled, and are now awaiting compensation events to complete before changing to aCancelled state. The specific state shown depends on whether the sub-process was active,suspended, or halted when it was cancelled.

— Active while Canceling— Suspended while Canceling— Halted while Canceling

● The Event Viewer now displays the names of resource entities, for events that contain a resourceentity attribute, rather than just the resource GUID.

Also, the Event Viewer has a new Work Item Participants selection on the View menu that lists theparticipants for the work item associated with the event. This selection is enabled for events thatcontain a "Resource Entity GUID" attribute.

A new EventView > EventViewer > WorkItemParticipants user access control has also beenadded to the userAccess.xml file to control access to the new "Work Item Participants" function.

● The "Allocate Work Item(s) To Self" function is now available from supervised work views.

A new WorkView > SupervisedWorkItem > AllocateToSelf user access control has also beenadded to the userAccess.xml file to control access to the new "Allocate Work Item(s) To Self"function.

● The following Workspace Client Component (WCC) methods have been updated to include a newincludeFormalParams parameter, which is used to specify that business services with formalparameters be returned in the result: listBusinessServiceCategories, queryBusinessServices, andqueryBusinessServiceCategories.

● The Column Selector is now available from the Resource List in Workspace when using the"Allocate Work Item(s) to Offer Set" and "Allocate Work Item(s) To World" functions.

12


The Column Selector has also been added to the Resource List in the Organization Browser(although it is disabled when viewing system resources, as well as when viewing resources in anLDAP container).

● A new user option has been added to Workspace that allows the user to change the size of the fontdisplayed in the application. This includes a new Font selection on the Options dialog in theapplication, as well as a new Font > fontSize setting in the <Options> record in the config.xmlfile.

A new ConfigureOptions > FontSize user access control has also been added to theuserAccess.xml file to control access to the new Font selection on the Options dialog.

● A modifyViewListData callout method has been added to Workspace. This method can be used tomodify display values for work views, process views, and event views. This allows for localizingthe names and descriptions of views, as well as ordering the views in the view list.

13


Changes in Functionality

There are changes to certain functions of the following components in this release:

● When a process fails, leaving it in the database can help determine what went wrong. If it isautomatically deleted, then all data is lost. In previous versions, failed process instances werepurged by default. With this version, failed process instances are not purged by default. To revert tothe previous behavior where failed process instances are automatically purged, add the JVMproperty com.tibco.bx.autoDeleteFailedProcesses="yes" in the BPM node configuration inAdministrator. This must be done on each BPM node.

If process instances failed before changing this property to "yes", they are not purged.Only failed process instances that failed after the property was set to "yes" are purged. Topurge process instances that failed before setting the property, use thepurgeTerminatedProcessInstances API using the processInstances parameter. For moreinformation see TIBCO ActiveMatrix BPM Developer's Guide.

14


Deprecated and Removed Features

This section describes deprecated and deleted features (if any), and lists features, if relevant, that maybe useful alternatives to the deprecated features in TIBCO ActiveMatrix BPM 4.0.0.

Any use of a deprecated feature should be discontinued as it may be removed in a future release.You should avoid becoming dependent on deprecated features and become familiar with the suggestedalternative features.

Deprecated Items

DescriptionDeprecatedRelease

"getWorkListItems" has a redundant response type in the xsd.

● getWorkListItemsResponseType

4.0.0

The correlation behavior for all BX audit events will change in futureversions.

3.1.0

ec_stats table is deprecated and will be removed in a future version. 3.1.0

Message IDs in BRM service faults will be changed in a future version. 3.0.0

The following Properties are deprecated and will be removed fromECPublicationJMS.properties in a future release. Therefore the legacy methodof event publication valid until TIBCO ActiveMatrix BPM 2.2 will no longerbe supported in a future release of BPM and only the shared resourceapproach would be supported:

● InitialContextFactory● InitialURL● TopicConnectionFactory● SecurityPrinciple● SecurityCredentials● SecurityEncryption● Persistent● Priority● TimeToLive● TopicName

3.0.0

15


Deleted Items


RemovedRelease

The following Directory Engine APIs are removed in thisrelease. The information below specifies the replacementAPI (as bullet points) for each of the APIs deprecated (initalics). In most cases, the replacement API providesadditional options and information over-and-above thatof the original, deprecated API.Attribute Service

listBusinessParameters

● OrgModelService.getOrgModel● OrgModelService.getOrgModelRoots

Both these services return the Resource Attributes for agiven organization-model version.

getBusinessParameters

● OrgModelService.getOrgModel● OrgModelService.getOrgModelEntity

The Attributes are returned as part of the details of eachorganization-model entity included in the response ofboth these services.

● OrgResourceService.getResource

This method includes the Attributes for a givenResource.

setBusinessParameters

● OrgResourceService.updateResource

Only the Attributes for a Resource can be updated (notthose for an organization-model entity). This methodallows those Attributes to be set/updated.

getPushDestinations

● OrgModelService.getOrgModel● OrgModelService.getOrgModelEntity

These services include the Push Destinations as part ofthe details for each organization-model entity in theresponse.

● OrgModelService.getPushDestinations● OrgResourceService.getResource

These methods include in the Push Destinations for theidentified entity. The

3.1.0 4.0.0

16



RemovedRelease

OrgModelService.getPushDestinations can also be usedfor Resources.

setPushDestinations

● OrgModelService.updatePushDestinations

Sets, or updates, the Push Destination for a given entity.

Browse Model Service

listCapabilities


Both these services include a list of all Capabilitiesdefinitions for a given organization-model version.

listPrivileges


Both these services include a list of all Privilegedefinitions for a given org-model version.

getCapabilities

● OrgModelService.getOrgModel● OrgModelService.getOrgModelEntity● OrgResourceService.getResource

All these services include the Capability assignments aspart of the details for the organization-model entities,and resources, included in the response.

getPrivileges

● OrgModelService.getOrgModel● OrgModelService.getOrgModelEntity● OrgResourceService.getResource

All these services include the Capability assignments aspart of the details for the organization-model entities,and resources, included in the response.

listModelVersions

● OrgModelService.listOrgModelVersions

This service lists all major organization-model versionnumbers. Nested within each major version are thedetails of the organization-models that make up thatmajor version.

openOrgModel

17



RemovedRelease

● OrgModelService.getOrgModelRoots

This service returns the details of the root entities of thegiven organization-model version. For Groups andOrganizations, the identifiers of any immediate childentities (sub-Groups or Organizational Units) areincluded. Those identifiers can then be fed into theOrgModelService.getOrgModelEntity, in order toretrieve details of those entities, in a drill-down fashion.

browseModelNode

● OrgModelService.getOrgModelEntity

This service returns the details of an organization-modelentity identified by its organization-model version andGUID. Those entities that have nested, sub-ordinateentities (Groups, Organizations and OrganizationalUnits) will include the identifiers of those sub-ordinateentities. Those identifiers can then be fed back into thesame service, in order to retrieve details of those entities,in a drill-down fashion.

listOrgModelOverview

● OrgModelService.getOrgModel

This service returns the details of all the entities within agiven organization-model version.

listOrganizations

● OrgModelService.getOrgModelRoots

This service returns the details of the root entities of thegiven organization-model version. For Groups andOrganizations, the identifiers of any immediate childentities (sub-Groups or Organizational Units) areincluded. Those identifiers can then be fed into theOrgModelService.getOrgModelEntity, in order toretrieve details of those entities, in a drill-down fashion.

Container Service

listLDAPContainers

● DirectoryService.listContainers

This service returns the full details of all LDAPContainers; including the mappings of LDAP Attributesto Resource Attributes.

getLDAPContainerDetail

● DirectoryService.listContainers

saveLDAPContainerDetail

18



RemovedRelease

● DirectoryService.saveContainer

Creates, or updates, an LDAP Container.

deleteLDAPContainer

● DirectoryService.deleteContainer

This service will delete the identified LDAP Container,and, optionally, all Resources derived from thatContainer. If Resources, derived from the identifiedContainer, still exist (and the option to delete them is notused), the deletion will be refused.

LDAP Service

listLDAPSources

● DirectoryService.listLdapConnections

This service will return the details, including theconnection URL, of all available LDAP ConnectionShared Resources.

listLDAPEntities

● DirectoryService.listCandidateResources● DirectoryService.getCandidateDetail

The listCandidateResources will return the LDAP details(alias and DN) for the LDAP entries accessible to theidentified LDAP Container. For those entries for which aResource has been created, the GUID and name of thatResource will be included. The service allows the callerto list only entries associated with existing Resources,only entries not associated with existing Resources, orboth. The service also allows the entries to be retrievedin a paged fashion.

Having retrieved the LDAP DN of the LDAP entries forthe LDAP Container, the values of any LDAP attributesmapped to Resource Attributes can then be retrievedusing getCandidateDetail.

listContainerResources

● DirectoryService.listCandidateResources● OrgResourceService.getResource

The listCandidateResources will return name and GUIDfor those Resources derived from the identified LDAPContainer.

Having retrieved the GUID for the Resources derivedfrom the LDAP Container, the full details of thoseResources can then be retrieved using getResource.

listLDAPAttributes

19



RemovedRelease

● DirectoryService.getLdapEntry

This service returns the values of the named LDAPAttribute for the given LDAP DN. If no LDAP Attributesare named, the response will include all attributes for theidentified LDAP entry. The values of those attributesthat contain binary data will be base-64 encoded, and theattributes entry will be marked as binary.

listLDAPAttributeNames

● DirectoryService.listAttributeNames

This service identifies the names of the LDAP attributesfor the entries identified by evaluating the given LDAPQuery against the LDAP Connection identified by itsalias. Those attributes that hold binary data will bemarked as such.

The response can also include a sample of the values forthose attributes. The values of those attributes thatcontain binary data will be base-64 encoded.

Mapping Service

listMappedEntities

● OrgResourceService.findResources● OrgResourceService.getResource

The findResources service will return name and GUID ofthose Resources associated with an identified org-modelentity (Group, Organization, Organizational Unit,Position, Location, Capability and Privilege). ForLocation; only those Resources directly assigned to theidentified Location will be included.

The getResource service can then be used to retrieve thefull details of the Resources, using their GUIDs.

getResourceGuid

● EntityResolverService.lookupUser● OrgResourceService.getResource● DirectoryService.listCandidateResources● OrgResourceService.createResource

Using lookupUser and getResource, the details of anexisting Resource can be retrieved using the LDAP DNfor that user.

Using listCandidateResources and createResource, anew Resource can be created from the LDAP propertiesretrieved from the LDAP Container.

deleteResource

20



RemovedRelease

● OrgResourceService.deleteResource

This service deletes the records of one or more Resourcesidentified by their GUID.

mapEntities

● OrgResourceService.createResource● OrgResourceService.updateResource

Resources, created by the createResource service, can beassigned to Positions and/or Groups using theupdateResource service.

updateCapabilityAssignments

● OrgResourceService.updateResource

This service allows the update of a Resource's Capabilityholdings; along with other properties of the Resource.

21


Migration and Compatibility

This topic describes migration and compatibility issues for TIBCO ActiveMatrix BPM 4.0.0.

Refer to TIBCO ActiveMatrix BPM Installation and Configuration for upgrade instructions.

If migrating from versions prior to this version, see TIBCO ActiveMatrix BPM Installation andConfiguration for information on configuring new features post upgrade:● Configuring CMIS if migrating from TIBCO ActiveMatrix BPM 3.0.● Using the Edit wizard to configure the BDS database to be other than internal BPM database.● Configuring Single sign-on.

Upgrading Pre-TIBCO ActiveMatrix BPM 2.2 to TIBCO ActiveMatrix BPM 4.0To upgrade to TIBCO ActiveMatrix BPM 4.0, TIBCO ActiveMatrix Platform 3.3.0 HF11 is mandatory.

See TIBCO ActiveMatrix BPM Installation and Configuration for more information on upgrade scenarios.

Procedure

1. Install TIBCO ActiveMatrix BPM 4.0.

2. Launch TCT (TIBCO Configuration Tool) from the TIBCO ActiveMatrix BPM 4.0 bin directory, andupgrade the Tibcohost, AMXAdmin and BPM nodes (to do this, select the first three upgradeoptions in TCT). This upgrades the platform to 3.3.0.

3. Stop tibcohost.

4. Install TIBCO ActiveMatrix Platform 3.3.0 HF11 (or above) and apply the patch using the patchmanager.

5. Start tibcohost.

6. Launch TCT from the TIBCO ActiveMatrix BPM 4.0 bin directory, and upgrade BPM Database (todo this, select only the last upgrade option).

Upgrading TIBCO ActiveMatrix BPM 2.2 and Later to TIBCO ActiveMatrixBPM 4.0

To upgrade to TIBCO ActiveMatrix BPM 4.0, TIBCO ActiveMatrix Platform 3.3.0 HF11 is mandatory.

See TIBCO ActiveMatrix BPM Installation and Configuration for more information on upgrade scenarios.

Procedure

1. Install TIBCO ActiveMatrix Platform 3.3.0 HF11 (or above) and apply the patch using the patchmanager.

2. Install TIBCO ActiveMatrix BPM 4.0.

3. Launch TCT from the TIBCO ActiveMatrix BPM 4.0 bin directory, and upgrade BPM Database (todo this, select only the last upgrade option).

TIBCO ActiveMatrix BPM Version 3.0

Updating Client Applications to Use SOAP Version 1.2

22


● Up to and including version 2.2, TIBCO ActiveMatrix BPM only supported SOAP version 1.1

A TIBCO ActiveMatrix BPM version 3.0 system can be configured to use SOAP version 1.1 (thedefault) or version 1.2 bindings. (See TIBCO ActiveMatrix BPM Installation and Configuration for moreinformation.)

To communicate with a (new or reconfigured) TIBCO ActiveMatrix BPM system that uses SOAPversion 1.2 bindings, an existing client application built using a version 2.2 (or earlier) BPM webservice API must be modified as follows:

API Used Modification Required

BPM web service API Rebuild the application using the SOAP 1.2version of the API.

Java Service Connector Reconfigure the application to use SOAPversion 1.2 - see "Instantiating and Configuringthe Service Connector" in the TIBCOActiveMatrix BPM Developer Guide.

TIBCO ActiveMatrix BPM Version 1.3

Using getWorkListItems in a Client Application

● Up to and including version 1.2, the entityID element used by getWorkListItems is contained withina choice element.

In some programming environments (such as .NET in its default form), choice elements arerepresented by a parent entity (in this case, Item) which can be cast to any of the types that thechoice allows. For more information, see "Handling Choice Elements in the BPM API Schemas" inthe TIBCO ActiveMatrix BPM Developer Guide.

In version 1.3, the choice element has been removed.

An existing application built using the version 1.2 BPM web service API will continue to run againstTIBCO ActiveMatrix BPM version 1.3.

However, if you rebuild an existing application (that uses getWorkListItems) against the version 1.3BPM web service API, you should change your code to directly use entityID (instead of casting).

Initializers and MigrationWhen you add a new ad-hoc activity, and then upgrade and migrate, you must define an initializer forthe activity which executes after the migration. This could actually be the migration point itself.

Configuring the Business Data Services (BDS) DatabaseIn particular cases, you may need to configure ActiveMatrix BPM so that names that are used in theBDS database are limited in length to 30 characters. This is to avoid issues that may arise if you latermigrate BDS database tables from SQL Server or DB2 to Oracle.

Prerequisites

If all the following conditions apply to your situation, we strongly advise you to perform thisprocedure:

● You are upgrading ActiveMatrix BPM (fresh installations are not affected).

23


● ActiveMatrix BPM is using DB2 or SQL Server.● You have not yet deployed any BDS Global Data Applications to your running system, or are

upgrading ActiveMatrix BPM from a version before 3.0.

If you have a system to which existing BDS Global Data Applications have been deployed, you shouldnot perform this procedure unless you are happy to first undeploy the Applications.

Procedure

1. Open the bds.properties file in a text editor.

The file is typically stored on the machine where you installed ActiveMatrix BPM, in the followingfolder:

CONFIG_HOME/bpm/BPM_APP_NAME/configuration/

2. Set the following properties to the values shown:# Allows the specification of the maximum length to use for table names.# It is recommended that this is set to 30 to provide the most# flexibility across all database typescaseDataStoreTableNameMaxLength=30 # Allows the specification of the maximum length to use for column names.# It is recommended that this is set to 30 to provide the most# flexibility across all database typescaseDataStoreColumnNameMaxLength=30 # Allows the specification of the maximum length to use for a database index.# It is recommended that this is set to 30 to provide the most# flexibility across all database typescaseDataStoreIndexNameMaxLength=30

These settings limit the length of the names used in the BDS generated database.

3. Save and close the file.When you have set these properties and deployed a BDS Global Data Application, you should notchange the property values again.

Upgrade Script Issue with Openspace GlobalHubPolicy DataThe upgrade script does not upgrade the Openspace GlobalHubPolicy data automatically. This meansthat the Calendar is not displayed. A manual post-upgrade action is required.

Procedure

1. Log into Openspace and open the preferences panel on any tab except Calendar, then click MoreGadgets.

2. Select Manage Gadgets > Communication. The Hub Policy Administrator opens.

3. Click Delete Selected Domain. A warning appears - click OK.

4. Click Save.

5. Select Manage Gadgets > Communication to reopen the Hub Policy Administrator.

6. Click Add Hub Policy.

7. Warnings appear - click OK.

8. More warnings appear - click OK.

9. Expand the OpenspaceApp / Publish Topics to confirm that TranslationEvent2 is listed.

10. Click Save.

24


11. Close the Hub Policy Administrator and log out of Openspace.

12. Log into Openspace again and the Calendar is available.

Upgrading the Oracle JDBC DriverTo use the new case data features introduced in 3.0 on Oracle, you must ensure your JDBC driver meetsthe minimum version requirement of 11.2.0.4.0.

If you have upgraded TIBCO ActiveMatrix BPM, ensure that you have the correct JDBC driver. You canfind out the current version of the Oracle JDBC driver by looking for the following entry in the log fileon system startup:

16 Apr 2014 11:03:27,276 [Job_Executor4] [INFO ] org.hibernate.cfg.SettingsFactory -

JDBC driver: Oracle JDBC driver, version: 11.2.0.4.0

Alternatively, locate the following folder: TIBCO_HOME/components/shared/1.0.0/plugins/com.tibco.tpcl.gen.oracle.jdbc_11.2.100.001, open the ojdbc6 JAR file, and examine the fileMETA-INF/MANIFEST.MF for the following entry:

Implementation-Version: 11.2.0.4.0

If your Oracle JDBC driver does not meet the minimum requirement, use the following procedure toupgrade it.

Procedure

1. Shut down the entire system (Administrator and all BPM nodes on all machines).

2. On all machines, replace the file ojdbc6.jar in the folder TIBCO_HOME/components/shared/1.0.0/plugins/com.tibco.tpcl.gen.oracle.jdbc_11.2.100.001 with the JDBC driver thatmeets the minimum requirement (11.2.0.4.0).

3. On all machines, replace the file ojdbc6.jar in the folder TIBCO_CONFIG_HOME/tibcohost/Admin-AMX BPM-AMX BPM Server/data_3.2.x/host/plugins/

com.tibco.tpcl.gen.oracle.jdbc_11.2.100.001 with the JDBC driver that meets the minimumrequirement (11.2.0.4.0)

4. Start up the entire system (Administrator and all BPM nodes on all machines).

Openspace Upgrade Script and Data ViewsWhen upgrading to TIBCO ActiveMatrix BPM 4.0.0 from an earlier version, the upgrade script will notadd the new Data Views, Data Admin and Organization Browser components to existing user layouts.A post upgrade step is required to push the new gadgets and layout to existing users.

There are two scenarios.

If no standard persona exists

The default persona is modified during the upgrade to include the new default TIBCO layout thatincludes the new Data Admin, Data Views and Organization Browser gadgets. After upgrade, theOpenspace Administrator must do the following:

● Login into Openspace.● Click Manage Settings.● From the drop-down list, select Default Persona.● Select Apply persona to all users.● All users must select Reset Settings and then logout and login to Openspace.

25


— This causes all users settings to default to the new TIBCO layout. Next time they log in, amessage displays informing them that their settings have been updated and the new layout willbe applied.

— Any user customizations such as sort / filter settings are reset to default and need to berecreated.

If a standard persona does exist

If you have previously created a Standard (customized) persona which is applied to new users andexisting users (in other words Apply persona to all users) was selected when the persona was created,the Standard persona is not modified by the upgrade. After upgrade, all existing and new users willcontinue to see the Standard persona layout. To see the new TIBCO layout, the OpenspaceAdministrator must do the following, after upgrade:

● Delete the standard persona and perform the steps described above to modify the default persona.● Modify the standard persona to include the new gadgets and desired layout and then apply it to all

users. See TIBCO Openspace User's Guide for more information.

Workspace MigrationThis section describes migration issues if you are upgrading TIBCO Workspace to version 4.0 from aprevious version.

The most common migration issues involve handling new configuration parameters (in config.xml)and user access elements (in userAccess.xml). The way in which you make use of new configurationparameters and user access elements after upgrading depends on whether you are using theWorkspace application or a custom WCC application.

The following two subsections describe what to do depending on the type of application you are using.Then the last subsection lists the configuration parameters and user access elements that have beenadded in Workspace 4.0.

For information about migrating from earlier versions, see earlier release notes.

Workspace Application

If you are running the Workspace application, after you upgrade, any new configuration parametersare automatically available and any new user access elements are automatically included in theAccessDefaults user access profile. However, if you have user access profiles other than AccessDefaults,you must manually add the new elements to those profiles to make use of the elements.

Custom WCC Application

If you are running a custom WCC application, and want to make use of new configuration parametersand user access elements, you must manually add them to your application’s config.xml file anduserAccess.xml file, respectively, on your development environment file system. You must thencreate a new .war file for your custom application, and redeploy the application using ActiveMatrixAdministrator. For information about the process of creating the .war file and deploying anapplication, see "Deploying an Application After Customizing" in the TIBCO Workspace Configurationand Customization guide.

Also note the following:

● If you choose not to use the new configuration parameters and user access elements, and you do notredeploy, your custom WCC application will not pick up the new WCC runtime; you must stillcreate the .war file and redeploy for your application to use the new runtime, even if you don'twant to use the new parameters and elements.

● If you add the new configuration parameters and user access elements to the files in yourdevelopment environment, and then create the .war file and redeploy, they will not be picked up in

26


your WCC application if you had previously accessed the Configuration Administrator and madechanges to configuration or user access that would result in the settings being stored in thedatabase. If this is the case, after redeploying, you must open the Configuration Administrator andeither click Defaults to pick up the changes you made to the files in the development environment,or duplicate the changes you made to the files in the database using the ConfigurationAdministrator interface. (For more information about using the Configuration Administrator andhow it writes information to the database, see "Using the Configuration Administrator" in theTIBCO Workspace Configuration and Customization guide.)

● You must upgrade WCC in your development environment prior to creating the new .war file.After upgrading WCC in your development environment, you must also perform the followingtasks:

— Copy your custom application-specific directory from the previous release to the new release.For example, if the name of your custom application is "accounts", copy this directory:

StudioHome\wcc\oldVersion\JSXAPPS\accounts\

to:

StudioHome\wcc\newVersion\JSXAPPS\

— Copy the launch fragment for your custom application from the previous release to the newrelease. For example, if the name of your custom application is "accounts", copy:

StudioHome\wcc\oldVersion\accounts.html

To:

StudioHome\wcc\newVersion\accounts.html

— Copy the .war creation command file for your custom application from the previous release tothe new release. For example, if the name of your custom application is "accounts", copy:

StudioHome\wcc\oldVersion\accounts.create.war.cmd

to:

StudioHome\wcc\newVersion\accounts.create.war.cmd

where oldVersion is the version you are upgrading from and newVersion is the new version towhich you are upgrading.

New Configuration Parameters and User Access Elements

This section provides information about configuration parameters in config.xml and user accesselements in userAccess.xml that are new in version 4.0.

New Configuration Parameters

The following configuration parameter has been added in Workspace version 4.0:

● Font > fontSize - This new parameter in the <Options> record is used to set the default font sizefor the application.

New User Access Elements

The following user access elements have been added in Workspace version 4.0:

● EventView > EventViewer > WorkItemParticipants - Controls access to the new "Work ItemParticipants" function on the Event Viewer.

● WorkView > SupervisedWorkItem > AllocateToSelf - Controls access to the new "AllocateWork Item(s) To Self" function on supervised work views.

27


● ConfigureOptions > FontSize - Controls access to the new font-size setting on the Optionsdialog.

28


Closed Issues

The closed issues in TIBCO ActiveMatrix BPM 4.0.0 are listed per component:

● Core Components● TIBCO Forms● Clients

Core ComponentsThe section lists closed issues for Core Components in TIBCO ActiveMatrix BPM 4.0.0.

Work Manager

Key Information

WRM-8599(WRM-8498)

If you specify a date on a form, submit the form, and then open the form fromanother user task, the user task displays the previous date.

WRM-8532 Registering RQL expressions, for Process Participants or Performer Data Fields,that use an apostrophe in a string, for example, resource(name="John's") failwith a "{DE_ENTITY_SAVE_ERROR} - Error encountered when saving anentity's details" exception, when parsed.

WRM-8304(WRM-8055)

Stricter classloading validations are implemented for Business Objects (BOMbased classes) in ActiveMatrix BPM 4.0.

WRM-8112 The completion of work items is slow. The number of work items queued up forcompletion is the same as the number of pending messages on the EMS queue.

WRM-8102(WRM-8098)

If you add a new business object model to an existing global data project, wherethe new BOM has a namespace that affects the natural ordering of previouslydeployed namespaces, incorrect error messages are reported in the BPM log filewhen you upgrade the global data application. For example:[ERROR] com.tibco.bds.core.deployment.BDSImplementationType - [ERROR] - {BDS_COMPONENT_GENERIC_DEPLOY_FAULT} - BDS: Deployment failed Â¬{extendedMessage=`Incompatible changes made during upgrade of version 3.0.7 of model pl.bzwbk.corpo.loans.bom-3Details:The following unsupported changes were made:....

WRM-8042 If you try to invoke a dynamic sub-process in a different project from the mainpageflow project and there are no user tasks in the main pageflow project afterthe call sub-process task, this causes an exception.

29


Key Information

WRM-7998 When upgrading from ActiveMatrix BPM version 2.0.0, the upgrade migratesfrom using the ECPublicationJMS.properties file for JMS configuration, tousing a new ec-event-rules.xml file. If the includeSeverity property inECPublicationJMS.properties has no value, an invalid ec-event-rules.xmlfile is created, containing the following erroneous rule:<rule name="ErrorTriggerRules" ruleOrder="900"> <filter> <severities> <severity/> </severities> </filter> <action> <messageProcess>TriggerProcess</messageProcess> </action></rule>

Because of this, upgrade fails with the following error:ERROR (UserTaskProgressIndicator.java:67) - Application Start failedERROR (UserTaskProgressIndicator.java:75) - Start component 'implementation.ec' on node 'BPMNode' failed : java.util.concurrent.ExecutionException: java.lang.IllegalStateException:

WRM-7994 Internal enhancements have been made to the ActiveMatrix BPM REST API toimprove its performance when communicating with the BPM runtime, byreducing the time taken to execute each API call. This results in improvedperformance for custom client applications that use the ActiveMatrix BPMREST API.

WRM-7956 To try and set up correct remote folders per node the upgrade tasks attempt todetect the current configuration folder. Previously (pre-ActiveMatrix BPM 2.2.0)there was not an amx.bpm.app app specific folder, so: <somedrive>:\amx.bpm.app would work, whereas: <somedrive>:\ would fail.

WRM-7926 When performing an upgrade of ActiveMatrix BPM, the following error isdisplayed: "The schema for component Directory Engine is not at the expectedversion. Expected 1.8.1 but found 1.8.0."

WRM-7912 Log Viewer sometimes gets a NullPointerException when loading a file usingthe "Open File" dialog, rather than drag/dropping files on to it (or usingcommand line load).

WRM-7895 When an Resource Query Language (RQL) expression is re-evaluated alongwith other registered RQL expressions, the processing of one may affect theresults of subsequent expressions; leading to incorrect result sets.

WRM-7884 Due to the security restrictions when using SSL enabled LDAP connections, thepagination of BPM resource/user lists is silently disabled, and all BPM resourcesare retrieved at once. So, although the user-interface suggests that BPMresources can be retrieved in a paged fashion infact, all resources will beretrieved from the LDAP Container.

WRM-7882 When using Microsoft SQL for your ActiveMatrix BPM database, the databasecleanup script has error 'Cannot drop the function 'csvList', because it does notexist or you do not have permission.

30


Key Information

WRM-7880 The upgrade of Business Data Services user application upgrade failed with thefollowing error: "Failed to Execute the following Script Fragment: create index".This failure occurred when both the following conditions were true:

● The global data user application had many versions that were in 'running' or'preparing to undeploy' state.

● The user application upgrade was performed after a number of BPM versionupgrades or after a node restart.

WRM-7857 Attributes like managedObjectStatus, resourceId, resourceName are not setcorrectly in the audit message.

WRM-7829 The work item state is not always being updated correctly.

WRM-7811 The getDataViewDetailsByName REST API is not returning any categoryinformation for saved searches.

WRM-7782 The listCaseSummary API is not returning any case actions for a valid andexisting case reference.

WRM-7779 Running JVMInfo leaves threads running in BPM JVM. This can result in largenumbers of threads running which can affect performance.

WRM-7745 Changes to the Business Data Services API to include case summaryinformation for case data. Please refer to the documentation for the CaseManagement Gadget in the TIBCO® Openspace User's Guide for moreinformation.

WRM-7669 Support available for the inject event on business service functionality in theOOTB BizApp Application.

WRM-7645 SAML Signed Sendor-Vouches Requests are successful for non-existing users.They should fail for non-existing users.

WRM-7632 When using data preview with a work item, instead of displaying a summary ofthe case data, the case reference displays.

WRM-7596 The case reference is required in a getCaseSummary request, but the response isreturned successful, even if no case reference is provided.

WRM-7585 The getCaseSummary API response returns a case reference even if no casesexist. It does not return any case summary information but it should return afault saying no cases exist.

WRM-7582 When you make an API call to the listBusinessServices operation where theoptional numberOfItems parameter is not specified, then the returned responsedoes not include the startPosition and endPosition.

WRM-7574 Sometimes a misleading exception is thrown (Null Pointer Exception) when apageflow execution fails (for example, when a wrong set of parameters arepassed).

31


Key Information

WRM-7569 When business data service applications are upgraded, BPM applies auseLastCaseAction rule. This means that for all upgrades, all case actions arelost for older versions of business data services cases. The useLastCaseActionrule should only be applied to non-major-version business data serviceapplication upgrades only.

WRM-7553 The listCaseAction API is used by case management gadget (it could be used bycustom clients as well) to display list of case actions that corresponds to a givencase reference. If a case reference passed to this API becomes stale (for example,if case objects gets deleted in-between reading it and supplying tolistCaseActions API), then the listCaseAction API will return all case actionsrather than returning a fault.

WRM-7546 When adding a new BPM node to your distributed TIBCO ActiveMatrix BPMsystem, all user applications display as 'out of sync' with the following message:"Type of unapplied configuration changes for this item - Distribution to nodes".The new node distribution was modified to explicitly deploy child userapplications that are not in the CONFIGURE_FAILED state.

WRM-7544 When a work item is rescheduled, the EC_WI_STATUS table is not updated.This means that any changes made to work item data that may have occurredwhen the work item was rescheduled are not reflected in the EC_WI_STATUStable.

WRM-7489 You can now configure a case summary at design-time in TIBCO BusinessStudio. You can select the attributes and the order that the attributes display.

WRM-7488 The GetDataViewDetails API now returns parameter details. Please refer to thedocumentation for the Case Management Gadget in the TIBCO® OpenspaceUser's Guide for more information.

WRM-7467 The findDocuments service unnecessarily fetches document details for alldocuments. This means that it spends a lot of extra time gathering the metadatafor all documents that it finds. This is likely to be a heavy performanceoverhead for the findDocuments() method.

WRM-7464 Logging related to the Document Service's findDocuments API can sometimesbe missing from the BPM.log. For example, if the system is configured toinclude INFO level logging, then messages such as "CMIS where clause is(cmis:name LIKE 'abc.txt')" should appear in the BPM.log when a find operationis performed.

WRM-7393 TCT Edit Wizard should get and populate the current setting for editing LDAPauthentication.

WRM-7244 If you are using any of the PUT or PUSH methods in the ActiveMatrix BPMREST API and you are passing an empty payload, you must pass anappropriate content-type HTTP header (Content-Type: application/xml orContent-Type: application/json).

32


Key Information

WRM-7195 New example provided for setMigrationRules REST API. Please refer to thedocumentation for the Case Management Gadget in the TIBCO® OpenspaceUser's Guide for more information.

WRM-7611 In the ActiveMatrix BPM database, in the EC_USER_ACTIVITY table, thePROCESS_NAME column contains values from the PROCESS_INSTANCEcolumn.

WRM-7230 When you deploy a new version of the ActiveMatrix BPM application, if one ormore child applications is in a bad state (that is, CONFIGURE_FAILED), theproduct upgrade can fail.

WRM-7220 Combination of Separation of Duties and Dynamic RQL can cause process tohalt.

WRM-7183 SQL deadlock in EC/SC shows the Process Instances as active in Openspace.Workspace shows the same process instances as complete.

XPD-7064 After performing an upgrade on TIBCO ActiveMatrix BPM, the SystemNode inSystemEnvironment is Out of Sync due to the WSDL Validator being markedfor Install.

Process Manager

Key Information

BX-3784 The purgeTerminatedProcessInstancesRequest API does not accept a "FAILED"process state.

BX-3746 Encoded URL is incorrect, if invoked URL service resource path data has a 'space'or delimiter characters.

BX-3708(BX-3625)

A java.lang.ArrayStoreException is received when a pageflow process invokesanother pageflow process in a different project.

BX-3632 The queryProcessInstance API returns invalid XML when a process attribute valuecontains a XML entity.

BX-3585 If there are system exceptions at the root task of a process, the process should moveto HALTED instead of FAILED.

BX-3583(BX-3574)

Currently, the system property autoDeleteFailedProcesses is set to "yes" whichmeans that a failed process instance is automatically deleted. This system propertyshould be set to "no" so that a failed process instance is not automatically deletedunless you configure the autoDeleteFailedProcesses system property to yes(com.tibco.bx.autoDeleteFailedProcesses="yes").

33


Key Information

BX-3580(BX-3585)

If there are system exceptions at the root task of a process, the process should moveto HALTED instead of FAILED.

BX-3571 If there is a fault in an event task, the process should move to a HALTED staterather than a FAILED state. This allows any errors to be corrected so that theprocess can complete successfully.

BX-3568 When restarting an ActiveMatrix BPM node, any ActiveMatrix BPM applicationswith Page Flows that contain Java tasks can cause process instances to go into ahalted state. This is because the ActiveMatrix BPM components start in the wrongorder. In other words, the BPM components start after the Pageflow, causing thePageflow Java task to not execute correctly.

BX-3531 If an upgrade of a child process fails and is recovered, using a force undeploy andredeploy, new and existing process instances should then complete successfully.However, new and existing process instances are failing to complete.

BX-3530/BX-3527

Not all the execution paths are evaluated resulting in tasks being marked asuncontrolled merges unnecessarily.

BX-3526 If you have an application that implements a BPM service and upgradeActiveMatrix BPM and the application, and restart the node, the upgradedapplication fails to start as it cannot find the BPM service.

BX-3516 Start parameters must be specified if a parameter type is an array for a complexelement. Start parameters should be optional.

BX-3512(BX-3508)

In some situations, processes that failed when calling out to sub-processes may gointo a HALT state. Upon retry, the processes may complete successfully, however,the processes final state maybe COMPLETING and not COMPLETED. Secondly,upon cancel, the processes may end up in CANCELLING state and notCANCELLED state. This means you are not able to purge these instances from thedatabase.

BX-3506(BX-3484)

If a process is making a call and an exception is thrown, this causes the process togo into a HALT ON ERROR state and, ultimately, the process fails. Instead, theprocess should go into a HALTED state.

BX-3499(BX-3476)

The setAvailableProcessInstanceVariables API does not support arrays.

BX-3490 When using the queryApplication REST API, an empty "" is required in the requestfor the call to work.

BX-3485 Debugger client has a mismatched SOAP version if the BPM node is set to adifferent SOAP version.

34


Key Information

BX-3484 If a process is making a call to calendarService that failed with a transaction issue,this causes the process to go into a HALT ON ERROR state and, ultimately, theprocess fails. Instead, the process should go into a HALTED state.

BX-3456 Debugger inconsistently throws various exceptions.

BX-3452 An ad-hoc activity added during a migration is not initialized by an activity thathas already executed prior to a migration, but can be initialized by an activity thatexecutes after a migration. If you want the ad-hoc activity to execute after amigration, you can use a migration point activity to initialize an ad-hoc activity.However, this is an issue if you have an embedded sub-process, as you can onlyadd a migration point on an embedded sub-process, and not on the activitiesinside.

BX-3433 Ad-hoc API enhancements. Please see TIBCO ActiveMatrix BPM Developer's Guidefor more information.

PVM-661(PVM-660)

Allow the purgeTerminatedProcessInstances API to accept a FAILED status. Thisallows you to use the purgeTerminatedProcessInstances API to delete either failedor faulted process instances by passing the status as either FAULTED or FAILED.

PVM-659 The QueryProcessInstance API does not return custom data for completed andtruncated process instances if they are marked for deferred purge.

PVM-653(PVM-652)

Performing a Force Undeploy of an application that has an active inline sub-process fails.

PVM-651(PVM-649)

When process manager fails to handle a failed error event, it discards the nestedevent error and marks the process as HALTED. This means that it cannot recoverbecause the event is discarded.

35


Key Information

PVM-614 The Process Engine maintains a queue of work requests to process. Depending onthe number of items in the queue, the engine retrieves further requests from thePVM_REQUEST_QUEUE database table. Although the settings that control thefrequency of this retrieval are suitable for most installations, you may want tochange them to increase efficiency.

Use ActiveMatrix Administrator to update the Java Virtual Machine (JVM)configuration for the ActiveMatrix BPM nodes, as explained in the TIBCOActiveMatrix® BPM SOA Administration Guide. Add (and set) one or more of thefollowing properties on the JVM Configuration page within the Configuration tab:

● com.tibco.bx.groupRQ.batchSize

The number of new requests to retrieve from the PVM_REQUEST_QUEUEtable at a time. Default: 25.

● com.tibco.bx.groupRQ.fillLevel

The maximum number of requests in the request queue. When this number isreached, the engine stops checking the PVM_REQUEST_QUEUE table for newrequests. Default: 50.

● com.tibco.bx.groupRQ.lowWaterLevel

The minimum number of requests in the request queue. When this number isreached, the engine starts checking the PVM_REQUEST_QUEUE table for newrequests. Default: 10.

● com.tibco.bx.groupRQ.idleSleep

If there are no requests in the PVM_REQUEST_QUEUE table, this is the amountof time (in ms) that the engine sleeps before it checks the table again for newrequests. Default: 100.

ClientsThe section lists closed issues for Forms, Openspace and Workspace clients in TIBCO ActiveMatrixBPM 4.0.0.

TIBCO FormsThis topic lists the TIBCO Forms closed issues in TIBCO ActiveMatrix BPM 4.0.0.

Runtime

Key Information

FORM-6755 The description of forms_compact_mode has changed to the following: "The keyapplies to all controls and panes on a form to make the form smaller in size. Whenthe value contains 1, the width of the grid panes in the form is set to a maximum of600 pixels. When the value contains 2, the labels align to the top even if the childlabels are configured to be aligned to the left. However, if the pane has onlycontrols in it, the labels are not aligned to the top. When the value contains 3, itreduces the spacing between controls along with the spacing between labels andvalue fields within a control. The default value for the runtime is [3]. If you want todisable the compact mode, specify an empty value for it in the custom propertyresource bundle."

36


Key Information

FORM-6748 When using forms_compact_mode, the spacing should be reduced between andwithin the controls.

FORM-6746 If you have a form with a date control and you refresh the form, the date no longerdisplays.

FORM- 6726 Validation error markers are not seen for failed validations on required controls ina grid pane.

FORM-6725 Label control values display with an outline border. Users sometimes mistake thisfor an additional text field on the form.

FORM-6724 Specifying the key forms_compact_mode in the common resource bundle does notaffect the rendering of modal dialog panes.

FORM-6721 (Only applies to Openspace) Hint provided to grid pane control is not alignedproperly.

FORM-6704 An exception is thrown when a form contains both a BOM class reference and aglobal data reference.

FORM-6700 (Only applies to Internet Explorer version 8) Sometimes glyphicons are not visible.

FROM-6508 If you change the locale of a form, the changes do not take effect if there is a customcontrol on the form.

FORM-6495 When specifying a resource validation for a form, an exception is thrown.

Openspace

Key Information

OS-3085 Ad-hoc searches have been added to the Case Management gadget. Ad-hocsearches enables you to create a one-off search, based on one or more top-levelattributes of a case class. See "Case Management Gadget" in the TIBCO® OpenspaceUser's Guide for more information.

OS-3083 The OK button is inactive on some warning and error dialogs in the Calendargadget.

OS-3070 When comparing case model revisions in the Data Admin gadget, the output doesnot fit into the window.

OS-3068 In the Resources column of the View Recipients page in the Work Views Wizard,the font is too small.

37


Key Information

OS-3061 If a username is entered with leading or trailing spaces, the usernames are notconsidered for authentication correctly. TIBCO Openspace does not strip thespaces. This results in multiple entries in the internal Openspace user tables.

OS-3059 The hover text for Language displays the country name instead of the language.

OS-3058 If a case action fails in the Case Management gadget, a blank page displays. Youmust refresh the Case Management gadget to continue.

OS-3040 Truncation issues when defining an integer value in a case view filter condition inthe Case Management gadget.

OS-3033 In TIBCO Openspace, when retrieving a document associated with case data, youmust provide the document filename as well as the document reference. Youshould only have to provide a document reference, as TIBCO Openspace should beable to obtain the document filename by querying the server.

OS-3008 (Only applies to Internet Explorer Version 11) "Logout" is overlapping with verticalscroll bar in Openspace.

OS-3005 Update the Ad-hoc gadget in TIBCO Openspace. Please refer to the documentationfor the Case Management Gadget in the TIBCO® Openspace User's Guide for moreinformation.

OS-2978 When using the Jaspersoft dashboards in TIBCO Openspace, the dashboards canfind users based on a GUID and find GUIDs based on a resource. However, ifTIBCO Openspace is localized for Russian, Korean or Chinese, the dashboards areusing invalid encoding of the UTF-8 usernames. In this situation, the dashboardsare not returning GUIDs for valid usernames, or finding GUIDs based on a validusername.

OS-2977 The Jaspersoft Statistics dashboard pulls in an external CDN file. This causes anerror if the user has no external web access.

OS-2976 Improve error message that you receive when trying to open a work item that isnot offered or allocated to you. The current error message is "Cannot open workitem".

OS-2974 When viewing ad-hoc activities for a work item, it is possible to cancel the workitem. You should not be allowed to cancel a work item that you are currentlydisplaying the form for.

OS-2973 A new max.page.size property has been added to the Case Management gadgetconfig.properties file. The max.page.size property allows you to configurethe number of case IDs to display in the Case Management gadget. Please seeTIBCO® Openspace Customization Guide for more information.

38


Key Information

OS-2968 After selecting Enter in the Case References Filter page, when you first select eitherPrevious or Next, the same case records display. If you select Previous or Nextagain, the records display correctly.

OS-2965 If a process has disabled ad-hoc activities, then a "There are no ad-hoc activities"message should display.

OS-2961 You can use query parameters in forms, for example, the form refresh queryparameter "tibco_enhanced_ui". However, none of the form query parameters areworking in the Case Management gadget.

OS-2958 Openspace (Accessible Variant). The text on the Submit button vanishes after anincorrect login attempt.

OS-2953 (Only applies to Mozilla Firefox) In the Data Admin gadget, if you hover over theCase model, the Details dialog displays. However, you are not able to scrollthrough it.

OS-2951 Inactive Gadgets on the Preference Panel start as minimized when activated.

OS-2950 When using Oracle and adding a web site gadget, if no category is specified, aNULL is inserted. (It is blank if you are using SQL server). This causes issueswithBPM startup as a null pointer prevents Openspace from starting. It also meansadded gadgets cannot be deleted.

OS-2946 (Only applies to Mozilla Firefox and Chrome) If you have a multi-columned formin Openspace and the first column consists of check boxes, the check boxes are notaligned correctly.

OS-2944 URL query parameters are not propagating to gadgets that run in iFrames.

OS-2940 (Only applies to Chrome) If you login to Openspace, and switch to a new tab andthen switch back to your previous tab, the options in the upper right hand side ofthe window, for example, Refresh, Maximize, Menu and so on, disappear.

OS-2921 Pressing ENTER on the Login page, without providing any login informationcauses the frames to disappear.

OS-2920 Substitute variables for static strings cannot be used for product strings that need tobe translated.

OS-2915 From the Case Management gadget, if you are viewing work items associated witha case and then close and re-open Work View, the Work View loses the casereference.

OS-2910 From the Case Management gadget, if you create a new process instance from acase reference and then select Refresh, to refresh the list of process instances, anerror displays.

39


Key Information

OS-2909 When you are in one of the Case Navigation pages in the Case Managementgadget, the page navigation box does not display correctly. If there are no furtherpages, the Next Page should be disabled.

OS-2908 Due to the introduction of ad-hoc events, a process flow can be interrupted andresumed. The graphical audit trail in the Process Template gadget currently doesnot reflect this.

OS-2907 When an action is performed on case data, the case action page closes and the useris returned to the main Case Management page. However, the case where the caseaction was performed is no longer selected.

OS-2904 There is overlap in the Customizing Columns field on the Process Views gadget.

OS-2894 In the Case Management gadget, if you try to view the contents of a work itemassociated with a case ID and you do not have the correct privileges, no errordisplays to warn you and the Preview tab is empty. This may cause confusion ifyou have previously viewed work item data successfully in the Preview tabbecause you viewed a work item that you did have the correct privileges to.

OS-2885 When using the Chinese language pack, some time zones are not translatedcorrectly in the Calendar gadget.

OS-2884 The Help URL's for Openspace and Accessible Openspace should be updated topoint to the TIBCO ActiveMatrix BPM 3.1.0 Help.

OS-2844 In the Audit tab on the Process Views gadget, a message start event in a non-interrupting event sub-process should be displayed with a dashed line instead of asolid line.

OS-2840 Improved search feature in the TIBCO Openspace Case Management gadget.Please refer to the documentation for the Case Management Gadget in the TIBCO®

Openspace User's Guide for more information.

OS-2839 Support for parameterized views in the TIBCO Openspace Case Managementgadget. Please refer to the documentation for the Case Management Gadget in theTIBCO® Openspace User's Guide for more information.

OS-2799 You cannot change the order of the columns for deleted users in the OrganizationBrowser.

OS-2780 Support parameterized case views in the Case Management gadget. Please refer tothe documentation for the Case Management Gadget in the TIBCO® OpenspaceUser's Guide for more information.

OS-2646 When selecting a new language from the Language drop-down list, an errordisplays.

40


Key Information

OS-2519 If you want to delete a large number of resources, you must delete users in groupsof 83, otherwise a "FULL headError" message is displayed and the request fails.

OS-2507 When clicking the Next/Previous buttons in the Calendar gadget, a blue borderdisplays, overlapping the month.

Workspace

Key Information

WS-1648 When viewing events for completed sub-process instances, the Event Viewerdisplays "Sub process instance 'null'".

WS-1646 When attempting to view a parameterized case view in Workspace, an"IndexOutOfBounds" exception is displayed.

The exception has been replaced by a message that states that parameterized caseviews are not supported in Workspace.

WS-1643 After a specific sequence of events involving defining a sort order for a work view,the fields in the left pane of the Sort dialog cannot be moved to the right pane toinclude them in the sort definition.

WS-1642 When opening a large form in a separate browser window, using Internet Explorer,a scroll bar is not available, preventing access to all fields on the form.

WS-1640 When creating a process view for halted process instances, the Filter and Sortdialogs show duplicate fault-related attributes. If one of the duplicate attributes ismoved to the right pane, it cannot be moved back to the left pane because itsduplicate is still there.

WS-1638 If you create a system view, then attempt to edit the recipient view, a message isdisplayed that states "A system view with this name already exists. Please enter aunique name." The Name field for the view is disabled, and you cannot proceedany further with the edit wizard.

WS-1637 For events with a messageId value of BX_CUSTOM, the Event Viewer needs todisplay the value of the Extended message attribute, rather than the value of theMessage attribute, in the Description column for the event.

WS-1636 If user access is denied to all the items in the Help menu, the menu is correctly notvisible after login. However, if the browser is refreshed and the application uses theexisting session and bypasses the login screen, the Help menu is displayed.

WS-1635 When work item forms are opened in a dialog, when the form first opens or if thedialog is resized, form contents do not resize accordingly to fill the dialog.

WS-1632 When starting a business service, or opening a work item form, using theopenworkitem application, the form does not display and a "Form load failed"error is generated. The frequency of the error varies with the type of browser beingused.

41


Key Information

WS-1631 If you have a language other than English selected in the application, and youcreate a new view, but specify an invalid value when filtering on a date attribute,the resulting message window contains an OK button that is not properly localizedto the selected language.

WS-1626 Login fails if the user name contains multi-byte characters (for example, Chinese orJapanese characters).

WS-1623 If an event view is created using the "All" pre-defined filter (rather than the"Summary" pre-defined filter), then the view is saved, all of the events are notsaved in the event view.

WS-1622 When specifying a filter expression in Event Views, entering multi-byte charactervalues into the expression might lead to a parsing error from the server.

WS-1621 Performing a "Save As" for an event view causes a Save View As dialog to bedisplayed with a disabled OK button. Changing the name of the view on the SaveView As dialog does not cause the button to become enabled.

WS-1613 When temporary Event Views are created, by selecting Open Event Viewer fromthe Work Items or Process Instances lists, when the user subsequently tries to usethe Remove All Temporary Views tool on the Events Views list, an exceptionoccurs and the items are not removed.

WS-1611 Creating a case view for cases that don't have case references returns an exception.

WS-1609 When a work view is created using multi-byte character values in the name of theview, and then the name of the view is edited, the name might show as Unicodevalues for the characters rather than the actual characters.

WS-1603 Scroll bars always appear on work item forms opened in the Preview Pane, evenwhen the content is smaller than the Preview Pane. The scroll bars partially coverthe form elements.

WS-1602 If a custom interface is defined to open in a separate browser window, when theinterface is invoked, an empty browser window opens; the custom interface is notdisplayed in the window.

WS-1600 When Custom Interfaces are defined for the Master Selection area (buttons in lowerleft), if they are of type "scriptedInterface," they fail to load when invoked; the logshows "obj is undefined".

WS-1599 When the user's login session is invalidated, either because of a server timeout orthe user logged out of a second browser instance of the Workspace application, anysubsequent actions by the user result in a corrupt layout displaying both pre-loginand post-login components.

WS-1595 The strings "Inbox" and "Master" (for a system view) on the Auto-Refresh dialogare not properly localized to the selected language.

42


Key Information

WS-1594 If a process instance attribute contains a CDATA section (more specifically itcontains the ]]> closing CDATA tag), the View Details button on the ProcessSummary pane in Process Views does not load the details. Also, if a businessservice or work item form is submitted, and it has a text field that contains aclosing CDATA tag, the data is not saved correctly and an error may occur.

WS-1592 The hover text for the Restore Down icon in the upper-right corner of theConfiguration Administrator dialog is not being properly localized to the selectedlanguage.

WS-1589 When a performer field is used for the participant of a user task, "Allocate WorkItem(s) To Offer Set" fails to return any resources for the offer set.

WS-1588 If a work view has a very long name, the name can overlap the close (X) icon on theAuto-Refresh dialog.

The Auto-Refresh dialog can now be re-sized to prevent the overlapping.

WS-1587 Some strings on the Event Viewer are not being properly localized to the selectedlanguage.

WS-1586 If the description for an event view is changed, the hover text for the description inthe Event Viewer still shows the previous description.

WS-1581 When using the German language pack, some of the text on the Pend Work Item(s)dialog is being truncated.

WS-1579 If an attempt is made to open a work item that is not offered or allocated to you,the following message is displayed, which does not describe the issue: "The ActionProcessor returned the service exception: EX_INTERNAL_SERVICE_FAULT".

A more descriptive message is now displayed in this situation.

WS-1573 If you name a work view, process view, case view, or event view using longdouble-byte strings, the name can overlap other information in the view.

WS-1572 When using the Korean or Chinese language packs, the Event Viewer only displaysthe time as a 12-hour clock.

WS-1526 When editing a process view, and Include all processes is selected on the EditProcess View dialog, the entire list of processes is incorrectly displayed in theAvailable Processes section. The list should be empty in this situation.

43


Known Issues

The known issues in TIBCO ActiveMatrix BPM 4.0.0 are listed per component:

● Platform● Core Components● Clients

PlatformThis topic lists the known issues for the TIBCO ActiveMatrix Platform in TIBCO ActiveMatrix BPM4.0.0.

Administrator


TAP-9568 Summary Errors are seen in the Administrator UI when deploying a BPM userapplication when one of the nodes is not available.

Workaround The error dialog can be dismissed. The application will deploy and start fineon the running nodes.

TAP-9402 Summary When using TIBCO Business Studio to deploy a DAA that is dependant onanother DAA which is not in the deployed state results in errors such as:Follower application component urn:amx:BPMEnvironment/com.example.appa/APPAProcessFlow requires capability com.tibco.amf.sca.model.componenttype.impl.RequiredCapabilityImpl@7ee0f191 (id: com.tibco.bx.capability.implementation.bx, version: 1.0.0, type: factory) but the target application does not provide it.

Workaround Make sure the dependant DAA is deployed.

TAP-9380 Summary When a new node is added, the synchronization flag for the BPMapplication, amx.bpm.app, shows Out of Sync.

Workaround The application being out of sync won’t prevent or cause problems forapplication deployed to the new nodes.

To sync the BPM application, amx.bpm.app, select the application and clickDeploy.

44



TAP-9351 Summary When you change the nodes to which the BPM application, amx.bpm.app, isdistributed and if you remove a node and then redeploy, the application failsto start.

Workaround None.

TAP-9344 Summary ActiveMatrix BPM applications use the Product Distribution mode whereyou distribute to a target application amx.bpm.app and not to specific nodesin an environment. If you visit the Distribution tab for your application, youwill see the node based distribution for your application components. TheDistribution tab appears to allow editing of the node distribution for yourapplication components. However, you cannot change the componentdistribution this way while using Product Distribution mode. Modifying thenode distribution for components and then clicking Save does not actuallychange the distribution. It will simply revert to the original distribution. Thedistribution for components should've ideally been made as read-only.

Workaround None.

TAP-14067 Summary: If you upgrade a case data application - for example, from V1.0 toV1.1, then add a new BPM node to the system, custom features related to V1.0of the case data application are not copied to the new node. V1.0 of the case dataapplication does not then work on the new node. This could impact a user'sability to progress outstanding work items for any process application thatreferences V1.0 of the case data application, if the process instance is handled bythe new node.

Workaround: None.

TAP-12878 Summary If you import a resource template into an upgraded user application that didnot previously contain a resource template (that is, if no resource templateshad previously been imported into the application), the scope of the importedresource template will automatically be set to Global, rather than Application.This occurs even if you specify Application scope in the CLI.

Workaround After the resource template is imported (to Global scope), you change itsscope as required (to Application scope, for example) in the ActiveMatrixAdministrator UI. To do this:

1. Go to Shared Objects > Resource Templates .

2. Select the imported resource template.

3. Click Change Scope, and change the scope to the Application orEnvironment level as desired.

45



TAP-12860 Summary If you have a main process and a sub-process application and one or moredependent main process applications deployed in ActiveMatrix Platformversion 3.1.5 (and any ActiveMatrix BPM version between 1.3.0 and 2.1.0),then upgrade the BPM platform version to ActiveMatrix BPM 2.2.0(ActiveMatrix Platform 3.3.0), and subsequently attempt to upgrade thesubprocess, you will see a warning similar to the following example:TIBCO-AMX-ADMIN-012430: Provided capability 'com.example.my.subprocess.pe.capability' provided by component 'MySubAppProcessFlow' cannot be removed. It is being used by the following components:Component 'MyMainAppProcessFlow' from application 'com.example.my.mainapp.process

This warning is issued erroneously and can be safely ignored. The subprocesswill be upgraded successfully and the main processes will run fine, providedthe sub-process maintains the same major version number as before.

Workaround None.

TAP-12858 Summary The logging configuration of a node, host, or application (which is stored inthe node, host, or application’s log4j.xml; for example, node-log4j.xml)may enter into an inconsistent state if the node, host, or application uses aJMS appender that is configured with an SSL-enabled EMS server. In thiscase, the logging configuration uses an HTTP URL to refer to a keystore that’shosted on the Administrator. This HTTP URL is the internal HTTP connectorURL of the Administrator.

Changing the configuration of the internal HTTP connector (for example, toenable SSL or change the port number) causes the URL configured in thelogging configuration (log4j.xml) to become invalid or out of synch. Thelogging configuration of each affected node, host, or application needs to beupdated or it will fail to connect to EMS.

Currently this is not done automatically.

Workaround You must manually save and apply the logging configuration for each node,host, or application that uses a JMS appender. To do this:

1. In the Administrator UI, go to the logging configuration for the node, host,or application that’s in the situation described above.

2. Change a value in the logging configuration that makes the node, host, orapplication go out of synch.

3. Click Save.

4. Click Apply. This pushes the new logging configuration, with a newHTTP URL, to the node, host, or application.

46



TAP-12738 Summary If you delete a binding in the ActiveMatrix Administrator UI, that bindingwill still be visible in the SPM Dashboard with a Down status. This occursbecause the Delete notification for the ActiveMatrix binding component is notbeing emitted.

Workaround None.

TAP-12714 Summary ActiveMatrix Administrator does not properly undeploy applications withmissing feature dependencies.

Workaround To avoid this issue, go to Node > Configuration > Features and remove thefeature with Marked for Install and a blank value for Type. You should beable to undeploy the application with no issues.

TAP-12702 Summary If you use TIBCO Configuration Tool to edit Administrator databasesettings, the following harmless error may appear in SystemNode.log: Couldnot open Hibernate Session for transaction.

Workaround None.

TAP-12087 Summary Making changes to the configuration of a JDBC service resource templatethat is a dependency for a running application may cause that application toenter a Stopped state.

Workaround Manually restart the stopped application.

47



TAP-11318 Summary If you use Mozilla Firefox as a web browser, TIBCO ActiveMatrixAdministrator may display a blank page when opened.

Workaround To avoid this issue:

1. In the Firefox address bar, enter about:config

2. Click "I'll be careful, I promise!"

3. In the search field, enter javascript.options.ion.content

4. Set the Value for javascript.options.ion.content to false

5. Restart Firefox in Safe Mode. See the following URL for more informationabout starting Firefox in Safe Mode: https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode#w_how-to-start-firefox-in-safe-mode

TAP-10854 Summary In an upgraded environment product applications are not auto-provisionedby default.

Workaround Either manually deploy the product applications or enable auto-provisioning for the environment and create a System folder for theenvironment.

If the product application is present in the environment but missing from thenode, move the product application to the System folder.

TAP-10830 Summary When wiring a reference to a service in the same application that has a SOAPbinding using an HTTP Connector that does not exist results in the followingexceptionError generating the WSDL for binding SOAPService_Binding1, Caused by: Could not find resource instance with name httpConnector when generating WSDL for binding SOAPService_Binding1 on service NewService

Workaround Create the HTTP Connector before creating the application.

48



TAP-10800 Summary When creating an Administrator server with an Oracle database thefollowing error messages are seen in the SystemNode log files:SystemNode 30 Jul 2012 16:42:48,287 [WAR-Deployer-Thread] [ERROR] org.hibernate.tool.hbm2ddl.SchemaUpdate - Unsuccessful: create index AdmnCnfig_sttsNtifictinTrnsprt on "ADMINCONFIG" ("NTFCTNTRNSPRT_STTSNTFCTNTRNS_D") SystemNode 30 Jul 2012 16:42:48,287 [WAR-Deployer-Thread] [ERROR] org.hibernate.tool.hbm2ddl.SchemaUpdate - ORA-00955: name is already used by an existing object SystemNode 30 Jul 2012 16:42:48,303 [WAR-Deployer-Thread] [ERROR] org.hibernate.tool.hbm2ddl.SchemaUpdate - Unsuccessful: create index AMXdminsrPrfrncs_prvisnvslctin on "AMXADMINUSERPREFERENCES" ("PRVISNVSLCTIN_PRVISNVSLCTIN_ID") SystemNode 30 Jul 2012 16:42:48,303 [WAR-Deployer-Thread] [ERROR] org.hibernate.tool.hbm2ddl.SchemaUpdate - ORA-00955: name is already used by an existing object......SystemNode 30 Jul 2012 16:42:48,319 [WAR-Deployer-Thread] [ERROR] org.hibernate.tool.hbm2ddl.SchemaUpdate - Unsuccessful: create index ApplicationFolder_childFolders on "APPLICATIONFOLDER" ("APPLICATIONFOLDER_PARENT_E_ID") SystemNode 30 Jul 2012 16:42:48,319 [WAR-Deployer-Thread] [ERROR] org.hibernate.tool.hbm2ddl.SchemaUpdate - ORA-01408: such column list already indexed

Workaround These errors can be safely ignored as the indexes are created.

TAP-10767 Summary HTTP Connector resource instances that are referenced by properties whosenames are not specific, such as HttpInboundConnectionConfig orhttpConnector, are not recognized by Administrator as HTTP Connectorswhile displaying information. As a result these HTTP Connectors are notdisplayed in the Administrator UI as dependencies where expected.

Also, you can delete any such HTTP Connector even when it has dependentapplications.

Workaround Use property names such as HttpInboundConnectionConfig orhttpConnect to refer to HTTP Connectors resource instances. Additionallywhen deleting a HTTP Connector resource instances manually check whetherother applications are dependent on it.

49



TAP-10751 Summary Executing the scripts generated by the DDL Script Generator for MicrosoftSQL Server displays errors reporting a failure to create foreign keyconstraints.

Also, even if the generated scripts are not used, error messages are seen in theSystemNode log file logged in SystemNode.log regarding failure to createforeign key constraints.

Workaround None. These errors can be ignored as a failure to create foreign keyconstraints does not impact product functionality.

TAP-10663

DSS-527Summary Heterogeneous environments with mixed JREs are not supported. Sun JRE isnot compatible with IBM JRE when it comes to storing secret keys in a Javakeystore. This causes a problem when the Administrator server running onSun JRE stores a username and password in its global identity keystore and ahost and node running on IBM JRE attempts to access that username andpassword. The reverse, Administrator on IBM JRE and host and node on SunJRE would have the same problem.

Workaround Ensure that Administrator, TIBCO Host instances, and nodes are all usingJREs provided by the same vendor.

TAP-7784 Summary After creating and starting a node, if you try to stop and uninstall the nodewhen its runtime state is Running and the Action History state is In Progress,the node will fail to get uninstalled.

Workaround Wait for the Action History state to change from the In Progress state to onethat matches the chosen action before selecting another action for the node.

TAP-7644 Summary You may see the following error message when undeploying an application[ERROR] com.tibco.amf.admin.server.axis2.RPCMessageReceiver - Error occured in Administrator... about to throw AxisFault for this exception

Workaround Refresh the browser. This error message can be safely ignored.

50



TAP-7571 Summary Users who have permissions only to view an application and anenvironment but do not have permissions to view a node are not able to seethe list of selected nodes when distributing an application.

Workaround Permissions to view the node have to be explicitly granted by a superuser.

TAP-7423 Summary You may see an Errors in dashboard dialog box when using the Dashboard.

Workaround Click OK to proceed using the Dashboard. This error message can be safelyignored.

TAP-6584 Summary When the extended monitoring is enabled the two new periodic windows(24 hours and 7 days) do not show on some Dashboard tabs.

Workaround Refresh the browser.

TAP-5653 Summary Updating the value of a substitution variable for the Timeout property in aJMS or SOAP/JMS binding in a deployed application does not take effect afterthe application is redeployed.

Workaround .Undeploy and deploy the application.

TAP-4890 Summary In the dashboards, a text filter is ignored when you maximize or minimize agadget.

Workaround Re-enter the text filter.

TAP-4645 Summary In the Dashboards > Infrastructure screens, resource instances cannot befiltered by promoted reference or promoted service.

Workaround In the Application Screen, check properties of the reference or servicebindings.

51



TAP-3698 Summary On Windows, the folder containing a TIBCO Host instance cannot be moved,copied, or deleted when the RuntimeWorkArea file name length is longerthan 255. This occurs if you select the default value for CONFIG_FOLDER whenrunning TIBCO Configuration Tool.

Workaround Delete the folder using rmdir /s /q.

PER-49 Summary When configuring an LDAP Authentication resource template inAdministrator, the option to generate SAML 1.1 assertion is not supported byplatform policies.

Workaround When configuring an LDAP Authentication resource template, accept thedefault setting to generate SAML 2.0 tokens.

MCR-1823

TAP-10602Summary The value for the uptime displayed in the infrastructure dashboard screensare accounted from the time a request is made to the application by invokingthe endpoint or through an internal call from another application.

If an application is deployed and not used, the value for uptime will be 0.

Summary None.

MCR-1422 Summary If nodes are restarted when the SystemNode is down, the Uptime and SinceStarted statistics are not reset.

Workaround Either make sure that the system node is running using admin replication orrestart the applications for which incorrect statistics are seen.

MCR-1350 Summary The number of components reported for a given node in the EnterpriseGraphical View includes components that belong to the ActiveMatrixPlatform Application. The Dashboard component count does not includethese components.

Workaround None

52



MCR-1226 Summary The Endpoint, Service, and References tabs display an incorrect value forAvg Comp Process Time when extended monitoring is enabled. The valuedisplayed is Req Comp Time.

Workaround The correct average component processing time is available in theComponents and Applications tabs.

MCR-1205 Summary If the TIBCO Host is shutdown while the Dashboard is running, thefollowing error message is seen in the SystemNode log files:[ERROR] org.apache.axis2.engine.AxisEngine - bean:name=govObjFilterServiceMBean

Workaround None. This error can be safely ignored.

MCR-1204 Summary Stopping the TIBCO Host instance occasionally causes exceptions to bethrown in the log file. During a graceful stop of TibcoHost instance there maybe some exceptions in the log file with the root cause "Caused by:java.lang.RuntimeException: Statistics aggregator is closing down, rollingback transaction".

Workaround Ignore the error.

MCR-1162 Summary Statistics for Web Application components do not display in the dashboard.

Workaround None.

MCR-876 Summary Status value is "Unknown" and uptime is empty when the same applicationis deployed on two nodes across environments.

Workaround Change the application name during deployment. It must be unique for anenterprise for dashboard to show correct status and uptime.

53



MCR-800 Summary When a component reference is promoted, component reference metricsshow zero values. All metrics are shown on the promoted reference andreference endpoint.

Workaround View metrics on the promoted reference.

MCR-753 Summary In the Dashboards > Infrastructure screens the application request countincludes requests counts from all services promoted to application level. Inaddition, it incorrectly includes reference invocations count from allreferences promoted to application level.

Workaround None.

MCR-521 Summary If a node is stopped or started several times while SystemNode is down, thelast stop or start time of SystemNode is used to calculate the node’s uptimepercentage. Other stops and starts are missed and not used in uptimecalculation.

Workaround Configure the Administrator server in fault tolerant mode.

AMX-10828 Summary If your BPM application refers to a OM project and if changes are made tothe OM project that break backward compatibility, errors are generated whenredeploying the BPM application.

Workaround Downgrade the OM project to the previous version.

WSBT-881 Summary Policies and policy sets cannot be added, edited, or deleted via theActiveMatrix Administrator UI. Policy set properties can be viewed but notadded, edited, or deleted.

Workaround Edit policy sets and properties in TIBCO Business Studio.

54



SVCP-86

SVCP-84Summary The TIBCOActiveMatrix Service Performance probe on the Administratornode does not receive self-shutdown notifications sent from TIBCO Host. Thisoccurs because the Service Performance Manager probe component on theAdministrator node responsible for such communication shuts down before itcan send the notification.

Workaround None.

Installer


INST-164 Summary The TIBCO Universal Installer does not display the products to be installedcorrectly.

Workaround Note the discrepancies. There is no action required.

MCR-1943 Summary If you have upgraded to ActiveMatrix release 3.3.0 from a prior version andattempt to replicate the upgraded configuration, deploying the replicatedconfiguration may fail.

Workaround Replicate your configuration before upgrading to ActiveMatrix release 3.3.0.

SDS-5917 Summary The installer downloads Hibernate and Eclipse LPGL assemblies required byTIBCO Business Studio and TIBCO Configuration Tool. In a suite installationscenario, if you unzip all product archives into the same directory, you mightoverwrite the 3.1.5 installer with a 3.1.2 installer. The 3.1.2 installer won'tdownload the required assemblies, which will lead to failure of TIBCOBusiness Studio and TIBCO Configuration Tool.

Workaround When you unzip all products in the same directory while preparing for asuite install, make sure you preserve the installer binary from the most recentproduct installation. When you run the installation, the version of the 3.1.5installer in the About dialog is 2.9.4.

55


Runtime


AMRP-5306 Summary: On TIBCO ActiveMatrix BPM version 4.0, .zip files or .pdf files that areuploaded to the CMIS repository may be corrupted. Content is lost and the filescannot be opened if they are downloaded.

Workaround: None.

This issue is resolved by TIBCO ActiveMatrix Platform 3.3.0 Hotfix 012.

AMRP-5232 Summary: A form fails to load and an java.io.IOException: write beyondend of stream Error" error is reported. This error only occurs on systemswhere TIBCO ActiveMatrix Platform 3.3.0 Hotfix 10 has been applied, and iscaused by an HTTP compression issue.

Workaround: To avoid this problem, disable the use of HTTP compression by theBPM runtime. To do this, add the following property:java.property.com.tibco.amf.hpa.tibcohost.jetty.disableCompression=true

to the CONFIG_HOME\tibcohost\Admin-enterpriseName-adminServerName\data_version\nodes\BPMnodeName\bin\BPMNode.tra file.

Support for this property was introduced in TIBCO ActiveMatrixPlatform 3.3.0 Hotfix 012.

AMRP-4754 Summary If a service provider and a service consumer exist in the same BPM application,undeploying the application may undeploy the service provider even thoughthe service consumer still requires the service provider.

Workaround Separate the service consumer and the service provider so that they’re both intwo separate user applications.

56



AMRP-4744 Summary If you upgrade ActiveMatrix BPM to release 2.2.0 and ActiveMatrix to release3.3.0, and upgrade a pre-existing user application so that it’s a web serviceimplementation with REST enabled, you may see exceptions similar to thefollowing in the logs during the reply message event although the response issuccessfully received:[INFO ] stdout - java.io.IOException: Exception in opening zip file: C:\ProgramData\amx-bpm-2.1.0v12\tibco\data\tibcohost\Admin-AMX BPM-AMX BPM Server\data_3.2.x\nodes\BPMNode\work\cf\cdfa6b9e-d49d-4764-8623-fa331f8820c3\bundle28 Aug 2013 16:52:32,824 [Framework Event Dispatcher] [INFO ] stdout - at org.eclipse.osgi.framework.util.SecureAction.getZipFile(SecureAction.java:291)28 Aug 2013 16:52:32,824 [Framework Event Dispatcher] [INFO ] stdout - at org.eclipse.osgi.baseadaptor.bundlefile.ZipBundleFile.basicOpen(ZipBundleFile.java:87)

Workaround Restart the node in which the application is deployed.

AMRP-4736 Summary You may not be able to start amxbpm as a Windows Service after upgrading toActiveMatrix release 3.3.0 from release 3.1.5 (or previous releases) orActiveMatrix BPM release 2.2.0 from release 2.1.0 (or previous releases).

Workaround If you encounter this issue:

1. Launch a command prompt where tibcohost.exe is located.

2. Uninstall existing ActiveMatrix BPM windows service by executingtibcohost.exe --uninstall

3. Install the windows service again by executing tibcohost.exe --install

AMRP-4639

DSS-811Summary The default JSSE provider for Oracle's Java 7 has introduced a bug with theDiffie Hellman Ephemeral (DHE) key exchange. (See the description in Oracle’sbug database for more information: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=8013059) Establishing ciphers likeTLS_DHE_RSA_WITH_AES_128_CBC_SHA sometimes fails and gives the errormessage Received fatal alert: bad_record_mac. By default, SSLconnections with TIBCO EMS Server prefer the stream cipher RC4. You canoverwrite this behavior by explicitly choosing the ciphers either in SSLClient RTor in the EMS Server.

Workaround By default, no workaround is needed. If you do choose explicit ciphers, avoidthe DHE ciphers so that you do not run into this occasional Java 7 bug.Unaffected ciphers include TLS_RSA_WITH_AES_128_CBC_SHA, amongstothers.

57



AMRP-4445 Summary If you create and install an HTTP Connector resource instance for a runtimenode and assign it a port that is also used as an external or internal HTTP port ofSystemNode, users will encounter a 404 error when attempting to log in toTIBCO ActiveMatrix Administrator after the TIBCO Host instance has beenrestarted.

Workaround To avoid this issue:

1. Stop the TIBCO Host instance.

2. Go to \tibcohost\tibco_host_instance_name\data_3.2.x\host\plugins

3. Delete, move (or backup with a different name) the plugin whose name takesthe following form:

ri_HTTPConnector_Resource_InstanceName_NodeName_******.jar

4. Start the TIBCO Host instance.

Users should be able to log in to TIBCO ActiveMatrix Administrator.

You may also need to modify the HTTP Connector resource template to use aport that is not being used by an existing instance such as SystemNode or aruntime node.

AMRP-4013 Summary Acceptor threads for HTTP connectors may consume excessive amounts ofCPU. The processing performance of any node that uses an HTTP connectorexperiencing this issue may be affected when asynchronous IO is involved.

Workaround Edit the HTTP Connector Resource Template to use blocking IO. See thechapter Resource Templates in Administration for more information.

AMRP-3842 Summary Can't log into Workspace if trying to access it from a node that is running on amachine different than the one on which the Enterprise Message Service serveris running and the Enterprise Message Service server restarts.

Workaround Restart the node.

AMRP-3823 Summary Status is not updated in Administrator for when an application running onBPMNode experiences a database connection failure.

Workaround If a component is failing, try restarting the component.

58



AMRP-3788 Summary The LDAP resource template pool properties are not used when initializing theconnection pool.

Workaround Configuring the connection pool using system properties specified for thetarget node applies them to all instances deployed to that node.

Refer to the Oracle documentation for more information:

http://docs.oracle.com/javase/jndi/tutorial/ldap/connect/config.html

AMRP-3721 Summary The LDAP shared resource does not reconnect automatically to its associatedLDAP server.

Workaround Reinstall the LDAP shared resource instance and then restart all dependentapplications. Or, restart the node.

AMX-15265 Summary: On a system where TIBCO ActiveMatrix Platform 3.3.0 Hotfix 10 hasbeen applied, upgrading TIBCO ActiveMatrix BPM to version 4.0 fails when youtry to upgrade the ActiveMatrix BPM database. The following error is displayed:Error moving LDAP connections to the application: The max connection pool size is invalid. It can only allow a number OR a substitution variable.

(This error occurs because the upgrade sends a string value for the maxPoolSizeparameter for the sslServer resource template, but this value is now an integer asa result of a change in TIBCO ActiveMatrix Platform 3.3.0 Hotfix 10.)


AMX-15258 Summary: A process application containing a service task that calls a BPM service(that is, invokes any public BPM API operation) may not work as expected afterupgrade to TIBCO ActiveMatrix BPM version 4.0. In some circumstances, theapplication may not work at all.


AMX-15224 Summary: If you upgrade from TIBCO ActiveMatrix BPM version 2.1.0 to version4.0, the upgrade fails on the first attempt on the upgrade-admin step.

Workaround: Re-run the upgrade. The upgrade process completes successfully.

AMX-15212 Summary: On a system where TIBCO ActiveMatrix Platform 3.3.0 Hotfix 10 hasbeen applied, you cannot deploy a Decisions Service project from TIBCO BusinessStudio.


59



AMX-15209 Summary: In TIBCO ActiveMatrix BPM, BX audit messages do not always includecontextId, parentContextId and correlationId.

Workaround: None.

AMX-15201 Summary: After upgrading the JRE used by ActiveMatrix BPM to JRE 1.8, theActiveMatrix Administrator viewaction.jsp and viewdata.jsp pages cannot beaccessed. When you try to load the page an HTTP-500 error occurs - for example:Problem accessing /amxadministrator/viewaction.jsp. Reason: Unable to compile class for JSP: An error occurred at line: 333 in the jsp file: /viewaction.jspThe type java.lang.CharSequence cannot be resolved. It is indirectly referenced from required .class files

Workaround: None.

AMX-14346 Summary Suite installation of ActiveMatrix Service Grid 3.3.0 and ActiveMatrix BPM 2.2.0fails with the following error: More than one active 'Finish' task hasbeen defined.

Workaround Do not install ActiveMatrix BPM and ActiveMatrix Service Grid at the sametime using the Suite Installer.

AMX-14345 Summary Upgrading the second system node in a replicated Administrator setup can failwith exception(s) similar to the following example:

java.lang.IllegalStateException:

org.springframework.beans.factory.BeanCreationException: Error

creating bean with name 'urn:amx:SystemEnvironment/amx.platform-

app/GovernanceAgent/pepHttp/HttpFilterComponent_1.3.0': TIBCO-

AMX-IT-JAVA-SPRING-801001: Invocation of init method failed;

nested exception is java.lang.NoClassDefFoundError: javax/xml/

transform/TransformerFactoryConfigurationError

Start component 'wtplogservice' on node 'SystemNodeReplica' failed : java.lang.IllegalArgumentException: Exception during web application initialization. Deployment of web application failed

Workaround Upgrade the second system node again.

60



AMX-14310

DSS-817Summary ActiveMatrix release 3.3.0 packages IBM JRE 1.7.0 SR2. If you are runningActiveMatrix on an AIX platform and install Unlimited Jurisdiction Policy (UJP)files, you may encounter errors.

Workaround If you encounter errors, you must install the appropriate version of the UJPfiles for that build of the JRE.

Errors similar to the following example indicate that the version of the UJP filesis not the appropriate version for the installed JRE:Caused by: java.lang.SecurityException: Jurisdiction policy files are not signed by trusted signers!at javax.crypto.b.a(Unknown Source)at javax.crypto.b.a(Unknown Source)at javax.crypto.b.access$600(Unknown Source)at javax.crypto.b$0.run(Unknown Source)at java.security.AccessController.doPrivileged(AccessController.java:254)... 28 more

If you see such errors, you must install the appropriate version of the UJP files.

AMX-13851 Summary If you use Microsoft SQL Server 2012 as an external database server and use itsMirror Mode to establish a connection to a secondary failover database server,TIBCO ActiveMatrix Administrator fails to connect to either database server.

Workaround In addition to providing the JDBC URL of the mirrored servers in SQL Server2012, you must set the IP and hostname of both the primary and secondarydatabase servers in the hosts file. The location of the hosts file depends on theoperating system:

● Windows: ROOT_DIR\system32\drivers\etc\hosts

● UNIX/Linux: /etc/hosts

For example, you have two database servers. The primary server's IP is192.167.71.42 and its hostname is amx-db42; the secondary server's IP is192.167.71.60 and its hostname is amx-db60. You would provide thefollowing JDBC URL for these two mirrored primary and secondary servers:jdbc:sqlserver://

192.167.71.42:1433;databaseName=db1;failoverPartner=192.167.71.

60.

To ensure that TIBCO ActiveMatrix Administrator successfully connects toboth servers and allows for seamless switching between them using SQLstatements, you must add the following entries to the hosts file:192.167.71.42 amx-db42192.167.71.60 amx-db60

61



AMX-11984

TAP-12831Summary You are not able to replicate the Administrator server after upgrading from anearlier 3.1.x version.

Workaround Follow these before attempting the replication procedure:

1. Import basic_cli.xml in sharedWorkFolder_build.xml.

Modify the line<import file="${admin.samples.directory}/admin-scripts-base.xml"/> to <import file=”basic_cli.xml”/>

2. Edit sharedWorkFolder_data.xml

a. Remove the ApplicationFolder element.

b. Change the artifact server app name fromcom.tibco.amx.platform.artifactserver toamx.artifactserver.app.

c. Change the name of the internal HTTP connector name in thesubstitution variable element from TIBCO ActiveMatrix InternalHTTP Connector Resource totibco.admin.http.connector.internal.

AMX-11970 Summary In a replicated Administrator server setup if you deploy to the system nodeapplications with policies applied on them, those policies are not enforced afterupgrade.

Workaround First undeploy and then redeploy these applications after upgrading all systemnodes.

AMX-10757 Summary After shutting down and restarting a database accessed by a JDBC resourceinstance, Workspace throws an error.

Workaround Log into Workspace again.

62



DSS-813 Summary While upgrading to ActiveMatrix release 3.3.0, you may see benign errorssimilar to the following example:[ERROR]com.tibco.trinity.runtime.base.provider.identity.CipherSupport

Such errors are harmless and do not mean that the upgrade failed. No action isrequired.

Workaround None.

MCR-2002 Summary If you have configured Microsoft SQL Server 2012 as a database forAdministrator, invoking a custom DAA may result in harmless exceptionssimilar to the following examples:Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Violation of UNIQUE KEY constraint 'UQ__Mcr2Stat__1C012A471DC5DDE4'. Cannot insert duplicate key in object 'dbo.Mcr2StatisticsMetric'. The duplicate key value is (93, 21, 22, 3, -1).at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216)at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1515)at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:404) ... 44 more

Workaround None.

MCR-1995 Summary If you have configured IBM DB2 as an external database, you may see harmlessexceptions similar to the following examples in SystemNode.log:Retrying database transaction after error: Proceccing of metric requestsIn for event com.tibco.governance.amxserviceprobe.ServiceProbeInstruments.ServiceRequestIn failed for measure Total and time window Since Started Time WindowRetrying database transaction after error: Proceccing of metric faults for event com.tibco.governance.amxserviceprobe.ServiceProbeInstruments.ServiceExecutionTime failed for measure Total and time window Since Started Time Window

Such exceptions are benign and don’t require any action.

Workaround None.

63



PER-2121 Summary: A SOAP call to a BPM web service fails when trying to use a sender-vouches SAML request.

Workaround: None

TIBCO Hawk ActiveMatrix Plug-in


HKAM-266 Summary If the ActiveMatrix Administrator server or TIBCO Host instance isconfigured to use SSL-enabled Enterprise Message Service on AIX platform,and Hawk 5.0 is installed, then starting Hawk Agent fails giving an error.

Workaround Use Hawk 4.9 instead of Hawk 5.0.

HKAM-264 Summary Users cannot change the timeout of method invocation for Custommicroagent.

Workaround None.

HKAM-253 Summary Hawk Display shows multiple entries for node Service microagent whenrulabases for TIBCO Host or nodes are invoked after the TIBCO Host or nodecrash.

Workaround Click Done, and again open the microagent. Alternatively, restart HawkDisplay.

HKAM-251 Summary Continuous error messages are seen in the hawk.log file after startingtibhawkagent.exe on HAWK 5.0. Hawk 5.0 is unable to runpowershell.exe used in TIBCO Host rulebase.

Workaround Prefix powershell.exe in the rulebase of the TIBCO Host with the absolutepath of powershell.exe.

64



HKAM-250 Summary When using Hawk 5.0, logs are not generated in the CONFIG_HOME/hkam/<host_instance_name>/logs folder. The Hawk Agent shows errors relatedto slf4j in the Hawk logs.

Workaround Remove the slf4j jars and jars with different versions of slf4j from theagent classpath.

HKAM-249 Summary The Stop Reason and Reason Code arguments are not updated for theonNodeEvent method after calling stopNode.

Workaround None.

HKAM-242 Summary Hawk 5.0 cannot find Windows PowerShell.

Workaround Prefix powershell.exe in the rulebase of the TIBCO Host with the absolutepath of powershell.exe.

HKAM-237 Summary On creating a node in the ActiveMatrix Administrator web interface, itsrulabase is created in the CONFIG_HOME/hkam/<host_instance_name>/rulebases folder. If the node is deleted, the HAWK.log file continuouslyproduces errors.

Workaround Manualy delete the rulebase to avoid error entries in the HAWK.log file.

HKAM-193 Summary Hawk ActiveMatrix Plug-in displays some ActiveMatrix applications orcomponents in runtime state as uninstalled, but ActiveMatrix Administratoror nodeutil do not show these applications.

Workaround Restart Hawk Agent to clear the cache.

65


Core ComponentsThis topic lists the known issues of Core Components in TIBCO ActiveMatrix BPM 4.0.0.

Work Manager

Key Information

WRM-8699 Summary: When a process user application references a Business Data userapplication that is in "Preparing to undeploy" (since there is a later version of thebusiness data application deployed) and a node restart is performed at this point,subsequent BDS API operations (for example, createCase) that requires BusinessData user application (in "preparing to undeploy" status) will fail.

Workaround:

● From TIBCO Administrator, select the BDS application.● On the Status tab, select Component status.● Stop and start the Prepare for Undeploy component.

This enables case creation.

WRM-8684 Summary: In graphical audit, a time-stamp is not displayed for the tasks (displaysas "pending") of process instance resumed after product upgrade.

Workaround: Run the SOAP request below against the Event Collector ManagementService.<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:api="http://api.ec.n2.tibco.com"> <soapenv:Header/> <soapenv:Body> <api:executeActionRequest> <action> <actionName>recoverProcessHierarchy</actionName> </action> <options> <advancedOption> <optionName>recoverAll</optionName> <optionValue>false</optionValue> </advancedOption> </options> </api:executeActionRequest> </soapenv:Body></soapenv:Envelope>

WRM-8468 Summary: Audit/graphical audit for processes which have not had their auditmigrated after upgrade to TIBCO ActiveMatrix BPM 4.0 will be incomplete and theGraphical Audit Trail may not be visible.

Workaround: Run the migration tool, then view the Graphical Audit Trail , and itshould work correctly.

WRM-8168 Summary: When a process user application references a Business Data userapplication, if there is a qualifier missing from the project version, then you mayreceive errors when opening forms.

Workaround: Make sure that a qualifier is part of the project version.

66


Key Information

WRM-8158 Summary: When you upgrade from TIBCO ActiveMatrix BPM 3.1.0 to 4.0.0, in theec_event_rules.xml file the commented section 'default_archive channel' andExcludeID rules are missing in the upgraded setup

Workaround: Manually edit the file to add them.

● Keep a backup of the ec_event_rules.xml file of previous TIBCO ActiveMatrixBPM 3.1.0 version before upgrading to TIBCO ActiveMatrix BPM 4.0.0 and thencopy the missing commented tag on the upgraded ec_event_rules.xml filefrom the backup file.

● Copy the missing channel default_archive below in ec_event_rules.xml

WRM-7593 Summary: If process data is mapped to attributes 15, 38, 39 and 40 you might see thedata also assigned to iteration, iteration ID, Host task name, and Host task typerespectively.

Workaround: Avoid using attributes 15, 38, 39 and 40 when mapping data fields.

WRM-7577 Summary: When you install TIBCO ActiveMatrix BPM, it will not work if you havespaces in TIBCO_CONFIG_HOME.

Workaround: Avoid having any spaces in TIBCO_CONFIG_HOME.

WRM-7549 Summary: Error while performing SiteMinder SSO authentication in Openspace/Workspace when the IP address is populated in resource template.

Workaround: Remove the client IP address from the runtime.

WRM-7512 Summary: TIBCO JasperReports Server for ActiveMatrix BPM: (For all claims)Clicking on a claim whose instance is completed, in the claim exposure value "-" isshown.

Workaround: None.

WRM-7509 Summary: TIBCO JasperReports Server for ActiveMatrix BPM: Internet Explorerspecific (Internet Explorer 9, 10 and 11) : Intermittent error where sometimes allreport contents are not loaded on the first attempt.

Workaround: Reload the report.

WRM-7508 Summary: TIBCO JasperReports Server for ActiveMatrix BPM : When you suspendprocess instances and resume, work items of such processes are not displayed in theOffered Work report.

Workaround: None.

WRM-7507 Summary: TIBCO JasperReports Server for ActiveMatrix BPM: Work items ofcancelled and suspended process instances should not be displayed in theOutstanding tasks report.

Workaround: None.

67


Key Information

WRM-7484 Summary: TIBCO JasperReports Server for ActiveMatrix BPM: Not able to formatand apply filters on Top 5 claims reports.

Workaround: None.

WRM-7481 Summary: If a BOM contains a type hierarchy, for example a class 'Drink' and sub-classes 'Coffee' and 'Tea', then problems can arise when manipulating instances ofsuch Business Objects via a User Task meaning that you may lose some sub-classdata. If a class 'Person' has an attribute/composition of type 'Drink' then, although aForm may appear to allow Coffee and Teas to be assigned, the resulting BusinessObject will always record these as the base type, Drink.

Workaround: None.

WRM-7437 Summary: TIBCO JasperReports Server for ActiveMatrix BPM: On loading ClaimBreakdown dashboard for first time if you click on the clear filter, 'All' claims aredisplayed though selected option is 'open' claim.

Workaround: Click on Open and then Closed again.

WRM-7333 Summary: TIBCO JasperReports Server for ActiveMatrix BPM: Column filtersshould not reset on refresh gadget or user login/logout.

Workaround: None.

WRM-7281 Summary: Case Data: When you delete a Case and the referring form has the sameCase marked as Mandatory, you receive an error and the case is not deleted.

Workaround: To remove the case you must cancel the process instance.

WRM-7268 Summary: TIBCO JasperReports Server for ActiveMatrix BPM: Jaspersoftdashboards do not work on Internet Explorer 8.

Workaround: Use an alternative browser.

WRM-7195 Summary: Calling the setMigrationRules REST method with a json body results inan error.

Workaround: Use XML payload as request/response.

68


Key Information

WRM-6964 Summary: If you enter a valid JSON string in a text field on a form, either an errormessage is displayed or the string is not stored in the ActiveMatrix BPM databaseexactly as you entered it. For example, if you enter:

{"name":"joe"}

ActiveMatrix BPM interprets the string as a JSON string, and tries to process itaccordingly. This is because ActiveMatrix BPM uses JSON internally to handle formdata.

Workaround: To store in the database a JSON string that you have entered in a textfield, escape the double quotation marks using the backslash character. For example,to store the above string, enter:

{\"name\":\"joe\"}

Consequently, when the string is retrieved from the database, the escape charactersmust be removed, using http://org.apache.commons.lang3.StringEscapeUtils, forexample.

WRM-6802 Summary: Event Collector Purge: Cursor_refresh (the number of process instancesthat should be deleted before the cursor is refreshed) is still considered as amandatory parameter even though it is deprecated.

Because the parameter is in the middle of the list of parameters and not at the end,providing no value for it causes a problem.

For example : EXEC amxbpm.ec_delete_audit_stats_data NULL, '08-OCT-1013:35:37', NULL, 'TRUE' would return an error as it tries to assign 'TRUE' tocursor_refresh which is a BIGINT.

Workaround: Provide a value for the Cursor_refresh parameter. For example,change the above command to EXEC amxbpm.ec_delete_audit_stats_dataNULL, '08-OCT-10 13:35:37', NULL, '10', 'TRUE'

WRM-6801 Summary: Warnings occur while creating indexes for Event Collector purge onMicrosoft SQL server.

Workaround: These indexes should be dropped immediately after finishing thepurge to avoid any future issues.

WRM-6791 Summary: TIBCO ActiveMatrix BPM Business Data Services Developer Guide:screenshots of TIBCO Business Studio's Properties tab are out of date.

Workaround: None.

WRM-6780 Summary: Updates to Global Data database scripts made via the Openspace DataAdmin gadget or web service API will not be audited.

Workaround: Edit the ec-probe-rules.xml configuration file, replacing'BDS_GLOBAL_DATA_ADMIN_SQL_SCRIPT_AUDIT' with'BDS_GLOBAL_DATA_ADMIN_SQL_SCRIPT'. Make this change if you want to seethis message propogated to the ec_event table

69


http://org.apache.commons.lang3.StringEscapeUtils

Key Information

WRM-6756 Summary: Search conditions based on certain attributes, whether specified in a DataView or DQL expression, can result in SQL errors at run-time.

Specifically, this can occur when (1) The attribute is multiplicity-many and on aglobal class, not the case class. and (2) The global object containing the attribute is inan attribute path that contains an [ALL] or [<index>] suffix in an earlier fragment ofthe path.

For example, consider searching for Clubs in the following BOM:

DQL expression: members[ALL].favouriteColours = 'Red'

Meaning: Find Clubs where all members have Red as one of their favorite colors.

DQL expression: members[0].favouriteColours = 'Blue'

Meaning: Find Clubs where the first member has Blue as one of their favorite colors.

Both of the expressions above can exhibit the problem.

To be clear, the problem occurs only when [ALL] or [<index>] are used, asdescribed above. The following DQL expression does not suffer from the problem:

DQL expression: members.favouriteColours = 'Red'

Meaning: Find Clubs where any member has Red of one of their favorite colors.

Workaround: Altering the BOM to eliminate the multiplicity-many attribute avoidsthe problem. In the following modified BOM, a Person contains many Colours, eachof which has a text attribute containing the name of the colour:

The original DQL queries would then be rewritten as follows:

DQL expression: members[ALL].favouriteColours.colour = 'Red'

Meaning: Find Clubs where all members have Red as one of their favorite colors.

DQL expression: members[0].favouriteColours.colour = 'Blue'

Meaning: Find Clubs where the first member has Blue as one of their favouritecolours.

In terms of the generated database tables, this is of equivalent complexity to theoriginal BOM, and may even be considered better practice.

70


Key Information

WRM-5878 Summary: If the Close/Submit fails because the update on the case reference hasfailed because the case reference is stale, errors are recorded in the BPM log, and thework item is stuck in Opened state.

Workaround: Cancel the work item, then re-open it (this causes it to re-read the casereference, thus getting the up-to-date version). Then the Close/Submit should work.

If the update fails because the case reference no longer exists, there is noworkaround.

WRM-5686 Summary: BPM Cleanup utility fails to generate scripts on AIX.

Workaround:

1. Download XmlTask source from http://www.oopsconsultancy.com/software/xmltask/.

2. Extract the downloaded tar file and edit the com/oopsconsultancy/xmltask/jdk15/XPathAnalyser15.java file, replacing:

import com.sun.org.apache.xpath.internal.objects.*;

import com.sun.org.apache.xpath.internal.*;

with

import org.apache.xpath.objects.*;

import org.apache.xpath.*;

3. Download the junit.jar (required by the build), place it in the XmlTask sourcefolder and then update CLASSPATH to refer to it: export CLASSPATH=./junit.jar

4. Run ant to compile the source, and ant package to create the xmltask.jar file.

5. Copy the xmltask.jar file to the /opt/apache-ant-1.7.1/lib folder.

WRM-4698 Summary: It is not possible to connect to a CMIS repository accessed via SSL byusing the CMIS sample.

Workaround: None.

WRM-4186 Summary: If an enumeration in a BOM is a restriction of another enumeration, it isshown in TIBCO Business Studio as if one is a generalization of the other. However,they are two separate enumerations, with no inheritance from each other in theunderlying code. Therefore, an interface that expects the base type to be passed to itcannot be passed the restricted type, and there will be a run-time failure.

Workaround: If this XSD construct is used in a web service that ActiveMatrix BPMneeds to interact with, use a Mediation between BPM and the external web service.

71


Key Information

WRM-2604 Summary: Service Connector uses third-party Apache Axis2 and Apache Rampartlibraries. This may increase the Java CLASSPATH length.

Workaround: To avoid CLASSPATH length issues, use the new feature provided inJava 1.6 to include all binaries by using the wildcard character(*).

1. Unzip the service connector to a folder, for example c:\service-connector.

2. Set the CLASSPATH to the c:\service-connector folder using the wildcardcharacter, for example:

SET CLASSPATH=%CLASSPATH%;c:\service-connector\*

WRM-1671 Summary: In TIBCO Workspace Event Views, the Push-related columns for thePUSH events do not display any information.

Workaround: None.

WRM-1539 Summary: If a measure is requested for a particular process, the returned data is acumulative roll-up of the data for the process. However, the statistics collector doesnot return any roll-up data for hours in which there is no activity in the process.

Workaround: If data for any hour is missing, assume that it is the same as that forthe previous hour.

WRM-521 Summary: If a pageflow process has no user tasks, this causes an exception when itis called from a client application, for example from either Openspace or Workspace.

Workaround: Add page activities to the pageflow process.

WRM-440 Summary: Uninstallation of TIBCO ActiveMatrix BPM fails to stop the processesBPMNode, AdministratorNode and TibcoHost before removing files.

Workaround: Stop the processes manually or restart the system.

WRM-69 Summary:The Email presentation channel does not support SMTP authentication.

Workaround: None.

Process Manager

Key Information

BX-3814 Summary: Mapping of 'Unprocessed Text' type REST Service response to Text datafield does not preserve the value in the data field after REST service task hascompleted.

Workaround: In the complete task of the same script you can copy the mapped textdata field to another data field. The value will be preserved in this second datafield.

72


Key Information

BX-3813 Summary: Renaming or deleting a global signal event handler in a new version of abusiness process may cause the global signal definition project to fail to upgrade orundeploy.

Workaround: Execute the following database query before attempting an upgradeor undeploy of a global signal definition application: delete fromPVM_EXT_SIGNAL_WAITING_REC where PROCESS_ID not in (select ID from

PVM_INST_PROCESS);

BX-3812 Summary: Global Signal correlation fails if the correlation field has been reset in anactivity within an event sub-process, and that activity is set as an initializer on thesignal start activity within the Event Sub-process.

Workaround: Use the setting on the sub-process to "Allow Concurrent Flows".

BX-3811 Summary: Correlation of global signals fails if the correlation field is of typedecimal or dateTime.

Workaround: Put the decimal or dateTime values in a string and use that incorrelation.

BX-3756 Summary: In a Global Signal audit, a persistent signal is not purged after its staletimeout has expired, but more that 10 minutes later.

Workaround: None.

BX-3743 Summary: Retrying a reusable sub-process shows the Graphical Audit Trailincorrectly.

Workaround: None.

BX-3678 Summary: Undeploy not working on an upgraded Global Signal Definitionapplication (for example, version 2) which is referenced by a user application (forexample, version 1).

Workaround: Force undeploy the Global Signal Definition.

BX-3634 Summary: Do not reset scope attributes on retry if they were set before entering thescope.

Workaround: None.

BX-3591 Summary: Could not synchronize database state with session on invoking messagestart event in a service process.

Workaround: None.

BX-3474 Summary: Sub-process with Start Immediately option inherits parent processpriority rather than starting the sub-process with priority Normal [200].

Workaround: None.

73


Key Information

BX-3425 Summary: TIBCO Business Studio workspace sometimes throws an error "Aninternal error occurred during: "Compute launch button tooltip"".

Workaround: None.

BX-3346 Summary: No support for mapping BDS data from a sub-process error event.

Workaround: Use a script task to break down the error data into multiple primitivefields and associate these with the sub-process throw error event. .

BX-3214 Summary: amx.bpm.app redeployment after removing a node from theamx.bpm.app distribution halts process instance creation/execution.

Workaround: Restart all Nodes in the setup.

BX-2967 Summary: When you have two versions of an application - V1 and V2 with V2having event handlers and added mandatory parameters, process instances thatmigrate from V1 to V2 might go into 'Halted' state with an error - 'No value set formandatory IN/INOUT parameter'.

Workaround:

● The parameters added in V2 should be non-mandatory.● The parameters added in V2 can be mandatory but at the interface of the tasks

where the process instance migrates, the parameters should be made INOUT -non-mandatory.

BX-2956 Summary: Mapping between incompatible types like BPM attribute to POJO listcould result in ExpressionEvaluationError.

Workaround: Add a script task before the java service task to build the source dataas an array of Java objects out of the BDS list, before mapping it to the POJOmethod parameter.

BX-2507 Summary: Data in the database and server's response can not display correctcharacters outside the character set supported by the default system encoding. Thiscould cause the extended message to be displayed incorrectly.

Workaround: None.

PVM-550 Summary: Maximum key length warnings appear when runningProcessManagerCreate.sql for SQL Server 2012.

Workaround: None.

74


ClientsThis topic lists the known issues for Forms, Openspace and Workspace clients in TIBCO ActiveMatrixBPM 4.0.0.

TIBCO FormsThis topic lists the TIBCO Forms known issues in TIBCO ActiveMatrix BPM 4.0.0.

Runtime

Key Information

FORM-6819 Summary: If you have configured ActiveMatrix BPM as a distributed system toprovide high availability and fault tolerance, then sometimes opening a work itemon one of the nodes fails with an "Error loading the Form model - 404: Resource notfound:SetPRDIDAndReleaseID.gwt.json" error.

Workaround: After a period of time, the issue resolves itself and you can open thework item.

FORM-6810 Summary: If there are multiple projects with the same version number, then someuser tasks, for example, forms or pageflows, fail to open with a Resource NotFound error.

Workaround: Change the version number of such projects in TIBCO BusinessStudio and redeploy or upgrade them.

FORM-6717 Summary: On Internet Explorer 9, when focusing on a grid pane button or columnname, the height of the root pane or the grid pane increases.

Workaround: Set the CSS as .TibcoForms.tf-uir-enabled.ua-ie9 .pane-grid{ height:100%; } and .TibcoForms.tf-uir-enabled.ua-ie9 .pane_<parentpane name> .pane-content { height:50%; }.

FORM-6714 Summary: On Windows 7 or 8, forms may not load properly on the GWT Previewtab of TIBCO Business Studio, if Internet Explorer has been upgraded.

Workaround: Use an external browser to preview forms.

FORM-6705 Summary: After working on a form in Workspace, if you open the same form inInternet Explorer as a work item and see the data preview, going back to theSummary tab throws an exception in GWT Log.

Workaround: None. You can safely ignore the exception.

FORM-6466 Summary: Custom controls of complex type are not validated.

Workaround: None.

FORM-6460 Summary: A select event is triggered on value update in a grid pane even whenthere is no selection.

Workaround: In the action scripts, add null checks when the grid pane selectionAPI is used.

75


Key Information

FORM-6446 Summary: The API setFocus(Integer index, Integer item) does not work on controlsin a record pane.

Workaround: None

FORM-6110 Summary: When editing a list control in Openspace or Workspace, if you scroll thewindow using the scroll-wheel, the edit box in the list control remains on the page,and does not scroll with the window. It is also applicable to editing controls in agrid pane when not in Always Render mode.

Workaround: Pressing the Escape or Enter key closes the edit box.

FORM-5717 Summary: At runtime, only one version of a Component Library can be loadedwithin the same browser session.

Workaround: If later versions of a process need to use an updated version of alibrary, then that library should be renamed to avoid a conflict with the earlierversion of the library.

FORM-4164 Summary: A mobile form that contains a Duration list control is not properlydestroyed when the form is submitted.

Workaround: None. The only workaround is to avoid using Duration list controlsfor forms targeting the mobile presentation channel type.

FORM-4145 Summary: In mobile forms, the deletion of values from multi-valued list controls isnot working.

Workaround: None.

FORM-3544 Summary: Sometimes the loading of a mobile form is slow or can appear to freeze.This only happens during the initial load of the particular form and for subsequentinstances of the same form load.

Workaround: None.

FORM-2592 Summary: The setOptions() method on RadioGroups and OptionLists in GoogleWeb Toolkit (GWT) fails if an array of numbers is passed as the option valuesarray.

Workaround: Use an array of strings to set the option values for an OptionList orRadioGroup control.

76


Key Information

FORM-2376 Summary: Specific to Google Web Toolkit (GWT) presentation of forms. For imagecontrols, the settings of width and height do not have any effect on the renderedimage.

Workaround: The size of images can be set using CSS. Follow these steps:

1. Create a CSS file in the Presentation Resources folder that contains a CSS rulefor setting the size of an image control, for example: .TibcoForms .imageSizeimg {width: 100px; height: 100px;}

2. Add the CSS file as a reference in the Form Resource property sheet.

3. Add imageSize as the Style Class Name for the image control. (You can usewhatever CSS class name you want as long as it matches what is used in theCSS file.)

Openspace

Key Information

OS-3421 Summary: In the Process Views gadget, if you start a process instance, all thedetails of the process instance, for example, priority, start times and so on, are notdisplayed immediately.

Workaround: Refresh the gadget to display the details about the process instance.

OS-3249 Summary: The Reporting gadget is used to view measures like the total number ofprocess instances and work items by their current status. You can also view theaverage duration of a process instance or work item. The Reporting gadget usedthe events generated by ActiveMatrix BPM to gather this information. However,due to changes in functionality, the Reporting gadget no longer works.

Workaround: Refer to "Configuring TIBCO ActiveMatrix BPM Auditing" in theTIBCO ActiveMatrix BPM Administration Guide for information on how to auditevents in ActiveMatrix BPM.

OS-3187 Summary: (Only applies to Internet Explorer Version 8) You cannot add a search toFavorites in the Case Management gadget.

Workaround: Use another browser such as Chrome or Mozilla Firefox.

OS-3097 Summary: In the Organization Browser, a problem can occur when using the ClearSelections checkbox in the Map to Positions tab to map resources to positions.Sometimes, selecting the Clear Selections icon leaves check marks besides positionseven though the Grant button is grayed out.

Workaround: Use the Space or Enter key to make selections.

77


Key Information

OS-2962 Summary: If you are creating a work view in the accessible variant of Openspaceand you select a work item attribute as part of your sort criteria, the name of theattribute does not display. The work item attributes display as attribute1, attribute2and so on.

Workaround: None.

OS-2779 Summary: (Only applies to Internet Explorer version 8 and Mozilla Firefox) In theChoose Columns drop-down list in the Work Views gadget, the DistributionStrategy name and icon overlap.

Workaround: Use another browser such as Chrome.

OS-2777 Summary: If you configure any groups for the work items in your work item list,they are lost when you open a work item belonging to the group.

Workaround: None.

OS-2630 Summary: If you have configured ActiveMatrix BPM to use Kerberos, and whileusing Openspace, your Kerberos session ticket becomes invalid, you can stillcontinue to use your current Openspace session. In other words, your Openspacesession is not invalidated if your Kerberos session ticket becomes invalid.

Workaround: Log out of your current Openspace session and then log back intoOpenspace.

OS-2518 Summary: When using Internet Explorer Version 9 with Openspace, delays areexperienced when opening work items with forms.

Workaround: Use a later (supported) Internet Explorer version - check the TIBCOActiveMatrix BPM Installation Guide for supported versions OR use anothersupported browser version as listed in the installation guide or readme.

OS-2438 Summary: In the Organization Browser, if you select some resources and thenchange the organization model version, the resources are deselected and you haveto select them again.

Workaround: None.

OS-2326 Summary: You cannot delete extension points using Openspace.

Workaround: You must delete extension points using the TIBCO ActiveMatrixBPM API.

OS-2140 Summary: You cannot contribute the sample Work View gadget supplied TIBCOActiveMatrix if your environment is enabled for SSL.

Workaround: The sample gadgets URL has to use HTTP and not HTTPS.

OS-1914 Summary: When you first open the Calendar gadget and click Edit next toSYSTEM, the Working Days and Exclusion tabs do not display.

Workaround: Click Back then click Edit again and the tabs display.

78


Workspace

Key Information

WS-1610 Summary: If long names are used when specifying items in Workspace (forexample, views), or the Organization Browser (for example, LDAP containers), thenames can overlap on the display, causing them to become unreadable. You mayalso experience a "DE_ENTITY_SAVE_ERROR " when attempting to save itemswith long names.

Workaround: When naming items in Workspace or the Organization Browser,limit the length to 80 characters.

WS-1524 Summary: When Workspace is using a Microsoft SQL Server database, if youcreate a process view using the Include selected processes option and thenindividually select hundreds of process templates, a SQLServerException may bethrown that states Some part of your SQL statement is nested too deeply.

Workaround: None

WS-672 Summary: Pageflow definitions can include branching that would require thesimultaneous handling of multiple user tasks, each requiring the display of a form(this same scenario could also occur in embedded sub-processes set up for chainedexecution).

Workspace cannot currently display multiple forms resulting from these parallelpageflows. If one is encountered in a WCC application (including the defaultWorkspace application), the following warning message is displayed: "Thebusiness service or work item has encountered a parallel pageflow which cannot bedisplayed in Workspace".

Workaround: Rework the process/pageflow to eliminate the parallel display ofmultiple forms, or create a custom BPM application using the available APIs thatcan handle pageflow branching (for information, see the TIBCO ActiveMatrix BPMDeveloper’s Guide).

79


Date post:	31-Dec-2016
Category:	Documents
Upload:	nguyennga
View:	248 times
Download:	8 times