Fixes Defects:

PI05258,PI05995,PI08291,PI11942,PI12706,PI12994,PI13106,PI13880,PI14297,PI14622,PI14808,PI15027,PI15457,PI17416,PI17591,PI18465,PI18785,PI19492,PI19646,PI19649,PI19771,PI20761,PI23200,PM39138,PM47047,PM56716,PM64247,PM74702,PM75669,PM81143,PM81900,PM83002,PM85281,PM86592,PM87092,PM92565,PM92870,PM93007,PM93857,PM96414,PM99113



This patch contains the following software changes:


PI05258:

   Problem: After migrating from Crystal Reports data-push to data-pull reporting model, ClearQuest Reports do not allow selection of multiple values in dynamic parameters.

   Fix: When migrating from Crystal Reports data-push to data-pull reporting model, ClearQuest Reports now allow selection of multiple values in dynamic parameters only after following the steps outlined in technote #1679569.
http://www.ibm.com/support/docview.wss?uid=swg21679569


PI05995:

   Problem: In ClearQuest Web v8.0.1.x, the Ctrl+Home and Ctrl+End keyboard shortcuts do not work as expected when used with multiline text fields.  Ctrl+Home moves focus to the first tab on the record rather than the expected begining of the text in the multiline field.  Ctrl+End moves focus to the last tab on the record rather than the expected end of the text in the multiline field.  This is not a problem when using ClearQuest Web v8.0.0.x.

   Fix: When using ClearQuest Web, the Ctrl+Home keyboard shortcut now correctly moves focus to the beginning of the text in the multiline field.  Ctrl+End now moves to the end of the text in the multiline field as expected.


PI08291:

   Problem: When using ClearQuest Web with Internet Explorer 9 and later, some vertical and horizontal scroll bars do not work as expected.  FireFox works fine.

   Fix: When using ClearQuest Web with Internet Explorer 9 and later,  the vertical and horizontal scroll bars now work as expected.


PI11942:

   Problem: The "Permissions" dialog for the workspace folders in ClearQuest Web intermittently fails to load the column values in the right panel.  The problem happens most often after you click the "Calculate" Button.

   Fix: ClearQuest Web workspace "Permission" dialog now loads all column values correctly.


PI12706:

   Problem: When using ClearQuest Web with the Representational State Transfer (REST) Universal Resource Indicator (URI) capability to start a new Submit record form and prefill certain values, or have user-interaction that modifies one of these pre-filled fields prior to saving, data loss occurs on the modified field.

   Fix: When using ClearQuest Web with the REST URI, the modified pre-filled fields now save correctly without any data loss.


PI12994:

   Problem: ClearQuest Web users see a vertical scroll bar displayed on the right side of their page even if it is not needed.  This happens only with Internet Explorer.

   Fix: ClearQuest Web users now only see the vertical scroll bar when it's needed.


PI13106:

   Problem: Deleting a record type that is used in a query will cause the ClearQuest web client to fail to load the query's workspace folder.

   Fix: ClearQuest Web can now open a query workspace folder even if it contains a query that uses a record type has been deleted.


PI13880:

   Problem: When running a Perl script which calls ClearQuest APIs, users can receive a "select failed: An operation was attempted on something that is not a socket" error.

   Fix: A ClearQuest Perl defect has been fixed so the above error message no longer appears.


PI14297:

   Problem: ClearQuest Web can't export a resultset that has fields greater than 32K characters to an Excel spreasheet.  A failure will occur with the error: "The Maximum length of cell contents (text) is 32,767 characters"

   Fix: ClearQuest Web users are now asked if they want to truncate the fields which exceed 32,767 characters.  If you select 'Yes', CQ will truncate the field and export to an Excel spreadsheet.


PI14622:

   Problem: ClearQuest Web doesn't show all the field values in a reference field if the first section of a dotted field path is a reference list. 

For example: a schema has Record type "A" and Record type "B" and record type "A" has Reference_List to "A" and Reference_List to "B".  When a ClearQuest Web record "A1" has two "A_child" child records that both have some references to a "B" record, ClearQuest Web displays on "A1" both "A_child" records but only the "B_child" records of the first "A_child".

   Fix: ClearQuest Web now shows all the field values in a reference field if the first section of a dotted field path is a reference list.  In the above example, ClearQuest Web now correctly displays all referenced "B_child" records.


PI14808:

   Problem: If you have a duplicate ClearQuest Web parent/child form control without a label, all form controls with a higher tab order than the duplicate parent/child control will not display. Even subsequent tabs on the record will disappear.  This is only a problem when using Internet Explorer.

   Fix: ClearQuest Web form controls now display correctly when using an Internet Explorer browser, even if there is a duplicate parent/child control without a label.


PI15027:

   Problem: The default record type is displayed even if a ClearQuest Web user does not have any permission to submit it.

   Fix: The default record type no longer shows on ClearQuest Web when the user does not have permission to submit it.


PI15457:

   Problem: When using a ClearQuest Web OSLC (Open Services for Lifecycle Collaboration) delegated user interface (UI) creation/linking dialog box, you may see "An error occurred while retrieving record data" message when attempting to perform an action on the child record of the parent loaded in the delegated UI.  This problem is intermittent.

   Fix: ClearQuest Web OSLC has been fixed so delegated UI creation/linking dialog boxes can now perform an action on the child record of the parent loaded in the delegated UI.


PI17416:

   Problem: When using a reference-list field on a ClearQuest Web form, a post action hook on the "New" button doesn't work, so any data that depends on that hook will not be correct.

   Fix: When using a reference-list field on a ClearQuest Web form, a post action hook on the "New" button now works correctly.


PI17591:

   Problem: If your ClearQuest Web browser locale is French and your ClearQuest Web Server is on an English locale, the MANDATORY FIELD MESSAGE is not translated to French.

   Fix: The MANDATORY FIELD MESSAGE is now translated to French, if your ClearQuest Web browser locale is French and your ClearQuest Web Server is on an English locale.


PI18465:

   Problem: When using ClearQuest with OSLC (Open Services for Lifecycle Collaboration) V1 to perform a FULL update of a record that contains a multiline (ML) string field, a situation may arise that causes either data truncation or a "conflict 409" failure during a PUT request.

   Fix: When using ClearQuest OSLC to perform a FULL update of a record that contains a ML string field, data truncation or a "conflict 409" failure no longer occurs during a PUT request.


PI18785:

   Problem: If a ClearQuest Web user uses an OSLC request to get a field that contains a second-degree reference list field in RDF format, the response is invalid with RDF verification.

   Fix: If a ClearQuest Web user uses an OSLC request to get a field that contains a second-degree reference list field in RDF format, the response now returns the correct RDF result.


PI19492:

   Problem: When using ClearQuest Web with Internet Explorer 8 on a non-English OS, charts do no display.

   Fix: Charts now display when using ClearQuest Web with Internet Explorer 8 on a non-English OS.


PI19646:

   Problem: ClearQuest Web does not translate the Private and Public folder names according to the user's browser locale.

   Fix: ClearQuest Web Private and Public folder names are now translated into 9 languages according to the user browser locale, instead of 4 languages based on the server locale.


PI19649:

   Problem: A ClearQuest security vulnerability was found.

   Fix: Fixes a ClearQuest security vulnerability.


PI19771:

   Problem: Using the ClearQuest REST URIs to log in automatically to ClearQuest web causes a session timeout.

   Fix: ClearQuest web users can now login automatically through the ClearQuest REST URI without a session timeout.


PI20761:

   Problem: When parsing a ClearQuest Web result set to XML using the REST URI, the date format incorrectly changes from SHORT to LONG.

   Fix: The date time field in the ClearQuest Web REST URI result set now uses the format specified in the user preference and does not always default to LONG.


PI23200:

   Problem: In ClearQuest Web, an issue occurs after adding a reference item to a reference list.  That reference cannot be opened from the list when it is double clicked until the record has been saved.  The following error occurs: ERROR: "THIS RECORD WAS NOT FOUND."

   Fix: This internal representation of the ClearQuest Web record was incorrectly constructed in this use case.  It has been corrected and the error no longer occurs.


PM39138:

   Problem: The ClearQuest Full Text Search Admin tool's "--update_fts_prop_files" option stops working  in the middle of a "--setup_cq_fts" after modifying the batch paramater settings in the cqfts admin XML file.

   Fix: ClearQuest Full Text Search Admin tool's "--update_fts_prop_files" option can now update batch parameters in the middle of a "--setup_cq_fts".


PM47047:

   Problem: The "alm_integrator script" shipped with the ClearQuest ALM 1.1 package does not follow the Workflow Automation rules to set the owner.

   Fix: The "alm_integrator script"  shipped with the ClearQuest ALM 1.1 package now automatically sets the owner according to the Workflow Automation rules.


PM56716:

   Problem: When you use the ClearQuest Eclipse client's "Convert to SQL" tool to convert a new query, the resultset returned from running the SQL query doesn't match the resultset of running the regular query.

   Fix: ClearQuest Eclipse client now correctly displays the resultset according to the display fields of the converted SQL query.


PM64247:

   Problem: The bookmark of a ClearQuest Web record is redirected to another URL using a "#" character to replace the REST URI.  This causes a problem when using a reverse proxy.  The base URL is changed from http://XXXX to https://XXXX, and the parameters after the "#" charcater do not match, resulting in a broken bookmark.

   Fix: The ClearQuest Web bookmark URL is no longer changed, so it now works correctly when using a reverse proxy.


PM74702:

   Problem: After exporting a CQ FTS (full text search) resultset to either an Excel spreadsheet or a text file, ClearQuest Web ignores the filters selected on the Search Scope option.

   Fix: After exporting a FTS resultset, ClearQuest Web now correctly accounts for any filters selected on the Search Scope option.


PM75669:

   Problem: ClearQuest Web users can not duplicate a record from a different record type.  It fails with the error message: "No Record Found".

   Fix: ClearQuest Web users can now duplicate stateful records of different record types.


PM81143:

   Problem: When attempting to run a SQ-edited query using ClearQuest OSLC 2.0 provider code, users get a 501 status code error.

   Fix: SQL-edited queries using ClearQuest OSLC 2.0 provider code now work correctly.


PM81900:

   Problem: When using ClearQuest Web with Internet Explorer, if you insert an empty value to a static text field, it displays as null.

   Fix: If you enter an empty value to a ClearQuest Web static text field, it now shows as empty instead of null.


PM83002:

   Problem: When viewing different ClearQuest Web records using OSLC links in separate Internet Explorer tabs, only the first record is shown on all tabs.  The other record URLs are ignored.

   Fix: When viewing different ClearQuest Web records using OSLC links, the separate Internet Explorer tabs now show the correct records specified in the URLs.


PM85281:

   Problem: Nested fields such as Owner.fullname are not updated on ClearQuest Web forms when the owner field is updated by a hook associated with a button.

   Fix: ClearQuest Web now updates nested fields when the owner field is updated by a hook associated with a button.


PM86592:

   Problem: The ClearQuest Web Security Context Access Denied message, which is displayed when users don't have access to view a record, is slightly incorrect when viewed using Internet Explorer.  The text ?apos; appears instead of apostrophes.  Here's an example of an incorrect message:  Error from RPC server: Failed to find the record: CRMUD0136E Access denied for retrieving record, ?apos;1395?apos;, record type?apos;Defect?apos;.

   Fix: The ClearQuest Web Security Context Access Denied message now correctly displays apostrophes.


PM87092:

   Problem: ClearQuest Web scrollbars on child popup windows are not working properly when using Internet Explorer 9.  The scrollbars cannot be pulled in a vertical or horizontal direction to scroll through text or items in the child window.

   Fix: ClearQuest Web scrollbars on child popup windows now function properly.


PM92565:

   Problem: When you select the Repository entry in the ClearQuest Web login page, an incorrect warning message always appears saying "The value you entered is invalid".  It appears even when you have a valid value.

   Fix: When you select the Repository entry in the ClearQuest Web login page, the warning message no longer appears if you have a valid entry entered.


PM92870:

   Problem: When WAS security is enabled, the ClearQuest Web "Site Administration Monitoring" login window is missing labels and buttons.  This is not a problem with ClearQuest Web 8.0.0.x.

   Fix: The ClearQuest Web "Site Administration Monitoring" login window now has all labels and buttons.


PM93007:

   Problem: When using ClearQuest 8.x, several operations on records containing a large number of histories or datetime field values are significantly slower than on ClearQuest 7.x versions.  These operations include viewing records, querying records, and certain modifications of records.

   Fix: ClearQuest datetime parsing has been improved to cache and reuse formats whenever possible, thus speeding up the processing of records with a large number of datetime field values and/or histories.


PM93857:

   Problem: When using ClearQuest Full Text Search to look for values to fill in a reference list field (eg customer), if the results are displayed on multiple pages, you can't view the last page.  Trying to view the last result page will revert back automatically to the previous page.

   Fix: When using ClearQuest Full Text Search to look for items to fill in a reference list field, you can now view the last page.  It no longer reverts back to the previuos page.


PM96414:

   Problem: After inputting invalid values into a drop-down list box, clicking the drop-down arrow, and dismissing the warning dialog, ClearQuest Web 8.0.1.x users can no longer enter values into any form control.  This problem only happens when using Internet Explorer and ClearQuest Web 8.0.1.x.

   Fix: After inputting invalid values into a drop-down list box, ClearQuest Web 8.0.1.x users can now enter values into form controls.


PM99113:

   Problem: If a stateless ClearQuest Web record has a slash or back-slash in its primary key field, a link that is created through the bookmark or email functionality fails to escape the (back)slash and results in an "Error 404 Not Found" message.

   Fix: ClearQuest Web bookmark or email functionality now works correctly when a record has a slash or back-slash in its primary key field.