Fixes Defects:

PI05752,PI06404,PI06756,PI08283,PI08639,PI08729,PI09577,PI10332,PM22934,PM37014,PM38989,PM44288,PM56099,PM63880,PM66412,PM88988,PM90345,PM92563,PM92893,PM95096,PM97101,PM97153



This patch contains the following software changes:


PI05752:

   Problem: ClearQuest does not always allocate buffers efficiently when building choice list queries.  This can lead to ClearQuest Web out of memory errors.

   Fix: ClearQuest has improved buffer allocations for choice list queries.  This will reduce memory usage and reduce the chances for out of memory errors.


PI06404:

   Problem: ClearQuest web users may experience hung threads under periods of heavy load.  This can result in timeout errors and temporary hangs for certain operations.  The WebSphere SystemOut.log may show the error "JRPC.RPCTimeoutError: Read timed out" when this condition occurs.

   Fix: The ClearQuest RPC library has been updated to protect against thread deadlocks (also known as hung threads) during periods of heavy load.


PI06756:

   Problem: A user marked as restricted in the ClearQuest Web site configuration security preferences sometimes consumes a license when it should not do so.

   Fix: The source of the extra license checkout has been identified and that checkout is no longer performed for this ClearQuest Web restricted user.


PI08283:

   Problem: Attachments that are added in an action initialization hook could not be downloaded from ClearQuest Web until after saving the record.

   Fix: Attachments that are added in an action initialization hook can now be downloaded from ClearQuest Web before saving the record.


PI08639:

   Problem: The ClearQuest LoadEntity() API fails for validation hooks.

   Fix: The problem with the ClearQuest LoadEntity() API has been fixed so it no longer fails during validation hooks.


PI08729:

   Problem: ClearQuest Full-Text Search (FTS) Administrator tool fails on MultiSite databases which have been deactivated.  The failure occurs during the batch indexing phase.

   Fix: ClearQuest Full-Text Search (FTS) Administrator tool now functions correctly on ClearQuest Multsitie databases which have been deactivated .


PI09577:

   Problem: When using the ClearQuest API "GSU_CQXE_SUBMITRECORD" to copy a CQ Web record form, multi-line string fields which contain leading blank lines will not retain those blank lines in the copied record form.

   Fix: ClearQuest Web has been changed so leading blank lines are now retained when a multi-line text field is copied via the "GSU_CQXE_SUBMITRECORD" API.


PI10332:

   Problem: When a ClearQuest Web user adds or deletes a reference list value using a value_change hook, it is fired twice.  The first time the hook is fired it returns an empty list.  The second time it returns the correct reference list value.

   Fix: ClearQuest Web will now only fire value_change hooks once on reference list values.


PM22934:

   Problem: When running a query using the ClearQuest "cqtool new_query" command, the result set columns are not displayed in the order that you specify in the arguments.  As example, the command "cqtool new_query -severity -headline" displays a result set with headline as the left column and severity as the right column.  It should have the reverse - severity as the left column and headline as the right column.

   Fix: When running a query using the ClearQuest "cqtool new_query" command, the result set columns are now displayed in the correct order matching what is specified in the command arguments.


PM37014:

   Problem: The EPIC editor plug-in used for editing Perl code in the ClearQuest Eclipse-based Designer does not support UTF-8. This causes errors in displaying the pre-log template of hook code for some situations.

   Fix: The ClearQuest Eclipse-based Designer now recognizes these cases and displays the record's dbname as the prefix. This does not affect what is actually stored in the database. The only behavioral change is visual.


PM38989:

   Problem: There is no way to insert carriage returns into multiline text fields using the ClearQuest cqtool "edit_record" command.

   Fix: The ClearQuest cqtool "edit_record" command now allows carriage returns to be inserted into multiline text fields.


PM44288:

   Problem: By default, Oracle does not create indexes on foreign keys.  They must be created manually, and failure to do so, could lead to slower ClearQuest performance.

   Fix: ClearQuest now explicitly creates the indexes for foreign keys on Oracle databases.  This is now consistent with our other database vendors (DB2 and SQL Server).


PM56099:

   Problem: When upgrading the package version of multiple record types with double-byte names, ClearQuest displays the following error message: Attempting to use a string which is too long. The limit on the number of bytes in the string is 255 but the string actually contained 268.

   Fix: ClearQuest package version upgrades complete successfully when done on multiple record types with double-byte names.


PM63880:

   Problem: If a ClearQuest login ID is specified as "domain\username" (example: "domain\212009807") , it gets reformatted or mangled when refreshing a ClearQuest Web page.  If a ClearQuest Web session times out, the login dialog pops up with the wrong username.

   Fix: ClearQuest Web has been fixed to handle login names in the format "domain\username".  They will no longer get reformatted or mangled when refreshing a ClearQuest Web page.


PM66412:

   Problem: ClearQuest users with the privilege "All Users/Groups Visible" unchecked will be shown groups they are not a member of in a choice list for a reference to groups field. Similarly, they can also see users that are part of these groups in a choice list for a reference to users field.

   Fix: ClearQuest users with the privilege "All Users/Groups Visible" unchecked can now only see the groups they are a member of, and can only see users that are a member of those same groups, in choice lists for the groups and users record types. The exception is the Everyone group, which does not provide visibility to any other users.


PM88988:

   Problem: When a new record type, stateless or stateful, is created with the ClearQuest Eclipse Designer, the default behavior for the ratl_mastership system field is set to READONLY.  The ClearQuest Windows Classic Designer behaves differently, setting the behavior of ratl_mastership to OPTIONAL.  For stateful record types, the behavior for the Submitted state is set correctly as OPTIONAL, but any other states inherit the default READONLY behavior.  This means users are not able to change the mastership of stateless record types and stateful record types in any state except Submitted.

   Fix: In the ClearQuest Eclipse Designer, new record types are now created with the correct default behavior of OPTIONAL for the ratl_mastership system field.  This is consistent with the behavior of the ClearQuest Windows Classic Designer.


PM90345:

   Problem: In the ClearQuest Web login dialog window, the cursor defaults to the User ID field even if "Remember User ID" is checked.

   Fix: In the ClearQuest Web login dialog window, the cursor will now set the focus to the Password field when "Remember User ID" is checked.


PM92563:

   Problem: The documentation on how to change the ClearQuest Full Text Search password is inadequate.

   Fix: Reference information on the cqtsadmin.pl command has been updated in the ClearQuest Information Center


PM92893:

   Problem: When using the ClearQuest GSU_CQXE_SubmitRecord() API for setting a reference list field on a tab that is not displayed on the submit form, only the first value is added to the reference list field.  The rest of the values are ignored.

   Fix: The ClearQuest GSU_CQXE_SubmitRecord() API has been fixed so that all reference list values are added.


PM95096:

   Problem: The ClearQuest V8.0.1 Information Center provides insufficient information about ClearQuest Web load-balancing.

   Fix: The instructions on ClearQuest Web load-balancing have been augmented in the ClearQuest V8.0.1 Information Center .


PM97101:

   Problem: The ClearQuest 8.0.1 Information Center includes a topic about escaping special characters in ClearQuest Full Text Search.  The information is incorrect:  SOLR disregards special characters when searching for the search term.

   Fix: The topic about escaping special characters in ClearQuest Full Text Search has been removed from the Information Center.


PM97153:

   Problem: The email generated by ClearQuest using EmailPlus and EmailRelay setup in PostOffice or SMTP Relay mode may fail to be sent due to the email exceeding the default limit of 2000 characters that is set by ClearQuest OSLC.

   Fix: The ClearQuest Information Center has been updated to explain how to increase the limit.