Fixes Defects:

PM23354,PM33122,PM46644,PM51128,PM59071,PM59308,PM60479,PM62929,PM63588,PM65979,PM66896,PM67910,PM68639,PM69506,PM69662,PM69692,PM70791



This patch contains the following software changes:


PM23354:

   Problem: CC/CQ UCM integration users intermittently see more license usage than expected.  It can be as many as 1 extra license checked out per user.

   Fix: The extra license check outs were caused by ClearQuest admin sessions consuming licenses when they should not be.  This has been fixed for all ClearQuest clients.


PM33122:

   Problem: The ClearQuest Full Text Search crawler does not release licenses between index cycles.

   Fix: ClearQuest Full Text Search crawler now releases the license as soon as extraction is done and regains the license the next time the extraction starts.


PM46644:

   Problem: When executing a validation hook in ClearQuest Web via a button, fields that are supposed to be changed within the hook are not updated.  An example is clicking on a "Web Refresh" button to update some fields without having to save the record.  The fields are not changed.

   Fix: This ClearQuest Web fix allows any fields within the validation button hook to be updated correctly.


PM51128:

   Problem: If the time zone of the ClearQuest Web server machine is set to certain locales such as UTC PKT, accessing a ClearQuest record through the OSLC interface results in a "ParseException: Unparseable date" error.  The error is issued when the record is accessed through an application that integrates with ClearQuest Web or through direct calls to the OSLC ClearQuest API.

   Fix: The time zone setting of your ClearQuest Web Server machine will not affect access to ClearQuest records even in locales such as UTC PKT.


PM59071:

   Problem: ClearQuest Web list view control fields have an inconsistent sort order if the unique key field of the reference record is not displayed.  When a CQ Web record with a list view control field is first loaded it is sorted.  Refreshing the record sorts the reference list in a different order.

   Fix: ClearQuest Web list view control fields now sort in a uniform way even if the unique key field of the reference record is not displayed.


PM59308:

   Problem: ClearQuest Web type ahead blocks user input when it's processing a search.  This may cause typed characters to be lost.  Example:  If using a field referring to "users", start typing "admin".   CQ Web will accept input only after filtering the list is complete but you can still type characters.  If the search takes a few seconds, you may have ended up typing "ain", because CQ Web blocked input while you typed "dm".  This means you have to remove the extra characters in order to refer to a valid item.

   Fix: ClearQuest Web type ahead no longer blocks user input when processing a search.


PM60479:

   Problem: When using OSLC with ClearQuest Web to query on records,  if there is a field name which has the "+" character, the return value is 0.

   Fix: ClearQuest Web OSLC will now return the correct number of records even if there is a field name with the "+" character.


PM62929:

   Problem: ClearQuest OSLC API ignores read-only fields when updating records, even if the read-only fields are made editable (non read-only) through a hook.

   Fix: ClearQuest OSLC API now allows read-only fields to be modified if they have been made editable (non read-only) through a hook.  It also throws a warning message when trying to modify read-only fields.


PM63588:

   Problem: When trying to submit or modify a record in ClearQuest Web, selecting a field value which has a value change hook may result in the following error message "Conflict error: Error from RPC server: PROPPATCH failed:  The field "XXX" cannot be modified because it is currently  read-only."  This error occurs when the value change hook is supposed to reset a field to it's original value and then make it read only.

   Fix: ClearQuest Web no longer throws the error message.  The field value will be reset and made read only via the hook.


PM65979:

   Problem: When a new file element is added to a VOB using the command line(cleartool mklem) that was first added as view private file using IBM Rational ClearTeam Explorer (CTE) most of the file element context menu options such as checkout etc  are greyed out in the right click menu even after refresh(from context menu) is done on the file element. After CTE is restarted the menu options are available in the right click context menu.

   Fix: The IBM Rational Clear Team Explorer code has been modified to re-fetch the relevant property of the file element when the user selects the refresh option from the right click context menu options


PM66896:

   Problem: The following security bulletin explains the problem:  http://www-01.ibm.com/support/docview.wss?uid=swg21606317

   Fix: The problem described in the security bulletin is fixed.


PM67910:

   Problem: When running a CQPerl script on ClearQuest RedHat 64-bit, users get the error " ERROR: ld.so: object '/usr/lib/libstdc++.so.6' from LD_PRELOAD cannot be preloaded: ignored" when there is a command or system statement in the script or when back ticks are used.

   Fix: ClearQuest now uses LD_PRELOAD_32 to pre-load the 32-bit c++ library.  This fixes the problem on RedHat 64-bit operating systems.


PM68639:

   Problem: After configuring and deploying the Report Launcher for ClearQuest Web, non-admin users who click on the Manage Reports button receive the following error message "Could not get the Rational Report Management Server URL"

   Fix: Non-admin users can now use the Manage Reports button in the ClearQuest Web Report Launcher.


PM69506:

   Problem: GSkit V8 links are broken when installing ClearQuest or ClearCase on Linux x86 after doing the following:  (1) Install the latest version of GSkit V8, (2) Install ClearCase or ClearQuest and (3) Configure SSL with LDAP for CQWeb.  Trying to access CQWeb using valid LDAP credentials will fail due to the broken links.

   Fix: The GSkit V8 links are now integrated correctly in the Linux x86 ClearCase and ClearQuest Install Manager.  LDAP CQWeb users will no longer see failures.


PM69662:

   Problem: Some fields are not word wrapping as expected on ClearQuest Web 8.0.0.x .  An example with the Defect Tracking schema is the Email field on the Customer record.  This is not a problem with CQ Web 7.1.2.x.

   Fix: All ClearQuest Web 8.0.0.x fields word wrap as expected.  The behavior is now consistent with CQ Web 7.1.2.x.


PM69692:

   Problem: When a CQ Web user executes an action (e.g. modify, resolve...) on a record but does not actually make any changes to the form , clicking the logout button results in CQ Web showing an invalid "Warning: All changes will be lost" message.  This is unnecessary because no changes were made to the record.

   Fix: CQ Web now only shows the  "Warning: All changes will be lost" message after clicking the logout button when changes were made to the record.


PM70791:

   Problem: Type ahead on CQ Web 8.0.0.x does not work when adding query field names.  Typing a letter does not highlight the field names that start with that letter.  It still stays on the first one.  This is not a problem with ClearQuest Web 7.1.2.x.

   Fix: ClearQuest Web 8.0.0.x type ahead for query field names now works correctly.  This makes it consistent with ClearQuest Web 7.1.2.x.