Fixes Defects:

PI08587,PI10643,PI11651,PI17340,PM44568,PM81769



This patch contains the following software changes:


PI08587:

   Problem: After executing a ClearQust Web query with an apostrophe in its name, the query tab title displays a bogus value where the apostrophe belongs.

   Fix: After executing a ClearQust Web query with an apostrophe in its name, the query tab title now displays correctly.


PI10643:

   Problem: Attempts to use list views to view a form from IBM Rational ClearQuest (CQ) Web results in the Parent / Child list box button referencing the wrong list box.

   Fix: ClearQuest technote #1670547 explains how to resolve this problem by using a workaround.


PI11651:

   Problem: Given the following situation:  When using the ClearQuest classic designer (cqdesign.exe), two users login and connect with the same account, and check out the same schema.  If the first user saves their schema changes and then the second user also tries to save changes, there is a risk that the first user's changes will be overwritten.  This is despite an error message that says that data cannot be saved.

   Fix: When saving a schema using the ClearQuest classic designer (cqdesign.exe), if the schema has already been saved by someone else - this condition is detected and data is no longer committed.  The user is warned that changes cannot be saved and that a logoff is warranted.


PI17340:

   Problem: ClearQuest Web out of memory errors can occur in a multisite environment when displaying names of reference fields.

   Fix: ClearQuest Web out of memory errors should happen less often in a multisite environment when displaying names of reference fields.


PM44568:

   Problem: When using the UCM integration with ClearQuest Web, users receive a null pointer exception if there is no view available for the stream associated with the ClearQuest record.

   Fix: ClearQuest Web users who are using the UCM integration now receive a valid error message informing them there is no view available for the stream associated with the record.


PM81769:

   Problem: When using Oracle databases, indexes that are created on ClearQuest date_time fields are ineffective when those fields are used as query filters.

   Fix: When using Oracle databases, ClearQuest query filtering has been fixed so indexes are now utilized on date_time fields.