HP Quality Center 9.

2 Patch 23 Readme
Software version: 9.20 Patch 23 / 1 May 2009 This document provides the following information about HP Quality Center 9.20 Patch 23: Fixed Defects Limitations Issues Addressed by Previous Patches Installation Instructions Support Legal Notices

Fixed Defects
BPT4SAP
Problem: A BPT test type description field is not editable if the user logs out and logs back in to the Test Plan module. Solution: The problem is fixed.

Manual Runner
Problem: When running a test set manually, field values that you provide in the Manual Runner for the first test are not applied to subsequent tests. Solution: The problem is fixed. Problem: In the Manual Runner dialog box, the value in the Test Source column is the test ID, not the test name. Solution: The problem is fixed. A new field is added that displays the test name is available. Note: In new project only the test name is displayed. In older project the test name and ID are both displayed

Document Generator
Problem: If you select the Full page Requirements layout, and customize the layout to include the Comments field, the document does not display comments. Solution: The problem is fixed.

Releases module
Problem: Long field labels are truncated even when there is sufficient space to display the entire label. Solution: The problem is fixed.

Analysis - test set summary graph

Problem: The graph might display incorrect results if tests it includes belong to folders with similar long names. Solution: The problem is fixed.

Site analysis
Problem: In the Site Analysis filter, if you select a domain, and scroll down in the Set Filter dialog box until the domain node is no longer visible and then click OK, the graph does not display data from the selected domain. Solution: The problem is fixed.

Work Flow
Problem: The field RN_STATUS, when called from Run_Fields, always returns 'Not Completed' regardless of its actual value. Solution: The problem is fixed. Problem: When SetDefectsFilter is called from Defects_BugsFilterChanged, an error occurs. Solution: The problem is fixed.

OTA
Problem: To change the value of the fields ST_STATUS and ST_EXECUTION_DATE, it is necessary to call the post method twice. Solution: The problem is fixed. It is sufficient to call the post method only once.

Out of memory
Problem: When Quality Center is installed on an AIX platform, Out Of Memory error for Java's compression objects might occur. Solution: The problem is fixed.

Mail
Problem: If a message is sent to multiple users, and the SMTP server determines that some of the recipient mail addresses are not valid, the message is not delivered to the valid mail users either. Solution: The problem is fixed.

Test Lab
Problem: When working with an Oracle database server, an error "[Mercury][Oracle JDBC Driver]long (>4k) parameters are only allowed in the values list of simple insert/update statements" may occur during test execution. Solution: The problem is fixed.
2

Log
Problem: The Site Administration log file includes unnecessary CInvalidRequestException errors. Solution: The problem is fixed.

Test Plan
Problem: When adding a new design step, the cursor is positioned by default in the Expected Result field, not in the Description field. Solution: The problem is fixed. Problem: When copying a test together with its called tests to a project with version control enabled, the copy fails with error "Failed to paste data". Solution: The problem is fixed.

Alerts
Problem: The Clear Alerts command does not remove alerts. Solution: The problem is fixed. Limitation: When you choose the command the first time, an error message displays. Ignore the error message.

Enhancements
Database driver
The Data Direct driver is upgraded to 3.72 and certified.

Issues Addressed by Previous Patches

Quality Center 9.20 Patch 22

BPT4SAP
Problem: The BPT Manual Runner commands ActNextStep and ActPassSelected cannot be executed via workflow. Solution: The problem is fixed. Problem: When running very large test sets, the Automatic Runner dialog box loads tests slowly. Solution: The problem is fixed.

Anti-Virus
Problem: If the McAfee Host Intrusion Prevention software is installed on client machines, it may block Quality Center. Solution: The problem is fixed.

Version Control
Problem: Copying a test between projects fails, if the test includes calls to other tests, and if the target project is version control enabled. Solution: The problem is fixed.

Database Termination Tool

Problem: When moving the repository of large projects from the database to the file system, an error may occur during the calculation of the repository size. Solution: A new site configuration parameter SKIP_GET_REPOSITORY_SIZE is available. Set the parameter to "Y" for the tool to skip the calculation of the repository size.

Test Lab
Problem: If you select a test in the Execution Grid, and select the Go to Test in Test Plan Tree command, the wrong test may be located. Solution: The problem is fixed.

Requirement
Problem: Assigning a requirement to a cycle may take a long time. Solution: The problem is fixed.

Log
Problem: Denied logins are not reported in the logs. Solution: The problem is fixed.

Quality Center 9.20 Patch 21

Fixed Defects
Login
Problem: When logging in to Quality Center where the servers URL and IP are not the same, an error occurs. Solution: The problem is fixed.

Manual Runner
Problem: On rare occasions, an error occurs when adding or editing a test step. Solution: The problem is fixed.

Site Analysis
Problem: For different time periods, the numbers of licensed users may differ slightly. Solution: The problem is fixed.

Document Generator
Problem: If Hummingbird/Open Text is running on the client machine, the user is prompted to save the DOT files during generation of the report. Solution: The problem is fixed.

OTA
Problem: The TDConnection.Password property returns the unencrypted password. Solution: The problem is fixed.

Customization
Problem: A user belonging to a group with the Add Test permission, but not the Modify Test permission, can create a new test only once after logging in. Solution: The problem is fixed.

Linked defect
Problem: When clicking a linked defect from a test step, the browser may display an Access Violation error. Solution: The problem is fixed.

Test Lab
Problem: When adding several tests at once to a test set, you cannot navigate from one of the test instances to its corresponding test. Solution: The problem is fixed.

Analysis
Problem: When selecting a Current Test Set graph, but no test set is selected, an error occurs. Solution: The problem is fixed. The Current Test Set graphs are disabled if no test set is selected.

Quality Center Explorer

Problem: If you are running Quality Center on Quality Center Explorer, when working in the Releases module, an error may occur. Solution: The problem is fixed.

Enhancements
Multi Selection of Tests and Requirements
Selecting multiple requirements with the Shift key is now available in the requirements tree view, for requirements on the same level under the same parent. In the Test Lab module, you can now select multiple tests to add to a test set by using the Ctrl key. Limitations: Pressing the Shift key to select multiple records clears any previous selection made by pressing the Ctrl or Shift keys.

Requirement Analysis Coverage View

There is a new Settings button in the Requirements toolbar which opens the Analysis Settings dialog box. You can select the following options: Coverage analysis Displays the current coverage status of each requirement: Passed, Failed or Not Completed - Requirements whose linked tests have been executed. No Run - Requirements whose linked tests all have the No Run execution status. Not Covered - Requirements not linked to a test.

Execution analysis Displays the execution status of each requirement in the selected cycles: Passed, Failed or Not Completed - Requirements whose linked tests were executed in the selected cycles. No Run - Requirements whose linked tests were never executed, or were executed in cycles other than the selected. Requirements with a Not Covered status are not displayed in this view.

Limitations
Progress Graph
Problem: It is not possible to use Replace in Defects/ Requirements for Target Release/ Cycle fields. An access violation error will appear

Quality Center 9.20 Patch 20

Fixed Defects

BPT4SAP
Problem: It takes a long time for a test to upload when opened from the Test Lab Execution Grid. Solution: The problem is fixed.

WinRunner
Problem: When you run a WinRunner Batch test, the called tests do not report the run results. Solution: The problem is fixed.

Workflow
Problem: The PageNo object does not work when used in the Test_MoveTo event. Solution: The problem is fixed.

Analysis
Problem: The Coverage Chart (Requirements module > Coverage Analysis view > Test Coverage Chart > Coverage Chart) displays results based on the last run instead of coverage by cycle status. Solution: The problem is fixed.

Customization
Problem: Users of groups that are assigned the Configure Automail task, are not able to configure automail. Solution: The problem is fixed.

Defect
Problem: When changing the Subject field of a defect in the defects grid, an error message displays. Solution: The problem is fixed

Limitations
Progress Graph
Problem: In rare cases 'Sum of' option might be accidentally enabled and the executed graph will generate and exception. Workaround: Manually disable the option.

Quality Center 9.20 Patch 19

Fixed Defects
Workflow
Problem: In setup workflow, after defining a field as a required field, it becomes read-only. Solution: The problem is fixed.

Rich Text
Problem: On Windows 2000 client machines, when resizing or maximizing a rich text window, the web browser might freeze. Solution: The problem is fixed.

Requirements - Coverage Analysis Test Plan Report

Problem: In the Tests Coverage dialog box, when you click an entity status in the Entity Status column, a blank page opens. Solution: The problem is fixed.

BPT
Problem: If a business process test in a test set comprising two tests returns an error, the second test remains in a "Connecting" state. Solution: The problem is fixed Note: If an ExitTest command is executed in the business process test, the test will run with a "Passed" status. Problem: If a business process test contains more than one instance of a component, and the component parameters are exported to Excel, only the first component instance is updated after values are added in Excel and imported. Solution: The problem is fixed.

Copy-Paste Tests
Problem: When copying tests between two servers that are on different domains, a "Failed to Paste Data" error occurs. Solution: The problem is fixed.

General
Problem: If the Delete button is pressed while renaming an entity, the entity might be deleted instead of the entity name. Solution: The problem is fixed.

Limitations
Microsoft Windows Vista Aero
Problem: Windows Vista Aero is not supported in Quality Center 9.2. Workaround: To work with Quality Center 9.2, Windows Vista Aero must be disabled.

Quality Center 9.20 Patch 18

Login
Problem: When trying to connect user receives the error "Failed to obtain a connection to schema, timeout expired". This happens because old connections were not removed. Solution: The problem is fixed.

QCExplorer
Problem: The QCExplorer browser hangs when clicking the X button. Solution: The problem is fixed.

Quality Center 9.20 Patch 17.1

Requirements
Problem: When viewing Requirements coverage an error message Item Not Found might appear. Solution: The problem is fixed.

Quality Center 9.20 Patch 17

10

Fixed Defects
Workflow
Problem: Event 'Bug_FieldCanChange' is not triggered when creating a defect from Manual Runner for a test whose test set has not been assigned to a cycle. Solution: The problem is fixed.

Client Side Environment

Problem: The Add-Ins page does not display a warning that Quality Center client side requires CAPICOM.DLL on client machine. Solution: The problem is fixed.

Client Side Login Page

Problem: Login button might become not visible due to client screen resolution configuration. Solution: The problem is fixed.

BPT
Problem: When executing two or more BPT test sets via Automatic Runner in parallel, one or more runs might fail with Host Is Busy error message. Solution: The problem is fixed.

Enhancements
Security
An option to use SSL for login phase on non-SSL connections. When connecting to a Quality Center server using an "http://..." URL, the Quality Center client can issue just the "Login" request using an "https://..." URL. This provides for enhanced confidentiality when transmitting your password across the network, while not enduring the performance penalty of full SSL. In the In order to activate SSL for login run on the client machine 'WebGateCustomization' tool, check 'login SSL mode' and assign 'SSL port'.
11

You also need to ensure the web server on Quality Center server is set to receive SSL connections. Note that this option is not required if your QC is using SSL (HTTPS).
.

Quality Center 9.20 Patch 16

Document Generator
Problem: The Document Generator report includes the character @ on every line of the report. Solution: The problem is fixed. Problem: Step attachments are not included in the Document Generator report. Solution: The problem is fixed. Problem: The value of the TestID field does not appear when a full page view of the Test Plan report is selected. Solution: The problem is fixed.

OTA
Problem: For the History object, the oldValue property does not work. Solution: The problem is fixed.

BPT Test Lab

Problem: In the Test Iterations or Component Iterations dialog box, when a parameter includes the Russian character , and parameters are saved using the Export feature, the character is read as a field delimiter in the .csv file. This causes the parameter to be split when the parameters are imported. Solution: The problem is fixed.

Tools Menu
Problem: The list of projects in Change Project is longer than the recent five projects. Solution: The problem is fixed.

Replace All
Problem: In the "Find/Replace" dialog box, when clearing the "From Beginning" option, all values are replaced. Solution: The problem is fixed. Problem: In the Find/Replace dialog box, when using the Replace all option and a required field has an empty value, you are prompted to add a value. If you double-click Cancel, an exception error occurs. Solution: The problem is fixed.

12

Defects
Problem: When clicking a Link Defect Entity from a step, the browser might crash. Solution: The problem is fixed. Problem: When opening the Defect Details dialog box and clicking the Execution Report link, the browser might crash. Solution: The problem is fixed.

Limitations
In rare situations, when editing or adding steps during test execution, the step update fails. In this situation, log out and log in, and repeat the edit or add function. Access violation error might appear in Test Lab when closing the "Run Steps" followed by the "Test Instance Properties" dialogs by pressing "X". To avoid error use Close instead of X Patch 16 does not support STM when client side is installed via 'client side installation'. To solve the problem connect to Quality Center as a user via browser. This will install the necessary client side components and enable the integration

Quality Center 9.20 Patch 15

Security
Problem: A security issue might allow unauthorized access to Site Administration. Solution: The problem is fixed. A new site configuration parameter DISABLE_STRICT_REQUEST_VERIFICATION - has been introduced to control the new behavior. Define this parameter with the value 'Y' to retain the previous behavior. Limitations: This fix impacts some tools integrating with Quality Center such as Version Control Add-ins and Quality Center Dashboard. See the following details on compatibility issues. Issues after installing the patch: When installing Quality Center Dashboard or Version Control Add-in temporarily set the DISABLE_STRICT_REQUEST_VERIFICATION parameter to 'Y' for the duration of the installation. Problem: Quality Center Dashboard cannot communicate with the Quality Center server. Solution: Install Quality Center Dashboard patch 11 or higher. For a higher security level, change the default value of the shared communication key as follows: Quality Center - Quality Center Dashboard shared communication: In order for the Quality Center Dashboard server to communicate with the Quality Center server in a secure manner, a solution based on pre-sharing a key between the two servers has been added. The pre-shared key is configured in Quality Center in the file "WEB-INF\psk.properties" inside "sabin.war". Guidelines: This key should be kept confidential. We recommend that customers change the default value after the patch installation.

13

When changing the value in Quality Center, you should change it respectively in Quality Center Dashboard by adding the appropriate key in "WEB-INF\qcc_config.xml" inside "15qcc.war". Add the line: <PSK>the_new_value</PSK> in the <TdSiteAdmin> tag (e.g. under the <Proxy>light</Proxy> line).

Risk Analysis Report

Problem: This issue applies when generating a report in the Risk tab of the Requirements module. If Microsoft Word is open, the browser might stop operating. Solution: The problem is fixed.

Defects
Problem: Pasting text into the Description field of a defect might fail. Solution: The problem is fixed.

Imported Projects
Problem: When opening a defect in an imported project, slower performance is observed. Solution: The problem is fixed. Limitation: This fix applies for projects exported from Quality Center 9.2 with Patch 15 or later installed.

Excel Reports
Problem: When the values in a field begin with special characters, an error message is displayed when running an Excel report. Solution: The problem is fixed.

Test Plan
Problem: After editing a design step where the contents of the edited field extend beyond the visible window, a different step is highlighted in the Design Steps tab. Solution: The problem is fixed.

Replace All
Problem: When clearing the "From Beginning" option in the "Find/Replace" dialog box, all values are replaced. Solution: The problem is fixed. Limitation:

In Test Set in Replace popup, when From Beginning box is unchecked, after pressing Find Next - the next found value will be the one before the current and not the one after the current in a specific situation - when the highlighted test is placed right after one with the searched value.

14

Document Generator
Problem: When generating a document for defects using the Tabular Layout option, if the Release or Cycle fields are chosen, an error occurs. Solution: The problem is fixed.

Business Process Testing for SAP Applications

Problem: When modifying or adding new defects, an error occurs. Solution: The problem is fixed.

Requirements Module
Problem: When importing a document into rich text, previous content is not overwritten. Solution: The problem is fixed.

Quality Center 9.20 Patch 14

Fixed Defects
Customization
Problem: When a user-defined field is removed, changes in the 'Script Generator - List Customization' dialog box might cause an error. Solution: The problem is fixed. Problem: When non-TDAdmin group users attempt to change their password, it does not allow them. Solution: The problem is fixed.

Test Plan
Problem: When a VuGen test type is displayed, it contains a question mark test icon. Solution: The problem is fixed. Problem: When editing a design step that includes a call to another test, changes to the Description field of the test might not be saved. Solution: The problem is fixed.

15

Lists
Problem: When entering a value in a list field that does not follow the transition rule set for the field, the value remains but the user cannot continue to work. Solution: The problem is fixed.

Test Lab
Problem: The Replace feature is unavailable in the Execution Grid. Solution: The problem is fixed.

Windows Vista SP1 Support

Improved Vista support has been introduced in Patch 14 that enables users who are not Windows Vista Administrator users to work in Quality Center. Limitations: The following limitation exists for any Vista user: 1. Remote Test Execution. Remote test execution is not working when the QC client is running on Vista. The following limitations exist for users that are not Windows Vista Administrator users: 1. Microsoft Office. This limitation applies when working with a version other than Office 2007. When using the Microsoft Word or Excel Add-ins, it is not possible to export user-defined fields that are defined for the Undefined requirement type. 2. Microsoft Office. Mappings in Excel Add-in cant be saved if the user is logged in as a Standard User. 3. Version Control. When working with a Version Control Add-in, the Undo Checkout and Check In buttons in the Version History dialog box do not display correctly. 4. Document Generator. Document Generators status bar does not show. Installing the Quality Center Client on a Windows Vista SP1 Machine:

1. The Microsoft .Net Framework 3.5 must be installed on the Quality Center client machine prior to Quality Center 9.2 client installation. 2. Microsofts capicom version 2.1.0.2 (or later) should be installed prior to QC client installation. 3. Quality Center 9.2 Client Side installation: a. Log in to the PC as an Administrator user. b. From the Quality Center Add-ins page, select HP Quality Center Client Side Setup. Save the QCClient.msi file to a temporary folder. c. Run a Command Prompt (CMD.exe) with administrator privileges. i. Click StartPrograms, and right-click Command Prompt. Choose Run as Administrator. Provide credentials if needed, or click Continue if no credentials are needed. d. Run QCClient.msi from the command prompt. e. Follow the Quality Center 9.2 installation wizard instructions. 2. Quality Center 9.2 Internet Explorer installation: a. Administrator user: Navigate to the Quality Center Server URL. Quality Center will be downloaded and installed automatically.
16

3. Quality Center Explorer installation: a. Log in to the PC as an Administrator user. b. From the Quality Center Add-ins page, select Quality Center Explorer Add-in. Save the QCExplorerAddIn.exe file to a temporary folder. c. Run a Command Prompt (CMD.exe) with administrator privileges. i. Click StartPrograms, and right-click Command Prompt. Choose Run as Administrator. Provide credentials if required, or click Continue if no credentials are required. d. Switch DEP off: i. On the command line, type: bcdedit /set {current} nx AlwaysOff. ii. Restart the machine. e. Log in to the PC as an Administrator user. f. Run a Command Prompt (CMD.exe) with administrator privileges. g. Verify that DEP is switched off by running from the command line: bcdedit, and verifying that the nx property is set to AlwaysOff. h. In the Command Prompt run with administrator privileges, navigate to the folder where QCExplorerAddIn.exe is located, and run the file. i. Follow installation instructions. 4. To run Quality Center 9.2: a. Administrator user: i. Internet Explorer: Navigate to the Quality Center Server URL. ii. QCExplorer: Run QCExplorer. Navigate to the Quality Center Server URL. b. Standard user: i. DEP must be completely switched off. Refer to (4)d for instructions on verifying DEP status. ii. Run QCExplorer. iii. In QCExplorer: Navigate to the Quality Center Server URL.

Limitations
Problem: When a defect's field is required by workflow but a value was not entered, using the Replace All feature displays a dialog box asking to fill in the missing value. If the user clicks 'Cancel an error occurs. This problem will be solved in later patches and/or versions. Workaround: Do not click the Cancel button but rather fill in the required values. Problem: If you have HP Enterprise Integration 2.0 module for SAP applications extension installed, it is impossible to open new or update existing defects in the Defects module in projects where Enterprise Integration 2.0 extension is enabled. Problem: When using import to override rich text contents in requirements, the changes are not saved. This defect will be solved in QC92 Patch 15.

17

Quality Center 9.20 Patch 13

Enhancements
OTA
Enhancement: Client certificates for SSL are fully supported by Quality Center running in Quality Center Explorer, in Internet Explorer, and when Quality Center OTA is used from non-Quality Center code. Note: There is a change in functionality when working with a Client certificate. Remote automated tests cannot be executed in unattended mode. This is because when first connecting to the Quality Center server, a dialog box is displayed requiring the user to select a certificate.

Fixed Defects
Licenses
Problem: In the Site Administration Licenses tab, licenses may be listed as In Use even though the connection has been closed. Solution: The problem is fixed.

Requirements Module
Problem: In the Requirements Grid view, the Delete button is active for users that do not have Delete Requirement permissions. Solution: The problem is fixed.

Customization
Problem: When input masks are defined for user-defined fields, the Replace or Replace All commands might not function properly. Solution: The problem is fixed. Limitation: Search on a masked field before updating a value in it fails. In order to search for empty value you need to open the search dialog.

18

Problem: After setting the Description field as required for requirement data, it is not displayed as a required field in the Requirements module. Solution: The problem is fixed.

Cancel Changes
Problem: If Workflow Customization is used to set defect or requirement details and the user does not enter values in all required fields, a dialog box displays all the required fields that need to be input. If the user selects 'Cancel All Changes', the workflow settings are overwritten. Solution: The problem is fixed.

Printing
Problem: Internet Explorer 7. When working with the Quality Center client and Internet Explorer 7, selecting the option to print all pages from Internet Explorer prints only the current page. Solution: The problem is fixed.

Test Lab
Problem: When the status of some of a tests steps are set to 'N/A' and some are set to 'Passed' during test execution, the overall status is set to "Not Completed." Solution: The problem is fixed. Problem: When editing or adding steps during test execution, an error message is displayed. Solution: The problem is fixed.

Site Administration
Problem: When using the REPLACE_TITLE configuration parameter to change the names of entities, the renamed entity might not be referenced correctly. For example, after replacing the name of the Test Lab module, when opening Linked Defects from the Test Plan module an error might be displayed. Solution: The problem is fixed. Problem: If the parameter SHOW_REPOSITORY_OVER_DB is set to N or is removed when a project is upgraded, the message "Do you want to store Repository in DB?" is displayed. Solution: The problem is fixed.

User Interface
Problem: When scrolling on a list in a Grid view, the Internet Explorer might crash. Solution: The problem is fixed.

Mail
Problem: Links in mailed defects cannot be opened if the Quality Center client was installed by client-side installation. Solution: The problem is fixed.

19

Log
Problem: A "Session authenticity broken" message may not explain what the server response was. Solution: The problem is fixed. Note: The "Session authenticity broken" message provides details of the invalid server response.

Documentation
Problem: In the Custom Test Type Guide, the Registering Custom Test Types with Quality Center topic was not updated. Solution: The issue is fixed. You can access the updated help file in Quality Center from the Help menu by selecting Help > Documentation Library > HP Quality Center Custom Test Type Guide.

Quality Center 9.20 Patch 12

Fixed Defects
Business Process Testing for SAP Applications
Problem: If an application entity is associated with a test or component, an exception causes the Quality Center client to close. Solution: The problem is fixed.

Server Security
Problem: 'DBListFiles' allows users to browse files of projects to which they do not have permissions. Solution: The problem is fixed. Problem: AddSiteUsers allows a user that does not have the proper permissions to add users to the site. Solution: The problem is fixed.

OTA
Problem: The IAlertable interface has changed and cannot be used by external applications. Solution: The problem is fixed.

Customization
Problem: Quality Center does not always require users to fill in fields that are checked as 'Required.' Solution: The problem is fixed. Problem: Changes made to Description and 'Comments' field labels might not be displayed correctly. Solution: The problem is fixed.
20

Problem: When field labels have been changed for Release module fields, the history data is not saved correctly. Solution: The problem is fixed. Limitations: Note that the problem is fixed for new projects only. For existing projects affected by this defect, such as those in which the customization was modified for one of the Detected in Cycle, Detected in Release, Target Cycle, or Target Release fields, history data for these fields will continue to be stored incorrectly. Workaround: To fix the problem for existing projects, the user needs to upgrade the project or do the following: 1. Run the following SQL statements: UPDATE SYSTEM_FIELD SET SF_REFERENCE_TABLE = 'RELEASES', SF_REFERENCE_NAME_COLUMN = 'REL_NAME' WHERE SF_COLUMN_NAME = 'BG_DETECTED_IN_REL' UPDATE SYSTEM_FIELD SET SF_REFERENCE_TABLE = 'RELEASE_CYCLES', SF_REFERENCE_NAME_COLUMN = 'RCYC_NAME' WHERE SF_COLUMN_NAME = 'BG_DETECTED_IN_RCYC' UPDATE SYSTEM_FIELD SET SF_REFERENCE_TABLE = 'RELEASES', SF_REFERENCE_NAME_COLUMN = 'REL_NAME' WHERE SF_COLUMN_NAME = 'BG_TARGET_REL' UPDATE SYSTEM_FIELD SET SF_REFERENCE_TABLE = 'RELEASE_CYCLES', SF_REFERENCE_NAME_COLUMN = 'RCYC_NAME' WHERE SF_COLUMN_NAME = 'BG_TARGET_RCYC' 2. Recreate the triggers: Log in to the project In Project Customization, clear the History check box for the affected fields. Save the changes. Select the History check box for the affected fields and then save the changes again.

Test Plan, Test Lab - Replace

Problem: In the Test Plan and Test Lab modules, the Replace command is displayed in the Edit menu where it should not be available. Solution: The problem is fixed. The following changes were made: In the Test Plan module, visibility of the 'Replace' command depends on the current view. In the Test Lab module, the 'Replace' command was removed.

Excel
Problem: Exporting Quality Center data into Excel does not include formatting. Solution: The problem is fixed.

Site Administration
Problem: The AUTO_LOGOUT_ON_SERVER_DISCONNECT parameter might cause Quality Center Explorer to close instead of logging out. Solution: The problem is fixed.

Security
Problem: Detailed stack traces are displayed in error messages and in the client log.
21

Solution: The problem is fixed. A new parameter BLOCK_VERBOSE_ERROR_MESSAGES is added to the PARAMS table in the SA schema. The parameter is Boolean and has two values: Y and N while the default value is N. If this parameter is set to "Y" verbose error messages and the Java stack traces are blocked - only an indication that an error has occurred and the error code is sent. If this parameter is set to N or does not exist, detailed stack traces are not blocked.

Test Lab
Problem: After deleting tests from a test set, a copy/paste operation of the test set does not include the execution flow. Solution: The problem is fixed. Problem: Opening test runs generates a List index out of bounds error. Solution: The problem is fixed.

Quality Center 9.20 Patch 11

Enhancements
Project Repository
Tool for migrating the Project Repository from the Database to the File System
New functionality was added to Quality Center Site Administration. It enables the migration of a Quality Center project repository stored in the database to be stored on the file system. The new feature can be employed on a single project or on a domain. The feature is enabled only for projects whose repository is currently stored in the database. When employed on a domain, only projects whose repositories are in the database are affected. When employing the new feature, the repository is copied from the database to the file system, leaving the original repository in the database. The Quality Center Database Administrator can then delete the repository from the database. Before You Start: 1. 2. Back up the project. Make sure you have enough disk space in the project directory to store the entire project repository. The disk space needed is approximately the same amount required by the projects scheme. The new features user interface will report the exact required disk space later in the process. Make sure the project directory is empty. Deactivate the project. While running the tool, the log level should be set to Flow. On a UNIX machine, make sure to set locale and restart the server, or files will not be copied.

3. 4.

5. 6.

22

7.

Disable antivirus scanning, enlarge JBoss heap size to 1.5 GB, and try to avoid Windows 2000 if possible, especially when working on large projects.

To Migrate a Database Repository for a Project:

1. 2. 3. 4.

In Site Administration, click the Site Projects tab, and select the project whose repository you want to migrate. Click on the newly added Copy Database Repository To File System button. The system calculates the database size. This might take a few minutes. A dialog box opens and displays how much disk space is needed for this operation. Click OK to continue. After the process completes, the data in the REPOSITORY table in the projects scheme is no longer used or needed, and can be deleted to save database disk space. You can use the following SQL in order to delete the repository table content: TRUNCATE TABLE Project_scheme.REPOSITORY

To Migrate Database Repositories for all Projects in a Domain:

1. 2.
3. 4.

5. 6.

In Site Administration, click the Site Projects tab and select the domain whose projects repositories you want to migrate. Click on the newly added Copy Database Repository To File System button. The system then calculates the database size. This might take a few minutes. A dialog box opens displaying a list of projects in the selected domain whose repository is in the database. Repository sizes and the total size are also listed. In this dialog box, you can select the projects whose database repositories you want to migrate. Click OK. Quality Center iterates through the selected projects and applies the repository migration process sequentially, and informs you when the process is complete. After the process completes, the data in the REPOSITORY tables in the projects schemes is no longer used or needed, and can be deleted to save database disk space. You can use the following SQL for this on each of the projects schemes in order to delete the repository table content: TRUNCATE TABLE Project_scheme.REPOSITORY

Note: If the process aborts in the middle of migrating a project repository, you must delete the content of the directory of the partially migrated project before reactivating the process, except for dbid.xml.

Related OTA API: In addition to this new feature in the Site Administration User Interface, a matching API was added. You can use the following API to migrate the repository of a project. Make sure you deactivate the project first, and verify that there is enough disk space. Public Function MoveRepositoryToFS ( _ ByVal DomainName As String, _ ByVal ProjectName As String _ )

23

Following is a code sample for using this method:

Private Sub MigrateProjectsRepository() 'The following Visual Basic example migrates a projects ' repository from the DB to the File System. Dim sDomainName As String Dim sProjectName As String On Error GoTo err sDomainName = "MyDomain" sProjectName = "MyProject" ' Deactivate the project Call m_SAClient.DeactivateProject _ (sDomainName, sProjectName) ' Migrate the projects repository Call m_SAClient.MoveRepositoryToFS _ (sDomainName, sProjectName) ' Reactivate the project Call m_SAClient.ActivateProject _ (sDomainName, sProjectName) Exit Sub err: MsgBox "Program failed:" + err.Description End Sub

Fixed Defects
Log
Problem: Log files might include multiple false warnings, taking up unnecessary disk space. Solution: The problem is fixed.

Test Plan - Filter

Problem: When applying a filter in the Test Plan, using the '^' character in the Path column might cause the server to stop responding. Solution: The problem is fixed.

24

OTA
Problem: Using multiple Connect() followed by Disconnect() might cause a memory leak. Solution: The problem is fixed. Problem: A member of the TDAdmin group who is not assigned the Change User Properties and Password permission can change the password of other users. Solution: The problem is fixed.

OTA Business Process Testing

Problem: When the TSScheduler's 'Run' method is called it might invoke only one iteration of a BPT test. Solution: The problem is fixed.

Quality Center Checker

Problem: After installing a patch, the 'params.properties' file is overwritten. Solution: The problem is fixed.

Client Side
Problem: After logging in, the file Test_Type.ini gets overwritten. Solution: The problem is fixed.

Site Administration
Problem: Users can create a domain called Templates. Solution: The problem is fixed. The name Templates is reserved for system use and cannot be used. Problem: The method 'AddSiteUser' works even if the flag ADD_NEW_USERS_FROM_PROJECT is set to 'N'. Solution: The problem is fixed.

Workflow
Problem: The IsVisible property in 'Test_MoveTo' event works only the first time the event is triggered. Solution: The problem is fixed.

Defects
Problem: Microsoft Excel. Field data exported to Excel that is longer then 255 characters is truncated. Solution: The problem is fixed.

Mail
Problem: Microsoft Excel. When mailing a defect with an Excel attachment, the name of the attachment might get truncated if it contains special non-English language characters. Solution: The problem is fixed.

25

Service Test Management

Problem: When Service Test Management is installed, the DB_TEST test type is not available when creating a new test in the Test Plan. Solution: The problem is fixed.

WebLogic
Problem: Weblogic 9.2.2 is not supported. Solution: The problem is fixed. Weblogic 9.2.2 is now supported.

BPT for SAP

Enhancement: New field Promoted From appears for a BP Test Runtime parameters. Limitation: The field is read only and used to display data. It is only effective when BPT for SAP 2.50 extension is used. For standard BPT users it does not provide added-value functionality

Quality Center 9.20 Patch 10

Enhancements
OTA
Users can now add custom audit events using AuditRecordFactory (which can be obtained through a TdConnection). This supports a new API: IAuditRecordAdder. Through IAuditRecordAdder, it is possible to call an API function AddAuditRecord( AuditRecordData ) The AuditRecordData object has 4 set/get methods, used to set the following attributes: Action, EntityId, EntityType, Description. To insert custom audit events into the AUDIT_LOG table, the user can create an AuditRecordData, set its properties to the desired information, and call the AddAuditRecord function with the previously created AuditRecordData object. In order for the AddAuditRecord to succeed, the Action property must start with the prefix "CA_". The Description attribute can be used to store any user-specific information. For example: // assuming 'conn' holds a valid TdConnection: IAuditRecordData auditRecData = new AuditRecordData(); auditRecData.Action = "CA_Sign_Document"; auditRecData.EntityId = getEntityId();
26

auditRecData..EntityType = getEntityType(); auditRecData.Description = getSignature(); IAuditRecAdder auditRecAdder = (IAuditRecordAdder) conn.AuditRecordFactory; auditRecAdder.AddAuditRecord( auditRecData );

Customization
A new site administrator parameter is added: DISABLE_EMAIL_CHANGE_BY_ADMIN. If the parameter is set to Y, the project administrator cannot change users e-mail addresses.

Login
In the Login window, a progress bar displays the progress of the Login process.

Fixed Defects
Customization
Problem: When Defects module is renamed using REPLACE_TITLE, selecting a linked defect from the Test Plan grid generates an error. Solution: The problem is fixed.

Workflow
Problem: field ST_RUN_ID used in Step_Fields object does not return the correct ID. Solution: The problem is fixed. Problem: When ViewOrder is used in the Test Plan module, when the module is first entered, the system fields are not sorted as expected for tests that are version controlled. Solution: The problem is fixed. Problem: In upgraded projects, there is no alert if users try to override existing Project_ functions, with the new functions, 'CanLogin', 'CanLogout', 'CanCustomize' or 'DefaultRes'. Solution: When a user tries to override existing functions, a warning message opens.
.

27

Quality Center 9.20 Patch 9

Workflow
Problem: Actions.Action("act_refresh").execute in Bug_move can cause data corruption. Solution: The problem is fixed. Problem: It is not possible to add an Alert to a requirement using OTAs AddAlert method. Solution: The problem is fixed.

LDAP
Problem: When importing LDAP users the error: "unsupported critical extension" shows. Solution: The problem is fixed. Limitation: Only LDAP V3 can be used.

QTP
Problem: When pressing the "Run" Button in test lab to run a QTP test and the QTP add-in for QC is not installed, the user gets an exception error. Solution: The problem is fixed.

Graphs
Problem: Selecting a favorite for a cross testset summary graph fails if a test set folder is selected and not a test set. Solution: The problem is fixed.

Requirement
Problem: When deleting several requirements in grid view, the error: "Failed to Delete requirement." might show. Solution: The problem is fixed.

Excel Add-In
Problem: Path column is not imported when importing Requirements from Excel Add-In. Solution: The problem is fixed. You must download and install the latest Microsoft Excel Add-in from the Quality Center Add-ins page

28

Quality Center 9.20 Patch 8

Releases Module
Problem: When viewing the Outstanding Defects graph for a release, the outstanding defects of other releases are included in the graph. Solution: The problem is fixed. The Only Targeted Defects option was added to the Configure Outstanding Defects dialog box.

Security
Problem: The Extended Storage API might not be secured when accessing the Quality Center server file system. Solution: The problem is fixed.

Test Lab
Problem: In the Find/Replace dialog box, clicking Replace All to change the status of tests in a test set changes the status but does not create a new run. Solution: The problem is fixed.

Workflow General
Problem: Using the TDFilter API to edit a filter in the Workflow code does not work. Solution: The problem is fixed.

Workflow Test Plan

Problem: The ViewOrder property does not work the first time a user logs in. Solution: The problem is fixed. Limitation: The problem is fixed for projects that do not have version control enabled.

Attachments - Mail
Problem: Microsoft Outlook 2003 SP3. When working on a Quality Center client machine with Outlook 2003 SP3 installed, mail attachments cannot be opened. Solution: The problem is fixed.

Reports - Requirements
Problem: When customizing reports in the Requirements Module, the Keep Parent-Child Order option does not work. Solution: The problem is fixed.

Customization - Fields
Problem: When creating and deleting multiple user-defined fields, the changes cannot be saved. Solution: The problem is fixed.
29

BPT
Problem: If the run time of a BPT component is higher than the value of the WAIT_BEFORE_DISCONNECT_TIME parameter, the rest of the components in the test are not executed. Solution: The problem is fixed.

Excel Add-In
Problem: The Microsoft Excel Add-in does not support Quality Center requirement types. Solution: The problem is fixed. You must download and install the latest Microsoft Excel Add-in from the Quality Center Add-ins page.

Quality Center 9.20 Patch 7

Exporting Grid Data
Problem: Microsoft Office 2007. This problem occurs when exporting grid data to Excel or Word from a client machine on which Microsoft Office 2007 is installed. The files are saved in Office 2007 format and cannot be opened by earlier Office versions. Solution: The problem is fixed. The files are now saved in the format of the earlier version.

Security
Problem: When logging in to Quality Center, the server sends project customization data to the client, including all the project user passwords. Solution: The problem is fixed. The user passwords are no longer sent to the client. Problem: Workflow scripts are not secured. Solution: The problem is fixed.

Site Administration Copy Project

Problem: This problem occurs when creating a project by copying data from an existing project. The copy operation fails to copy attachments from the Releases module. Solution: The problem is partially fixed. To copy Releases module attachments, you must choose to copy all available customization categories.

Quality Center Checker

Problem: When Quality Center Checker is run for the first time it cannot identify the database version. Solution: The problem is fixed. Problem: Visual Basic Scripting Edition (VBScript). Quality Center Checker fails to run VBS scripts. Solution: The problem is fixed.

30

Test Lab
Problem: This problem occurs when working in the Test Lab Module Execution Grid. When the test status is changed manually, the update may cause the creation of multiple runs. Solution: The problem is fixed.

Languages
Problem: It is not possible to edit memo fields for Thai language content. Solution: The problem is fixed. Limitations: The following limitations are still affective: - It's impossible to create QC project in Site Administrator with Thai chars in name. - Thai chars are corrupted in all QC Graphs and Site Analysis graph. - Error 'System does not support the specified encoding.' appears when creating Report in QC. - Thai chars are corrupted in VAPI-XP script. - When copying a Thai String field value from Details form and pasting into Memo field it is pasted corrupted but after Refresh it is updated correctly. - QC client shows incorrect dates on Thai machines

Customization
Problem: When the ENABLE_RUN_HISTORY_CUSTOMIZATION configuration parameter is added in Site Administration, history is still not enabled. Solution: The problem is fixed.

Components
Problem: This problem occurs when the user clicks New Component Request from the Test Plan module, but cancels before completing the wizard. If the user has 'add' but not 'delete' permissions, an error message is displayed and the components are reordered. Solution: The problem is fixed.

31

Quality Center 9.20 Patch 6

Test Lab Module

Problem: When copying and pasting test sets, a failed to get test data error might occur. Solution: The problem is fixed.

Requirements
Problem: This problem occurs when cutting or copying requirements. When pasting the requirements using the right-click menu, the requirements are pasted without folder IDs. Solution: The problem is fixed

Reports
Problem: After clicking the Print or Save All Pages button, the browser hangs. Solution: The problem is fixed.

Workflow
Problem: Test_Fields("TS_NAME").Value can be called only once from Test_New event. Subsequent calls are ignored Solution: The problem is fixed. Problem: In Defect Details dialog box, clicking the Add Comment button does not trigger any action. Solution: The problem is fixed. The action name is called 'AddDevComment'. Limitation: The add Comment has been expanded in QC9.2 to include Test Plan and Requirements as well. Therefore the name BugAddDevCommentsAction1 cannot be used in Defect Details dialog. 'AddDevComment' is used for add comments in Defect Details dialog, but 'BugAddDevCommentsAction1' is still used for add comments in Defects Grid.

Security
Problem: A possible security breach in the SetProjectCustomizationData method. Solution: The problem is fixed.

32

Quality Center 9.20 Patch 5

BPT
Problem: In the Test Plan module, it is not possible to drag and drop BPT test types. Solution: The problem is fixed. Problem: When trying to view Last Run Results for a BPT test that contains a group of several components, and the last component has no parameters, an error message is displayed. Solution: The problem is fixed Problem: When BPT test cases include many components and each component includes numerous iterations, memory leakage will occur. Solution: The problem is fixed.

Document Generator
Problem: When generating a document that includes test plan data, there might be extra space between the test step table and the preceding test details. Solution: The problem is fixed Problem: In the Logo tab, it is not possible to save a picture. Solution: The problem is fixed

Test Plan
Problem: The Generate Script button for QuickTest Professional is disabled . Solution: The problem is fixed

Defects, data hiding

Problem: When two or more data-hiding filters are applied to a user group, and the member of that group attempts to view the defects history, an error is displayed. Solution: The problem is fixed

Workflow
Problem: The moveTo event is not called when the user clicks OK or Cancel in the Defect Details dialog box. Solution: The problem is fixed

33

Security
Problem: Session keys could be compromised. Solution: The problem is fixed. Secure session keys are now used. Limitations: This fix required a change in the network protocol. For legacy interoperability reasons the old protocol is still supported and the secure mode is not enforced by default (This allows customers who are not concerned by this issue to keep using existing LoadRunner scripts for load testing Quality Center for example). In order to activate the new mode, in Site Administrator create a Site Configuration Parameter named "FORCE_KEY_AUTHENTICATION" and set it's value to Y.

Quality Center 9.20 Patch 4

General
Problem: Microsoft Windows Vista on a client machine is not supported. Solution: The problem is fixed. Limitations: To run Quality Center on a Microsoft Windows Vista client machine, only Quality Center Explorer is supported. When running a system test with the Collect System Information option selected, the test fails and an error message is displayed. Before connecting to a Quality Center server, the HP Quality Center Client Side Setup Add-in should be installed. When opening a defect from 'QC Package for VS' or from 'QTP Test Run Reports' and the user is trying to attach "All topic" from systeminfo an error message appears Notes for running the HP Quality Center Client Side Setup Add-in on Vista: During installation of the add-in, in the Setup Type page where the installation folder is selected, the Everyone option must be selected. Before running the add-in on the client machine, you must set the client machine Local Security Policy. You need to disable the Run All Administrators in Admin Approval Mode option. When installing the Quality Center Package for Microsoft Visual Studio Add-in on the client, the installation fails. A temporary work around is to install HP Quality Center Client Side Setup Add-in in the following location: <drive>\Program Files\Common Files\, and not in the default location <drive>\Program Files\HP\. Problem: Quality Center does not support an Oracle 10.2.0.3 database. Solution: The problem is fixed. Problem: Quality Center does not support IT Governance (ITG) integration. Solution: The problem is fixed. Problem: When using the HP Quality Center Client Side Setup, the spell checker does not work. Solution: The problem is fixed. Problem: When Client side installation is installed not in the default location BPT doesn't work. Solution: The problem is fixed.

34

Test Parameters
Problem: WinRunner test. When editing a WinRunner test that has both manual and automated parameters, values in one parameter might overwrite those of another. Solution: The problem is fixed.

Graphs
Problem: When displaying graphs in Requirements Analysis, the horizontal scroll bar is not fully visible. Solution: The problem is fixed.

Workflow
Problem: When the user clicks Cancel in the Defect Details dialog box, the changes performed by the workflow code of the Defects module might also be canceled. Solution: The problem is fixed.

Advanced Filter
Problem: Oracle 10.2.0.1 or Oracle 10.2.0.2. The use of advanced filters returns incorrect information. Solution: The problem is fixed.

Site Analysis
Problem: Site Analysis might show an incorrect number of peak users. Solution: The problem is fixed.

Quality Center 9.20 Patch 3

Requirement Module - Rich Text
Problem: When you expand the Rich Text tab, Internet Explorer stops responding. Solution: The problem is fixed Problem: When you save rich text using the Save button in Microsoft Word, an error message displays. Solution: The problem is fixed Problem: In some situations, it is not possible to update the Rich Text tab. Solution: The problem is fixed Problem: You cannot load a Word document into the Rich Text tab more than once. Solution: The problem is fixed

35

Limitation: For a new project, for the first project requirement, you might not be able to see the content of the Rich Text field after loading a document into it. Clicking the browser Refresh button solves the problem Problem: Editing rich text is not supported in client machines on which Microsoft Office 2007 is installed. Solution: The problem is fixed.

Analysis
Problem: A document generated by the Document Generator on a client machine on which Microsoft Office 2007 is installed cannot be opened by Office 2003 or earlier versions. Solution: The problem is fixed.

Graphs Test Lab Module

Problem: When the X-axis for a graph is set to display test sets and the Show full path check box is selected, the numbers in the graph are incorrect. Solution: The problem is fixed.

Workflow Test Lab Module

Problem: There is no event triggered when the Assign To Cycle dialog box opens. Solution: The problem is fixed. A new action ActAssignToCycle is triggered before the Assign To Cycle dialog box opens for a test set folder.

Quality Center 9.20 Patch 2

General
Problem: Microsoft Office 2007 on client machine is not supported. Solution: The problem is fixed. Limitation: Edit operation on a Rich Text field is not supported in client machines on which Microsoft Office 2007 is installed. Problem: In all modules, the user interface is cut off at the bottom of the screen. Solution: The problem is fixed. Problem: Quality Center does not support a Microsoft SQL 2005 SP2 database. Solution: The problem is fixed. Problem: Quality Center server is not supported when installed on Microsoft Windows 2003 SP2 machine. Solution: The problem is fixed.

36

Site Administration
Problem: Passwords with Japanese characters are set incorrectly in Site Administration. Solution: The problem is fixed. No functional changes. Problem: Unable to log in to Site Administration if the site administrator password contains Japanese with MB characters. Solution: The problem is fixed. No functional changes. Problem: The REPLACE_TITLE Site Configuration parameter does not work in the Business Components module. Solution: The problem is fixed. No functional changes.

Client-side
Problem: After downloading several Quality Center components in a WAN environment, the downloading process stops. Solution: The problem is fixed. Added a resume mechanism for downloading files. If an internet connection problem occurs, the downloading process resumes after refreshing or reopening the browser. Problem: When closing a Quality Center client by clicking the Close button (X) in the Internet Explorer window, runtime errors might occur. Solution: The problem is fixed. No functional changes.

Releases Module
Problem: The Requirements assigned to release and Requirements assigned to cycle links do not work properly. Solution: The problem is fixed. No functional changes.

Requirements Module
Problem: An access violation error might occur when moving a lower node requirement to a higher node requirement in the requirements tree. Solution: The problem is fixed. No functional changes. Problem: An access violation error might occur when closing a combo box without selecting a value. Solution: The problem is fixed. No functional changes. Problem: This problem occurs after modifying a rich text document. When the user attempts to create or open another document, a warning message does not always display. Solution: The problem is fixed. No functional changes. Problem: When creating a new requirement and importing a Word doc into the Rich Text tab, Failed To create Attachment error appears. Solution: The problem is fixed. No functional changes. Problem: An error occurs when closing the New Requirement dialog box without typing the requirement name. Solution: The problem is fixed. No functional changes.

37

Problem: This problem occurs in requirements assigned to user-defined requirement types. After upgrading a project from Quality Center 8.2 to 9.2, the requirements Name field is no longer defined as a required field. Additionally, in Project Customization, you cannot set this field to be required. Solution: The problem is fixed. When working with user-defined requirement types, the requirements name is set to be required. Problem: In the Risk tab, after clicking the Cancel button in the Generate Report dialog box, the Quality Center window is minimized. Solution: The problem is fixed. No functional changes. Problem: In the Risk tab, after selecting the Override calculated value check box, the selection gets cleared. You must reselect this option. Solution: The problem is fixed. No functional changes. Problem: This problem occurs when defining the testing policy for an analysis requirement and applying it to its assessment requirements (Save and Apply to Children button) in the Risk tab. Assessment requirements set to testing level 3 are displayed as 3-Sanity instead of 3-Basic. In addition, when filtering on the RBQM Testing Level field, the testing level is listed as 3-Basic. Solution: The problem is fixed. Limitations: To correct previously defined testing policies, the database must be updated (run the next SQL statement on every project with defined testing policy: MSSql: update td.req set rq_rbt_testing_level='3-Basic' where rq_rbt_testing_level='3-Sanity' Oracle: update req set rq_rbt_testing_level='3-Basic' where rq_rbt_testing_level='3-Sanity'). Alternatively, if you are not updating the database, set the filter condition for the RBQM Testing Level field to "3Sanity Or 3-Basic". Problem: When generating a risk-based testing report, the testing levels are not displayed in the Implemented testing policy table. Solution: The problem is fixed. No functional changes. Problem: In the Risk tab, after clicking the Save and Apply to Children button, the RBT Date of Last Analysis field is incorrectly updated. Solution: The problem is fixed. No functional changes.

Test Lab Module

Problem: This problem occurs in the Manual Runner when pressing Ctrl + A to select memo text. The status of all the steps changes to Pass. Solution: The problem is fixed. The shortcut for setting steps status was changed to Ctrl + Alt + A. Problem: This problem occurs when attempting to assign a test set subfolder to a cycle that is different than the cycle the parent test set folder is assigned to. This action prompts an error message that indicates that the specified cycle is not valid for this folder. After closing this message box, it may cause Quality Center to stop responding. Solution: The problem is fixed.

Customization
Problem: Module access definitions for the Business Components module are overridden during project upgrade. Solution: The problem is fixed. No functional changes. Problem: This problem occurs after you enter data to the Risk-Based Quality Management page, and click the Return button to save the changes and return to your Quality Center project. If some of the data is invalid, all of the changes are lost.
38

Solution: The problem is fixed. When saving your changes, if the data is invalid, a prompt message opens before enabling you to return to your project. Problem: This problem occurs in Project Customization. An error occurs when closing Internet Explorer. Solution: The problem is fixed.

Document Generator
Problem: This problem occurs when generating a Business Components document. Snapshots and comments are not included in the report. Solution: The problem is fixed.

Workflow
Problem: This problem occurs when fields in a dialog box are set to be hidden. After closing the dialog box, the fields are also hidden in main view. Solution: Set IsVisible=True in the DialogBox event (dialog box is closed). The fields remain visible in the main view. Problem: Unable to customize tab names in the Requirement Details and New Requirement dialog boxes because the Requirements_GetDetailsPageName event is not supported. Solution: Added 2 new events to the workflow: GetReqDetailsPageName and GetNewReqPageName. You can use the GetReqDetailsPageName event to customize the tab names in the Requirement Details dialog box. You can use the GetNewReqPageName event to customize the tab names in the New Requirement dialog box. Note that the new events are not listed in the scripts tree of the Script Editor. Problem: This problem occurs when opening the New Defect dialog box from the Manual Runner. The Bug_FieldChange and Bug_FieldCanChange events are triggered before the Bug_New event. Solution: The problem is fixed. The Bug_New event is now triggered before Bug_FieldChange and Bug_FieldCanChange events.

Integrations
Problem: Connection cannot be made between QuickTest Professional and Quality Center. This problem occurs when working in UNIX or Linux environment. Solution: The problem is fixed.

Quality Center 9.20 Patch 1 Security

Problem: When opening Quality Center from a client machine, the last user login information is displayed in the Quality Center Login window. Solution: In Site Administration, add the DISPLAY_LAST_USER_INFO parameter to the Site Configuration tab. If this parameter does not exist or is set to Y, then the last user login information is saved on the client machine and is displayed in the Quality Center Login window. If this parameter is set to "N", the last user login information
39

is not saved on the client machine and is not displayed in the Quality Center Login window. Note that to activate this parameter, you must log in to Quality Center, log out, and log in again. Problem: After a user logs in to Quality Center, the server sends all project user names, passwords, and customization data to the client. Although passwords are encrypted, they still pose a security threat. Solution: The problem is fixed. Passwords are no longer sent from the server to the client. Problem: Using OTA API, a user is able to see audit history on items that are hidden by data-hiding filters. Solution: The problem is fixed. User will still be able to see information on when changes were made, but not which values or properties were changed.

Client-side
Problem: Quality Center client stops responding after the relevant user session is disconnected in Site Administration. Solution: The problem is fixed. No functional changes. Problem: This problem occurs after a client session is disconnected from a server (due to client inactivity, or session disconnection in Site Administration). The user is unaware of this disconnection because Quality Center appears to be logged in. Solution: In Site Administration, add the AUTO_LOGOUT_ON_SERVER_DISCONNECT parameter to the Site Configuration tab. If this parameter is set to "Y", then Quality Center logs out the client user and reopens the Quality Center Login window. If this parameter does not exist or is set to N, then the current behavior remains.

Releases Module
Problem: When clicking links in the Statistics pane for a selected cycle, Quality Center does not update the filters displayed in the Requirements and Test Lab modules. Solution: The problem is fixed. No functional changes.

Requirements Module
Problem: Unable to delete assessment values in the Risk tab by pressing the Delete key. Solution: The problem is fixed. No functional changes. Problem: When generating a test from a requirement in the Generate Test dialog box, an access violation error occurs if the Add Test to Test Set option is selected. Solution: The problem is fixed. No functional changes. Problem: When generating a report for a selected requirement, an error message is displayed. Solution: The problem is fixed. No functional changes. Problem: This problem occurs in the Linked Defects view of the Requirement Details or Defect Details dialog box. The online help does not open when clicking the Help icon (?). Solution: The problem is fixed. No functional changes. Problem: After clicking the Rich Text tab of a newly created requirement, an error occurs when logging out or closing the browser. Solution: The problem is fixed. No functional changes.

40

Problem: This problem occurs after filtering the requirements tree and clicking the missing assessment link in the Risk tab. The Drill Down Results dialog box ignores the applied filter settings. Solution: The problem is fixed. No functional changes. Problem: After clicking the Perform Risk Analysis button in the Risk tab, the excluded link shows an inaccurate count. Solution: The problem is fixed. No functional changes. Problem: After generating a report in the Risk tab, Quality Center does not allow saving over an existing file name. Solution: The problem is fixed. No functional changes. Problem: Performance problems occur when expanding branches in the requirements tree, or when opening and closing drop-down windows. Solution: The problem is fixed. No functional changes. Problem: When creating a new requirement, the Comments and Rich Text tabs are not displayed in the New Requirement dialog box. These tabs can be viewed after you submit the new requirement and close the dialog box. Solution: The problem is fixed. No functional changes. Problem: When client machine is running on Japanese operating system, gibberish appears on the Rich Text tab menu titles. Solution: The problem is fixed. No functional changes. Problem: When deleting items in the grid view and moving to the tree view the client stop responding. Solution: The problem is fixed. No functional changes. Problem: When there is a message box in Req_MoveTo event method of the module workflow and a user changes the requirement tree filter - Quality Center displays an Access violation error message. Solution: The problem is fixed. No functional changes.

Business Components Module

Problem: When a Quality Center project repository is stored on Oracle, the Quality Center client machine fails to open large size Business Components reports. Solution: The problem is fixed. No functional changes.

Test Plan Module

Problem: Unable to copy tests of a version-control enabled project. Solution: The problem is fixed. No functional changes. Problem: Unable to drag and drop a renamed test or folder. Solution: The problem is fixed. No functional changes.

Test Lab Module

Problem: When renaming a test set, unable to use the Delete key to delete the text of the old name. Solution: The problem is fixed. No functional changes.

41

Problem: Pressing CTRL+F keys invokes a Windows Explorer action instead of the Find dialog box. Solution: The problem is fixed. No functional changes. Problem: This problem occurs in the Manual Runner when modifying a test which is checked out by another user. When ending the test run, a message box does not indicate that the test cannot be modified because it is checked out to another user. Solution: The problem is fixed. No functional changes. Problem: The ViewOrder workflow property does not set the order in which the fields appear in the following views: Test Instance Properties dialog box and Details link in the Test Set Properties tab (in the Test Lab module), and Details tab (in the Test Plan module). Solution: The problem is fixed. No functional changes.

Defects Module
Problem: When customizing the Defects Summary graph, an error occurs when the following pairs are selected: Detected in Cycle and Target Cycle, or Detected in Release and Target Release. Solution: The problem is fixed. No functional changes. Problem: When grouping grid records in the Filter dialog box, an error occurs when the following fields are selected: Detected in Cycle and Target Cycle, or Detected in Release and Target Release. Solution: The problem is fixed. No functional changes.

Document Generator
Problem: Generating a document for both Business Components and Tests at the same time, causes Quality Center to stop responding. Solution: The problem is fixed. No functional changes. Problem: Unable to display rich text in Document Generator reports. Solution: The problem is fixed. No functional changes.

Excel Reports
Problem: When moving example reports from a public to a private folder, an error occurs. Solution: The problem is fixed. No functional changes. Problem: If you export rows of a grid to Excel and the system locale date format on the client machine is different than the user locale date format on the client machine, the date is incorrect. Solution: The problem is fixed. No functional changes.

Customization
Problem: The problem occurs when a user session is disconnected while in Project Customization. After being disconnected, the user can still click the Return button to go back to the Quality Center project and continue working. Solution: The problem is fixed. When this situation occurs, the Quality Center Login window now opens. Problem: To view the Risk-Based Quality Management link in the Project Customization window, the user must have permissions for the following tasks: Customize Requirement Types and Customize Risk-Based Quality
42

Management. Solution: The problem is fixed. No functional changes. Problem: Performance problem occurs when opening Users list dialogs content when there are many users defined in Site Administration. Solution: The problem is fixed. No functional changes.

Site Administration
Problem: When creating a new project by copying data from another project, risk-based quality management settings are not copied. Solution: A new option is added to the Create Project dialog box. To copy risk-based testing, select the Risk Based Quality Management option. Problem: This problem occurs when the Site Administration database schema is stored on Oracle. If you try to disconnect a user from the Site Connections tab and there are more than 1000 sessions, an error message displays. Solution: The problem is fixed. No functional changes.

General
Problem: When clicking the Paste button in the Filter dialog box and there is nothing to paste, an irrelevant error message is displayed. Solution: The problem is fixed. No functional changes. Problem: This problem occurs when a Quality Center client machine is using 800x600 screen resolution. The scroll bar is positioned at the bottom of the screen. Solution: The problem is fixed. No functional changes. Problem: When a user is deleted from a project, no other user can delete the users alerts. Solution: The problem is fixed. Anyone can delete alerts of a user that no longer exists in a project. Problem: When moving the mouse pointer over the Authenticate and Login buttons in the Quality Center Login window, the mouse pointer should change to a hand. Solution: The problem is fixed. No functional changes.

Installation Instructions
This patch is intended to be installed on top of HP Quality Center 9.2 only. To check the version you are using, select Help > About HP Quality Center Software.

Installing the Patch

This section describes how to install the patch on your server machine. Notes:

Microsofts capicom version 2.1.0.2 (or later) should be installed prior to QC client installation
43

Before installing the patch, make sure that all users log out of Quality Center. You can check active connections from Site Administration in the Site Connections tab. If you are using clustering for Quality Center, make sure you install the patch on all nodes of the cluster. If you are using WebLogic or WebSphere as the application server, you must undeploy qcbin.war and sabin.war before patch installation. After the patch is installed, the first time you log in to Quality Center, new files are downloaded and installed on your client machine. Note that you must log in to your machine with administrator privileges. If file downloads are prohibited through your browser, you can install these files from HP Quality Center Client Side Setup Add-in on the HP Quality Center Add-ins page, or contact HP Customer Support (http://support.openview.hp.com/) for assistance.

To install the patch: 1. On your Quality Center server machine, run the patch setup file that matches the server's platform.
Platform Windows Solaris or Linux To install: Run the setup.exe file. To install on a Solaris platform, in the command prompt, type: ./setupSolaris.bin To install on a Linux platform, in the command prompt, type: ./setupLinux.bin Note: Make sure that the DISPLAY environment variable is properly configured on the Quality Center host machine, or that it is in silent mode.

2. After installing the patch, deploy the Quality Center .war files on the Quality Center server machine.
If you are using JBoss as the application server, select Deploy files on JBoss to deploy the files automatically during the installation process. If you are not using JBoss, or you did not select Deploy files on JBoss, proceed with the instructions for deploying the files manually.

Deploying the Files Manually

To apply the patch changes, the Quality Center .war files must be redeployed. The following instructions describe how to manually deploy the .war files installed under the Application directory after installing the patch.

To deploy the files manually:

1. Stop the Quality Center service.

If you are using JBoss on Windows, stop Quality Center by right-clicking the system tray icon, and selecting Stop Quality Center. If you are using JBoss on a non-Windows machine, stop JBoss by running run.sh -stop from the console.

44

If you are using WebLogic or WebSphere, stop the server using the WebLogic or WebSphere Management Console.

2. Undeploy the qcbin application from the application server.

If you are using JBoss, move the <QC_home_directory>\jboss\server\default\deploy\20qcbin.war and 10sabin.war files to a different directory. Do not rename the files, and leave them in the existing directory as JBoss will try to redeploy them on startup. If you are using WebLogic or WebSphere, undeploy the qcbin and sabin applications using the WebLogic or WebSphere Management Console. Also copy the qcbin.war and sabin.war files to another directory.

3. Deploy the files to the application Server.

If you are using JBoss, copy the qcbin.war and sabin.war files from the application folder to the JBoss deployment folder (for example, ...\jboss\server\default\deploy). Rename the copied files to 20qcbin.war and 10sabin.war respectively. If you are using WebLogic, redeploy the qcbin.war and sabin.war applications using the WebLogic Management Console, and make sure that sabin.war loads first before qcbin.war. For more information, see the Mercury Knowledge Base Article 35712 (http://support.mercury.com/cgibin/portal/CSO/kbBrowse.jsp). If you are using WebSphere, redeploy the qcbin.war and sabin.war applications by following the instruction in the Mercury Knowledge Base Article 38493 (http://support.mercury.com/cgibin/portal/CSO/kbBrowse.jsp).

4. Start the Quality Center service.

Uninstalling the Patch

This section describes how to uninstall the patch from your server machine. Notes: If you are using clustering for Quality Center, make sure you uninstall the patch on all nodes of the cluster. If you are using WebLogic or WebSphere as the application server, undeploy qcbin.war and sabin.war before uninstalling the patch.

To uninstall the patch:

Run the uninstall program located in <QC_home_directory>\Patches\Quality Center 9.2 Patch6\_uninst\

To uninstall the patch manually:

Undeploy the qcbin.war and sabin.war files that came with the patch installation, and redeploy the old .war files that you moved to a different directory.

45

Support
Mercury Product Support
You can obtain support information for products formerly produced by Mercury as follows: If you work with an HP Software Services Integrator (SVI) partner (www.hp.com/managementsoftware/svi_partner_list), contact your SVI agent. If you have an active HP Software support contract, visit the HP Software Support site and use the Self-Solve Knowledge Search to find answers to technical questions. For the latest information about support processes and tools available for products formerly produced by Mercury, we encourage you to visit the HP Customer Support Web site at: http://support.openview.hp.com/. Contact your HP Sales Representative if you have additional questions.

HP Software Support
You can visit the HP Software Support Web site at: www.hp.com/managementsoftware/services HP Software online support provides an efficient way to access interactive technical support tools. As a valued support customer, you can benefit by using the support site to: Search for knowledge documents of interest Submit and track support cases and enhancement requests Download software patches Manage support contracts Look up HP support contacts Review information about available services Enter into discussions with other software customers Research and register for software training Most of the support areas require that you register as an HP Passport user and sign in. Many also require a support contract. To find more information about access levels, go to: www.hp.com/managementsoftware/access_level To register for an HP Passport ID, go to: www.managementsoftware.hp.com/passport-registration.html

Legal Notices
Copyright 1993 2009 Hewlett-Packard Development Company, L.P.

46

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice. Microsoft is a U.S registered trademark of Microsoft Corporation.

47