Plumtree Process 1.5 HF231199 - released August 2006

Plumtree Process 1.5 - released January 2006

These release notes cover the v1.5 release of Plumtree Process.

Release notes are occasionally updated after the release date. For the most up-to-date release notes, go to the Product Center.

It is recommended that this hotfix be applied to ALL installations of Plumtree Process 1.5.

• A process cannot be instantiated from an external JSP portlet. (Issue #52646)
• Execution of a process activity when the activity is an external method results in an ALBPM error. (Issue #51242)
• When using MS SQL Server for the directory service, synchronization issues may occur under rare conditions. (Issue #53092)
• Images do not appear in Fuego Object Presentations or BAM dashboards. (Issue #53620, Support Request #1-3747691557)
• Global applications with instance access are displayed in the Applications portlet instead of the Work Item Details portlet. (Issue #53601, Support Request #1-3700498933)
• A NullPointerException is thrown when starting the failover engine. (Issue #53575)
• Collaboration attachments do not work in processes with split-join activities. (Issue #53702)
• The FuegoWarehouse service does not populate the BAM database. (Issue #53766, Support Request #1-3784589492)

Refer to the Interoperability page in the Product Center for the latest information on supported operating systems, databases, and browsers.

At the time of release, Plumtree Process 1.5 supports the following:

• Operating Systems:
  • Process Execution Engine and Admin Center (Utility): Windows 2003 SP1, Linux Red Hat 3 Update 4 ES & AS (on x86), SUSE Enterprise Linux 9 (on x86)
  • Process Designer: Windows 2003 Standard Edition SP2, Windows XP, Linux Red Hat 3 Update 4 ES & AS (on x86), SUSE Enterprise Linux 9 (on x86)
• Database Servers: SQL Server 2000 SP3a through the use of the SQL Server Data Direct Plumtree JDBC Drivers, Oracle 9i (9.2.0.4 and 9.2.0.6) and 10g (10.1.0.3) in default configuration or in Oracle RAC configuration through the use of Oracle Data Direct Plumtree JDBC Drivers
• Browsers: IE 6.0 (administrative use), Netscape 7.2, Firefox 1.0, Safari 1.3
• Java Virtual Machines
  • JRE: Plumtree Process ships with JRE 1.4.2 for Windows and Linux versions. Installers for other operating systems require a 1.4.2 JVM (JRE + tools.jar or JDK) with the latest patches applied.
• Application Servers: N/A. 

Refer to the Interoperability page in the Product Center for the latest information on supported Plumtree products.

At the time of release, Plumtree Process 1.5 supports the following:

• Plumtree Foundation 6.0, Plumtree Corporate Portal 5.0.4 with HF 210172, and Plumtree Corporate Portal 5.0.4J with HF 209071
• Plumtree Collaboration 4.0.2 and higher
• Plumtree Enterprise Development Kit (EDK) 5.3 and higher
  

The product distribution includes the following documents in the Documentation folder.

• General
  • In a UNIX/Linux production environment $PT_HOME/ptprocess/1.5/bin/startwebconsole.sh and $PT_HOME/ptprocess/1.5/bin/stopwebconsole.sh should be used to start/stop the Host Process Execution Engine as an alternative to using the Admin Center. (Issue #49372)
  • Plumtree Process 1.5 ships with a valid integrated product key and any reference to "Enter License Key" should be ignored. (Issue # 50704)

• General
  • The Thread Dump button on the Engines tab throws "java.lang.RuntimeException: Broken pipe" exception (Solaris 8/9). (Issue #48229)
    
    Workaround: Change the first line in the pid.sh in the $PT_HOME/ptprocess/1.5/bin/pid.sh $PT_HOME/ptprocess/1.5/libraries/admcenter/pid.sh directories to #!bin/sh. Change the /bin/sh to /bin/bash shell or point it to where the bash shell is displayed on the Solaris box.
  • The process execution engine caches all users in the Plumtree Foundation "Process Administrators" group on startup. If another user is added to Plumtree Foundation with these permissions after startup, the user is not picked up by the engine and they will not be able to monitor or control the engine or deploy a project to the engine. (Issues #49317 and #50416)
    
    Workaround: Restart the process execution engine and all new users in the "Process Administrators" group will be able to control and monitor the engine.
  • After undeployment of a project, the deployment status displays "Waiting for undeployment." (Issue #49993)
    
    Workaround: Reload Plumtree Process Administrator. Note that projects can only be undeployed while the engine is running.
  • The Holiday Rules calendar does not follow the user's locale settings. (Issue #50056)
  • A 404 error is returned when trying to import a project using the "Republish a previous version" option with a project that has never been published. (Issue #50247)
  • If the Role Name and Role Description together exceed 254 characters, the process execution engine throws an "inserted value too large for column" error in the log. No user interface error is provided. (Issue #50333)
    
    Workaround: Role Name plus Role Description must be less than 254 characters.
  • Filtering on Participants using the Description column as a condition does not return any results. (Issue #50419)
  • If the Process Log Viewer is launched from Process Administrator, its associated help does not work. (Issue #50702)
  • Error handling is not implemented if trying to access Process Administrator when the Portal Identity Service is not running. A stack trace is displayed instead of a useful error message. (Issue # 49001)
  • If the "Database String" option of Edit Business End Points | Engine Database Configuration is used, the Plumtree Portal Identity Service may display an exception "ERROR Error in sourcePoll()" in the logs. This can be safely ignored. (Issue #50506)
    
• Portal Identity Web Service, Integration
  • When a user is deleted from Plumtree Foundation, the participant becomes disabled in Process Administrator. If you add a new user with the same name to Plumtree Foundation, Process Administrator displays one disabled and one enabled participant, both with the same name. (Issue #49565)
  • The Portal Identity Service occasionally throws an exception, but the exception is handled without causing any issues for end users. The exception is caused by an FDI plug-in invocation with an illegal number of arguments. (Issue #50165)
  • When an Identity Service, previously referred to as an Authentication Web Service (AWS), changes group-in-group memberships, these changes are not reflected in the Plumtree Portal Identity Service. As a result, Process Administrator will not reflect these changes. (Issue #50595)

• User and Group Maintenance
  • Filtering on the userid of the display name does not work if the participant name contains a "\" character. (Issue #47850)

• General
  • Using Firefox, the views in a mypage/community, including the Worklist Portlets, may not fit on a user's screen.(Issue #48940)
    
    Workaround: Turn off scrolling within Firefox.
  • In 508 mode, the Worklist Portlets do not use edited Worklist Portlets preferences settings until you refresh the portlet or log out and log back in. (Issue #50344)
  • Intermittent: "[Portlet Name] cannot be displayed due to an unknown error" error is returned when accessing Worklist Portlets for the first time after the host process execution engine is started. (Issue #50106)
    
    Workaround: Reload Worklist Portlets.
• Worklist Navigation
  • Worklist navigation scrolling is turned off for FireFox so that the portlet fits to the number of views. (Issue #48746)
• Applications Portlet
  • On creation of a process instance for a global/non-interactive creation activity, an empty window flashes briefly. (Issue #49379)
  • Intermittent: The application launcher holds on to previous version of a process. (Issue #49641)
    
    Workaround: Restart the process execution engine.
  • "The page cannot be displayed" error is returned when launching an application in a new window after switching the display mode from Standard Portal to 508 mode without logging out. (Issue #50326)
    
    Workaround: In order for the display mode settings to take effect, log out and log back in.
• Worklist Items Portlet
  • Search | Filter Options allows condition "Participant Is" without a value. (Issue #49350)
  • Intermittent: Execution Dispatcher locks an instance when a new window is opened to execute a process. Closing the page does not seem to release the instance, the underlying page does not know to refresh, and selecting this process throws the following error: "The batch operation could not be executed for all selected instances." (Issue #50159)
    
    Workaround: Click the Refresh button on the portlet and then try again.
  • Scrolling on DatePicker months does not work in Firefox. (Issue #50514)
• Work Item Details
  • Cannot sort Notes by Description when the description contains accented characters. (Issue #50151)
  • E-mail notification: "The instance can be reached here" link will be broken if the "Everyone" group is added to the Work Item Details portlet security settings. If the "Everyone" group is added, then the user will not be forced to log in. (Issue #50160)
    
    Workaround: The "Everyone" group should not be added to the Work Item Details portlet security settings.
  • When strings are localized, the audit trail window may show mixed languages in the execution state column. (Issue #50668)
  • View item details from e-mail notification link preserves view state when going back to Worklist community portlets and selecting one of the Worklist Items views. (Issue #50834)
    
    Workaround: Go back to Worklist portlets (Process community) and select a view.
  • Item Details view page opened from e-mail notification does not refresh status after execution. (Issue #50836)
    
    Workaround: Leave the page and close the browser or go back to the portal community page.
• Attachments
  • Documents deleted from Plumtree Collaboration remain in the list of attachments. (Issue #50212)
  • In Firefox, files with names that consist of non-ASCII characters will download with a corrupted file name in Firefox. The file itself will not be corrupted. (Issue #50470)

• General
  • Prior to installing Process 1.5, determine if you have any of the following products installed on the same machine where Process 1.5 will be installed. If so, you must delete the file xalan.jar from the directory $PT_HOME\uninstall\ant162\lib before installation:
  • LDAP IDS 2.1
  • Windows CS 6.0
  • Studio 2.1

• Process Execution Engine
  • The Plumtree Portal Identity Service must be running in order to create a directory service. If the Plumtree Portal Identity Service is not running, the directory service will be created and not returned. (Issue #49220)
  • Re-installing Process Execution Engine 1.5 on top of an existing Process Execution Engine 1.5 installation fails with "Could not find the main class. Program will exit." error. (Issue # 50703 )

• General
  • Attempting to add a participant when the user exists in the database but is not displayed in the Participants list in Process Designer throws an error. (Issue #48669)

• General
  • Consultation e-mail messages cannot be localized - they are English only. New Instance notification e-mails can be localized by modifying the email template activityNotification.mail and putting the modified copy into the home directory of the process execution engine. (Issue # 50821)
  • The supported encodings/codepages for process names and descriptions, activity names and descriptions, as well as documentation added in Process Designer are Windows 1252/CP 1252 and ISO-8859-1. Role names and descriptions should only use characters covered by ISO-8859-1. (Issue # 50820)
  • The directory database uses the data types char/varchar and text to store text data as opposed to the Unicode data types used by other Plumtree products. Please refer to your RDBMS documentation for implications of "native" data storage.
  • Process 1.5 has improved localization support. The portlets are localized into French, German, and Italian. All administration components (Process Administrator and the Admin Center) are in English.