Fixes Defects:

PM15837,PM44971,PM51777,PM51842,PM53058,PM59316,PM60531,PM64420,PM71739,PM77116,PM77814,PM79532,PM80631,PM80778,PM81433,PM83701,PM86523,PM86720,PM87949,PM88253,PM89327



This patch contains the following software changes:


PM15837:

   Problem: When browsing ClearQuest records from within CCRC on a Korean locale, CQ UCM field labels have a slighter larger font size.  This sometimes leads to truncation of some label names.

   Fix: On Korean locales, ClearQuest field labels now have uniform font sizes when viewed from within CCRC.


PM44971:

   Problem: There is a Replace Value option in the ClearQuest Eclipse Client (RCP) Import Tool. This technote explains in more detail.
http://www-01.ibm.com/support/docview.wss?uid=swg21121020
However, the value "" (double quote double quote) does not clear reference_list fields even when the Replace value option is selected.

   Fix: Users can now use "BLANK" to clear out reference_list fields when the Replace value option is selected on the ClearQuest Eclipse Client (RCP) Import tool. Technote 1121020 has been updated with this new information.


PM51777:

   Problem: The ClearQuest Multisite syncreplica command fails on an English OS if the export packet file name contains non-ascii characters. It will fail with a "cannot open file" error.

   Fix: ClearQuest Multisite syncreplica now works with packet file names on all supported character sets.


PM51842:

   Problem: When a ClearQuest Web user selects the Print icon, a blank white screen is shown instead of the print preview, if the record has some field values with invalid xml characters (like the arrow character).

   Fix: If the field value of a record contains some invalid xml characters, they are now replaced with space. This allows ClearQuest Web users the ability to Print Preview when pressing the Print icon.


PM53058:

   Problem: If a ClearQuest Web user does not have permission to view a record, sometimes clicking 'Open Related Record' returns a NullPointerException error.

   Fix: ClearQuest Web users that don't have permission now receive a detailed insufficient privilege exception.


PM59316:

   Problem: In ClearQuest Web, when adding a new entry in a list view and then pressing the "Browse" button, the workspace that is brought up does not include any modifications that were done using the CQ API (typically new queries) in the current user session.

   Fix: The problem was fixed by adding a Refresh button in the ClearQuest Web "Browser" dialog.


PM60531:

   Problem: The ClearQuest Export tool exports history records of other stateless records with the same dbid. These records should not be imported.

   Fix: The ClearQuest export tool now only exports the history records of the exported records.


PM64420:

   Problem: When a ClearQuest Web child record is modified on it's parent record using a utility action, a refresh is needed from the parent record for the change to be visible. Note - this only a problem with a utility action not a modify action.

   Fix: ClearQuest Web child records which have been modified using a utility action are now immediately changed on the parent record. A refresh is no longer needed.


PM71739:

   Problem: When using the GSU_CQXE_SubmitRecord function to pop-up a form, ClearQuest Web can not handle more than one reference value in a reference list field.

   Fix: Multiple reference values can now be used with the GSU_CQXE_SubmitRecord function on ClearQuest Web.


PM77116:

   Problem: When editing a ClearQuest query filter using the Cut or Copy action, Pasting to a new query filter will incorrectly affect the original not the new filter.

   Fix: A fix to ClearQuest was made to add a new valuePane for new filter items. This now allows users to modify items using the 'cut/paste' and 'copy/paste' actions.


PM77814:

   Problem: The ClearQuest Full-Text Search Administrator tool (cqtsadmin.pl) does not correctly handle record type and field names in Chinese (and other non-English/double-byte characters) when using the add_record_type and remove_record_type functions.

   Fix: The ClearQuest Full-Text Search (cqtsadmin.pl) script was not decoding field name correctly. This has been fixed and now works for non-English characters.


PM79532:

   Problem: During an installation or upgrade to ClearQuest Web 8.0.0.x, the IBM Installation Manager does not set the JVM heap size value for the WebSphere Application Server profile. By default, when a new WebSphere Application Server profile is created, the JVM value is set to 256 MB. This value is too low for ClearQuest Web 8.0.0.x and must be increased to 1 GB.

   Fix: Install code has been changed so that the JVM heap size value for the WebSphere Application Server profile is set to 1024MB when Installation Manager is creating a new WebSphere Application Server Profile for IBM Rational ClearQuest Web.


PM80631:

   Problem: When you have a ClearQuest text field containing "mailto:<some email address>" on the ClearQuest Windows client, you can start a mail client by clicking the text, and the to address gets filled with <some email address>. This is not working in the ClearQuest Web client.

   Fix: The mailto function in text fields now works the same way on the ClearQuest Web client as on the ClearQuest Windows client.


PM80778:

   Problem: ClearQuest licenses in a web enabled environment are generally consumed by a unique combination of userid + hostid + dbset. In the CQ Web load balanced environment, the addition of more than one potential host (server) can cause more than one license to be checked out for a given user.

   Fix: The ClearQuest license code has been changed to disregard the host and dbset in which the user is performing a login in a web enabled situation. This forces the license server to reserve only one license for a given user id - regardless of the host and or dbset.


PM81433:

   Problem: The ClearQuest Login Stats tab in the ClearQuest Web Site Monitoring window fails to display the information for the logged in users (LoginId, Email, Phone,..) when the number of entries exceeds 100. Row 101 and successive ones show three dots ("...") instead of the actual data.

   Fix: The ClearQuest Web Site Monitoring tool now shows all rows even when the number of logged in users exceeds 100.


PM83701:

   Problem: ClearQuest Web does not have appropriate caching options to prevent browsers from storing local copies of returned data which may be retrieved by other users who have access to the same computer.

   Fix: ClearQuest Web can now be configured via a CQ Web site configuration option to prevent caching headers which might store local copies of sensitive data.


PM86523:

   Problem: When clicking on a URL to enter ClearQuest Web, or if entering ClearQuest Web through an additional web-browser tab, users may experience an "Error 500 java.lang.NullPointerException". If the web user is already logged in, the URLs work as they should. NOTE - this is a regression introduced in ClearQuest Web 7.1.2.10 and 8.0.0.6.

   Fix: The ClearQuest Web URLs now work as they did prior to 7.1.2.10 and 8.0.0.6 even if the web user is not logged in.


PM86720:

   Problem: When using ClearQuest Web with a FireFox browser, scrolling through reference_list fields on a record form is very slow if you are using the mouse wheel.

   Fix: Scrolling through ClearQuest Web reference_list fields using the mouse wheel is now back to a normal speed for FireFox.


PM87949:

   Problem: ClearQuest MultiSite multiutil commands will get an error message when a logical database name or family name has characters in lower case on Windows platforms.

   Fix: ClearQuest MultiSite multiutil commands now work correctly on Windows no matter if the database name / family name is in lower case or upper case.


PM88253:

   Problem: When using Clearquest EmailRelay in SMTP Relay and PostOffice modes, e-mails are not sent if more than one user is on the TO, CC or BCC list because the wrong JavaMail API was being used.  

   Fix: Now e-mails are sent when more than one user is included on the TO, CC or BCC list.


PM89327:

   Problem: ClearQuest Perl and VB Script Hooks that call the CQEntity::FireNamedHook API will fail.

   Fix: ClearQuest users can call the CQEntity::FireNamedHook API in hooks successfully again.