iPlanetTM Process Manager

Version 6.0 Service Pack 1

Release Notes

Updated November 30, 2000

Contents

What's New

System Requirements

Process Manager 6.0 Service Pack 1 runs on the following platforms:

Database Support

Installation

Issues and Limitations

Resolved Issues

The following issues, listed by category, have been resolved in the iPlanet Process Manager Version 6.0 Service Pack 1 release.

Resolved Installation Issues

ID Summary
399257 Process Manager installer no longer turns off the JIT compiler. Now the JIT compiler is on by default.

Resolved Process Administrator Issues

ID Summary
408581 After the user accepts a work item, the dynamic group that was created for the work item list query is not deleted. This has the effect that once a work item is accepted by a user, the other users from the assignment script results are still shown work items in their worklist; even though another user has accepted the work item.
406181 Groups with more than 1,000 entries no longer results in an application error. The default search behavior is now overwritten; there is no limit to the number of entries.
515287 A CORP_DIR_ACCESS_FAILED exception when dynamic groups are used in the assignment scripts. For example, if a node has a custom exception manager associated with it, the assignment script of this execption manager decides which user the resultant exception work item is assigned to. This functions properly for user assignments such as new Array("admin", "raghavan"), but fails when the exception node has been assigned using toGroup("some_dynamic_group").
518496 When using Oracle as the database, populating a large amount of text into a TextArea box with the Data Type set to "Long Text" no longer results in an error.

Resolved Process Builder Issues

ID Summary
450809 The error message "Unable to initialize AppDesignerView module (array index out of bounds)" is no longer encountered on launch if the user is running Process Builder using the Java Developer's Kit 1.2.2 and is using Process Manager Version 6.0 Service Pack 1.
518259 The browser client-side event handler code is not generated properly. If the data dictionary elements contain client-side event handler code, this code is not transfered to the browser properly. All the semicolons in the code are replaced by commas causing an error on the browser side.

Resolved Process Express Issues

ID Summary
408561 The event OnStartWorkItem does not setParticipant() in the Process Instance. The result is that when a custom field display() method is called, the process instance object is incomplete as IParticipant is not set.

Resolved API Issues

ID Summary
394401 The getPriority() method used to give a default value of 3 instead of the user specified default. This problem has been resolved in this release.
397666 WorkItem.addUserAssignee(String) throws ambiguous Rhino method Exception. The following code in a Javascript function results in the above exception:
var pi = getProcessInstance ();
var wi = getWorkItem ();
wi.addUserAssignee("SMatsuzuka");
519585 Calling the setData() method on a UserPicker widget no longer reports an error or fails on the next transition with an error.

Known Issues

The following issues, listed by category, have been addressed in this release and a workaround is provided.

Known Installation Issues

ID Summary
515611 Problems encountered when changing LDAP that the Process Manager authenticates against.
Workaround: Do not change the LDAPBackend1 entry; this is required for the Application Server configuration entries. However, if you need to change the LDAP you can:
  1. Create a clone of the entire registry entry LDAPBackend1 from the \GDS\Backends\Ldap directory.
  2. Rename your cloned registry to any desired name such as LDAPBackend2.
  3. Change the properties (host et al) to point to the new LDAP server.
  4. Change the 6.0\PRINCIPAL\DBO key to point to your cloned registry LDAPBackend2.
  5. Bounce the web server and all engines.

The Process Manager, or actually the Application Server, should now begin to authenticate against the new LDAP server i.e. the one pointed to by your cloned registry entry LDAPBackend2.

Some precautions to consider: Any other iPlanet Application Server application deployed to the same instance that uses "container based authorization" will now look for the new new LDAP registry entry. Additionally, keep in mind that you are changing the security domain that the entire Application Server instance authenticates against, not just the security domain of the Process Manager.

Known Process Administrator Issues

ID Summary
393777 The toParallelApproval does not work in certain scenarios.
Workaround: Take the following code for the following scenarios: toParallelApproval(new Array("admin","admin1"),"comp1")
Scenerio 1: Admin starts the process and completes the process by accepting the work items.
Bug: Engine should check whether admin1 completed the work item before completing the process.
Scenario 2: Admin starts the process and admin2 accepts the work item and rejects it.
Bug: The work item is still showing up in the admin work item list even though it is rejected by admin1.
404161 Changing the corporate directory does not update the iPlanet Application Server registry. As a result, corporate directory remains the same even if it is successfully changed through the Administrator.
Workaround: The iPlanet Application Server must be defined to use the same corporate directory as the Process Manager. Changing the cluster definitions in the Process Manager does not update the Application Server principal database. Limited support is available for changing the corporate directory configuration of the iPlanet Application Server. Full support will be available in a future release.
514200 Information needed on how to set up Process Manager to work with an iPlanet Application Server cluster.
Workaround: See the directions for Setting Up Process Manager to Work with an iPlanet Application Server Cluster.

Known Process Builder Issues

ID Summary
512001 Process Manager does not ship with its own version of the JVM.
Workaround: Process Manager uses the JDK and the JVM from the iPlanet Application Server installation. by default, Process Builder must be installed in the same location as the Application Server for this to work. Builder relies on the JAVA_HOME environment variable to determine the JDK location. Make sure this variable points to a valid location before launching.
513615 The security ACLs on the EJBs such as the PMClusterManager, PMCluster, and the application EJBs have been removed.
Workaround: It is no longer necessary to use the security container for Servlets and EJBs that are registered to access the Process Manager API.

Known Process Express Issues

ID Summary
402317 Files with the extension .bat, .exe, and .dll do not upload.
Workaround: Set the file name to something other than these extensions.
519649 Business.apm does not list completeted PI's.
Workaround: This is a known issue and will be resolved in a future release.

Known API Issues

ID Summary
394558 The expire() method has been removed from the JavaScript API Reference.
Workaround: Use the extend(Date) method instead. The functionality is the same.
410588 The setTitle() method has been removed from the JavaScript API Reference.
Workaround: The setTitle() method does not have an alternative in JavaScript. It is only available from the Java API.
412968 The setPriority method has been removed from the JavaScript API Reference.
Workaround: The setPriority method is does not have an alternative in JavaScript. It is only available from the Java API.
451009 The addRoleAssignee() JavaScript method on workItem has been removed.
Workaround: Use the addGroupAssignee() method instead.
451469 The isUserAssignee() method on workItem has been added to the JavaScript API Reference.
451609 The getCurrentActivityCN() method has been removed from the JavaScript API.
Workaround: Use the wi.getNodeName() method instead.

Known Application Server Issues

ID Summary
394657 Problems with the Application Server KJS when you deploy a process that contains a subprocess.
Workaround: You must restart your application server after you deploy an application for the first time to a server that is under load.

Reporting Problems

Online and telephone Technical support can be found at: http://iplanet.com/support/online/

For More Information

For all iPlanet Process Manager documentation, including the Installation Guide, and updated release notes, refer to: http://docs.iplanet.com/docs/manuals/pae.html

Newsgroup

Process Manager now has its own newsgroup. Please post questions to: snews://secnews.netscape.com/netscape.server.processmanager

Copyright © 2000 Sun Microsystems, Inc.
Some preexisting portions copyright © 2000 Netscape Communications Corp. All rights reserved.