Fixes Defects:

PI17984,PI28856,PI31207,PI32437,PI34211,PI34244,PI35254,PI37311,PI38212,PI38279,PI38286,PI38291,PI38423,PI38939,PI39590,PI40268,PI40656,PM92870,PM99516



This patch contains the following software changes:


PI17984:

   Problem: ClearQuest can have slower performance when the HIDE_ACTIONS properties setting is enabled.

   Fix: ClearQuest performace has been improved when the HIDE_ACTIONS properties setting is enabled.


PI28856:

   Problem: When used in ClearQuest choice list hook, the Perl range operator does not always return the correct result.

   Fix: When used in ClearQuest choice list hook, the Perl range operator now returns the correct result.


PI31207:

   Problem: When a user already has a session open and clicks on an e-mailed hyperlink or bookmark, there is a spelling mistake on the German ClearQuest Web login page.

   Fix: The spelling mistake has been corrected on the German ClearQuest Web login after clicking on a hyperlink or bookmark.


PI32437:

   Problem: While attempting to duplicate one defect to another, if the user enters an invalid id, ClearQuest Web displays a confusing error message in a pop-up dialog that is hidden from the user.  It is only visible after the users closes the duplicate id window.

   Fix: While attempting to duplicate one defect to another, if the user enters an invalid id, ClearQuest Web now displays a clear useful error message that is visible to the end-user.


PI34211:

   Problem: When doing feature level upgrades, ClearQuest sometimes has inefficient data checking.

   Fix: ClearQuest now has more efficient data checking when doing feature level upgrades.


PI34244:

   Problem: The ClearQuest Web a Search by ID feature may throw an 'ORA-01722: invalid number' error message when searching for existing stateless record ids.

   Fix: When searching for existing stateless record ids, ClearQuest Web Search by ID no longer throws the mentioned error message.


PI35254:

   Problem: If the 'Run Again' option in the ClearQuest Web Multi-Record update 'Increase the Page Size' dialog is chosen, the number of updating records is limited to 20.  It is only increased to the maximum number if you open the result set sub-tab of the Multi-Record Update view before making the record change.

   Fix: ClearQuest Web Multi-Record update now adheres to the setting in the 'Increase the Page Size' option. It is no longer limited to a size of 20.


PI37311:

   Problem: Memory allocation that occurs in loading groups, users, and master links is inefficient.  This can lead to out of memory errors in the ClearQuest Designer and User Admin tool when there are a large number of data rows in the related database tables.

   Fix: ClearQuest's allocation of memory for loading groups, users, and master links has been made more efficient so that "out of memory" errors no longer occur.


PI38212:

   Problem: If a List View control is used for a Reference field, removing an item from the field fails when using ClearQuest Web.

   Fix: ClearQuest Web ListView controls were fixed to work correctly with reference fields.


PI38279:

   Problem: When using the ClearQuest Web OSLC load balancer feature, admin sessions may be created and not released, resulting in extra database connections.

   Fix: The ClearQuest Web OSLC load balancer no longer retrieves data by using admin sessions..


PI38286:

   Problem: The Cancel and Save/Close buttons on a ClearQuest Web OSLC creation dialog form no longer actually close the form, and clicking them causes a persistent spin icon.  Also, the window.name property is never updated in the case of the "Cancel" operation so it's difficult to figure out when the actual action is complete.

   Fix: ClearQuest Web has been updated so that the window.name property is properly updated upon cancel.  In addition, the dialog itself is automatically closed which removes that burden from the caller.


PI38291:

   Problem: When using the OSLC creationDialog API, users are instructed to issue an OSLC DELETE API call to release the associated http and ClearQuest sessions used when work is complete.  The DELETE call in many cases does not log off the ClearQuest session, despite clearing the http session.

   Fix: The OSLC DELETE call performed on the session will delete the associated ClearQuest session following API calls using the creationDialog.


PI38423:

   Problem: When a ClearQuest Web user right clicks on an record on a list view control, it does not open.

   Fix: When a ClearQuest Web user right clicks on an record on a list view control, it can now be opened.


PI38939:

   Problem: ClearQuest Web users are unable to create a project relationship between ClearQuest and Doors 9.6.1.0.

   Fix: ClearQuest Web users are now able to create a project relationship between ClearQuest and Doors 9.6.1.0.


PI39590:

   Problem: Some ClearQuest Web operations take a long time when fetching and caching ClearQuest metadata.

   Fix: Some ClearQuest Web operations were optimized to improve performance and stability in ClearQuest.


PI40268:

   Problem: When creating or modifying a stateless record, some custom validation messages from hooks are not being shown in the ClearQuest Web client.

   Fix: ClearQuest Web client was fixed to show custom validation messages from hooks.


PI40656:

   Problem: If the ClearQuest/ClearCase V2 integration is configured to work via the ClearQuest Change Management (CM) Server, it fails to return a query result set for selecting associations for the integration step.

   Fix: If the ClearQuest/ClearCase V2 integration is configured to work via the ClearQuest Change Management (CM) Server, it now returns a query result set for selecting associations for the integration step.


PM92870:

   Problem: When running the ClearQuest Web Site Administration Monitoring tool, the login dialog box has text labels missing.  The "Ok" and "Cancel" buttons are also smaller than expected.

   Fix: The ClearQuest Web Site Administration Monitoring login dialog has been fixed. The labels and buttons are restored back to normal.


PM99516:

   Problem: When a ClearQuest LDAP user tries to run an OSLC query, the authentication fails if there is any group set as Restricted on the CQ Web server to which the OSLC queries are directed.

   Fix: When a ClearQuest LDAP user tries to run an OSLC query, the authentication succeeds when there is a group set as Restricted on the CQ Web server.