Fixes Defects: PI66613,PI69194,PI74220,PI74735,PI75039,PI75052,PI76052 This patch contains the following software changes: PI66613: Problem: In ClearQuest Web, items in the List controls cannot be removed when the List View layout of the record is applied. Fix: In ClearQuest Web, items in the List controls can now be removed when the List View layout of the record is applied. PI69194: Problem: The Title field cannot be displayed in the OSLC delegated UI search result set on ClearQuest Web. Fix: The Title field can now be displayed in the OSLC delegated UI search result set on ClearQuest Web. PI74220: Problem: Saving or running queries from the query editor in ClearQuest Web fails for users that do not have SQL Editor privilege. Fix: Saving or running queries from the query editor in ClearQuest Web works appropriately for non SQL Editor users, provided the change does not explicitly set new SQL. PI74735: Problem: Running actions on a record which is enabled to use the ClearCase / ClearQuest UCM Integration results in a CRMCU0087E error. The symptom is seen on ClearQuest Web on AIX with the Zh_CN locale. Fix: ClearQuest was using the wrong default locale when executing actions on ClearCase / ClearQuest UCM records. This problem has been fixed. PI75039: Problem: Dates in the List View control are not formatted with the correct timezone and locale when the Deferred Loading of Reference Lists feature is enabled on ClearQuest Web. Fix: Dates in the List View control now have the correct timezone and locale when the Deferred Loading of Reference Lists feature is enabled on ClearQuest Web. PI75052: Problem: When loading ClearQuest Web records via REST APIs, there can be a delay caused due to unnecessary reloading of the UI if the user is already logged into ClearQuest. Fix: Reloading of the ClearQuest Web UI is prevented for this use case. PI76052: Problem: In Rational ClearQuest,using a fieldpath name to get the value of a field will fail with error CRMUD0207E when a reference field in the fieldpath has no value. Fix: ClearQuest was not properly handling the case of a null reference in a fieldpath when getting a field value. This problem has been fixed.