Quality Center 9.

0 GA - Patch# 16
==================================
Date: 15-June-2007
-------------------

I. Description of the issues addressed by this patch:

1. Problem description:
Test Plan. When converting manual tests to automated tests, an error
occurs.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

2. Problem description:
Requirements. When changing the Reviewed field in the requirements
tree, the change is not posted.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

3. Problem description:
Workflow - isRequired. When a field is not marked as a required
field and the workflow attempts to set it as a required field, an
error occurs.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

4. Problem description:
Graphs - Test Set. The test set progress graphs show incorrect
results.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

5. Problem description:
VAPI-XP. In some cases, when you click the Test Script tab, the
VAPI-XP scripts do not load.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

6. Problem description:
Manual Runner. Unable to link to existing defects in the Manual
Runner dialog box.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.
7. Problem description:
Requirement – replace. When using the replace feature and a field
contains multiple values, an error occurs.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

8. Problem description:
Requirements – Coverage. Unable to hide coverage between
requirements and test instances.
Fix description:
The problem is fixed. By default, you can create coverage between
requirements and test instances. To disable this feature, in Site
Administration, add the ALLOW_REQ_COVERAGE_BY_TEST_INSTANCE
parameter to the Site Configuration tab and set its value to‘N’.
Limitations:
No limitations.

9. Problem description:
Test Plan – Mail. This problem occurs after you change field values
of a test, and then you proceed to e-mail the test. The changes are
not saved.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

10. Problem description:

Web Browser. An error occurs when minimizing or maximizing the Web
browser.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

11. Problem description:

Defects – Linked Entity. Unable to search for a linked defect in the
Defects to Link dialog box.
Fix description:
The problem is fixed. A search button has been added to the Defects
to Link dialog box.
Limitations:
No limitations.

12. Problem description:

Site Administration – Site Configuration. If the
DISABLE_COMMAND_INTERFACE parameter is set to 'N', users that do not
belong to the TDAdmin group cannot use the OTA ICommand interface.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

13. Problem description:

 WinRunner – Execution Reports. When WinRunner tests are stored
outside the repository and the TS_PATH is set to a network path,
users are unable to open WinRunner reports from Quality Center.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

14. Problem description:

Site Administration – Adding User. You cannot assign more than 1000
users to a project.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

15. Problem description:

LDAP – Importing Users. After importing users from an LDAP server
that has non-English user names, a question mark symbol is added to
their names.
Fix description:
The problem is fixed. There were no functional changes. To use non-
English characters, in Site Administration, set the value of the
LDAP_CHARSET parameter in the Site Configuration tab to Default to
use the Quality Center default character set. Alternatively, you can
set this parameter to another value listed in the encoding sets
supported by Java
(http://java.sun.com/j2se/1.4.2/docs/guide/intl/encoding.doc.html)
Limitations:
No limitations.

16. Problem description:

Test Plan. Unable to run DB-TEST type tests from Quality Center.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

17. Problem description:

Upgrading. When upgrading a large-size project, the process may take
some time.
Fix description:
The problem is fixed. The upgrade process has been optimized. There
were no functional changes.
Limitations:
No limitations

Note: This patch contains all the fixes that were fixed in previous patches for
Quality Center 9.0

II. Issues addressed by previous patches:

QC 9.0 Patch 1
1) Performance:
 a. Poor response time on Oracle for Show Linked Defects: executed SQL
was re-written to use V_LINK_* views.
b. High CPU utilization on Oracle caused by redundant multi value
trigger invocations: trigger logic is now invoked for multi-value
fields only. The condition inside the trigger was changed.
2) Copy-Paste:
a. Attachments were not copied for any Quality Center entity when the
repository was on Unix/Linux: File paths were translated to
operating system specific format.
3) Migration:
a. “Copy file system to database” option inserts the file system into
the database before adjusting folder names: Adjustment is now made
before moving the repository into the database.
4) Synchronization:
a. Line feed characters in Quality Center memo fields are replaced by
the 'space' character after synchronization: <br> was replaced by
\r\n.

QC 9.0 Patch 2
1) Test Lab – When running test steps in the Manual Runner dialog box, in the
bottom of the dialog box, the focus is placed on a user-defined field
instead of the Description field.
2) Defects - Filters applied to the Defects Grid are ignored in the Tabular
Defects report.
3) Test Lab and Business Process Tests - In the Filter dialog box, the Sort
tab is missing.
4) Site Configuration parameter - Fixed the problem with the
SELECT_FS_OVER_DB parameter. This parameter enables you to specify whether
newly created projects should store their repository in the database or
file system. The parameter now works as follows:
When creating an empty project, if this parameter is “Y”, then the project
repository is stored in the database. If the parameter doesn’t exist or is
set to “N”, the project repository is stored in the file system.
When creating a project by copying data from an existing project, if this
parameter is “Y”, then the project repository is stored in the database.
If the parameter doesn’t exist or is set to “N”, then the project
repository is stored in the same way as the one stored in the existing
project.
When creating a project by importing data from an exported project file,
the project repository is always stored in the database.

QC 9.0 Patch 3
1) Site Administration – A new Site Configuration parameter
AUTO_MAIL_USER_NOTIFICATION has been added to Site Administration. When
its value is set to 'N', no mail notification is sent to a project
administrator when users are added or removed from a project from Site
Administration. The default value is ‘Y’.

2) Core – Improvements have been made to the performance of the Sender All
Qualified (SAQ) action. The SAQ action checks whether mail has been sent
from a project, and if mail has been sent, sends the mail to its
recipients.
Each time the SAQ action is performed, Quality Center creates a database
 connection for each project. This can take some time if there are a large

number of projects.

Previously, the SAQ action was performed on every specified project

regardless of whether or not the project was accessed since the SAQ
action was last performed. After installing this patch, Quality Center
only performs the SAQ action on the Quality Center projects that were
accessed during the last time frame. This time frame is defined by a new
Site Configuration parameter MAIL_RECENTLY_ACTIVE_THRESHOLD. If this
parameter is not defined, the time frame is the value of the Site
Configuration parameter MAIL_INTERVAL * 2.

The fix also limits the number of simultaneous SAQ threads to 10 and
improves the efficiency of SQL queries.

3) LDAP Integration – Fixed the problem where Quality Center could not
import users from LDAP with more then 20 characters in the user name. The
limit is now 60 characters.

4) LDAP Integration – Fixed problems when importing users from LDAP to

Quality Center failed due to spaces at the end of the LDAP user name.

5) Site Administration – Fixed the problem where the link in a Quality

Center defect e-mail did not work when the user name contained spaces.

QC 9.0 Patch 4
1) History Records – When working with MS-SQL database servers and multibyte-
character languages (like Chinese and Japanese), names in the Changer
field
are displayed incorrectly in the history.
Solution:
Add -Dmssql_multibyte_encoding=y to the $JAVA_OPTIONS of your application
server.
For a JBoss application server, use the following procedure:
1. Add -Dmssql_multibyte_encoding=y to the $JAVA_OPTIONS in
InstallJbossService.bat file and in run.bat file on the JBoss bin
directory.
2. Execute the following commands:
InstallJbossService.bat –uninstall
InstallJbossService.bat –install

Upgrade the project from Site Administration.

Alternatively, open Project Customization. In the Customize Project
Entities page, select a history-enabled field. Clear the History check box
and save. Reselect the History check box and save.
2) Site Administration API - The SAApi.Disconnect method worked incorrectly.
3) Defects module – When logging in to Quality Center with a defects module
license, linked test runs cannot be viewed.
4) Defects module - The Modified field is not displayed in the Defects
module.
5) LDAP - The LDAP Import Settings dialog box indicated the wrong LDAP
authentication type.
 6) LDAP - When importing LDAP users, if an LDAP attribute contains more than
one
value, Site Administration may import the incorrect value.
Solution: Define the attribute name and value for the
LDAP_IMPORT_ATTRIBUTE_MASK Site Configuration parameter.
Parameter value format: <attribute name>=<regular expression>.
For Example: cn=^\D\w+$, Quality Center searches for a name that starts
with
a non-digit character (^0-9 or ^\d) followed by any character classified
as a
"word" character (a-ZA-Z0-9_).
7) Test Plan module – Fix a refresh problem in the Test Grid When moving the
Cursor, the same field value is duplicated in multiple records.
8) Test Lab module - When selecting a test instance in the Execution Grid,
the
displayed field values are from the previously selected test instance.
9) Workflow - When setting the PageNo property of the Field object, at least
one
field value must be set to page 0. Otherwise, fields mapped to page 1 will

not be displayed.
10) Core – Two Site Configuration parameters have been added:
DB_CONNECTION_TIMEOUT – This parameter enables you to set the time in
minutes a Quality Center connection to the database is idle before the
connection is closed.
If the parameter is not defined or contains a not valid value (not
integer) the default value is 5 minutes.
DB_CONNECTION_POOL_TIMEOUT – This parameter enables you to set the time in

minutes the entire connection pool is idle before it is closed.

If the parameter is not defined or contains a not valid value (not
integer) the default value is 30 minutes.

QC 9.0 Patch 5
1) Test Lab module – If you used a logical operator in the filter condition
for the Tests or Runs sub-reports, an error message displayed.
2) Test Lab module – When you added a defect from the Manual Runner, the
Subject field for the defect was not automatically filled in.
3) Site Administration – Automail did not send mail correctly if a user had
multiple e-mail addresses defined.
4) Site Administrator – In the Servers tab, when you set the value of Max.
Log Days to be higher than 14, Quality Center created new log files and
deleted old log files every day.
5) Workflow – Defect creation workflow events were triggered at the incorrect
time.

QC 9.0 Patch 6
1) Integration – Users imported from an Oracle LDAP server cannot log on to
Quality Center if the search contains only one attribute (for example, a
'username' only).

Note: When defining settings for importing users on the Oracle LDAP
server, you must specify a directory base in the Import Settings dialog
box of the Site Users tab.
2) Mercury Screen Recorder - Opening any Windows Dialog: “Open Files”, “Font
dialog” etc; after Mercury Screen Recorder finished working – the wanted
dialog will not be visible.
3) Customization - When setting user group permissions, you cannot modify
the filter settings in the Data-Hiding Filter dialog box.
4) Test Plan - Version Control is unable to find design steps created using
previous Quality Center versions.
5) Test Lab module - The TestLab_MoveToFolder workflow method is not called
when that action is performed.
6) Analysis - When exporting data to a Microsoft Excel spreadsheet, if an
exported cell contains more then 8185 characters, the export fails and an
error message is displayed.
7) Analysis - When you export data that includes Chinese characters to a
Microsoft Excel spreadsheet, these characters appear as random ASCII
text.
8) Integration - When working with the Clear Case Version Control
integration on a UNIX operating systems, you cannot use attachments.
9) Test Plan – In the Test Plan module, the Version Control integration
causes Quality Center to ignore the field view order defined in the work
flow script.
10) Integration - When executing a QuickTest Professional test (in versions
9.0 or earlier) or a WinRunner test (in any version) and the test has
attachments, the attachments are marked as locked in the Quality Center
server.
11) User Interface - The user interface freezes during login.
12) Site Admin - User associations to projects are deleted in Site
Administration. As a result, these users cannot see the projects they are
assigned to in the login window.
13) Integration – Users imported from LDAP cannot log on to Quality Center if
the user name attribute in the LDAP records contains more than one value.
14) Migration – When migrating a Quality Center project where the repository
is to be stored in the project’s database, the migration fails if the
project contains an attachment with a “’” character in its name.
15) Test Lab module – When the project repository is stored in the database,
you may not be able to open a QuickTest Professional test that contains a
large number of actions.
16) Core – In the Test Plan module, filtering tests by Subject folder affects
performance and may result in a timeout error. It also causes high CPU
consumption on the database.

Note: In addition to the fix in this patch, you can improve performance
further by inserting additional indexes using the script below.
CREATE UNIQUE INDEX AL_ABS_PATH_COV_IDX ON
ALL_LISTS(AL_ABSOLUTE_PATH,AL_ITEM_ID);
CREATE UNIQUE INDEX TS_SUBJECT_IDX ON TEST(TS_SUBJECT, TS_TEST_ID);
It is recommended to run statistics on the database if you are using
Oracle.

17) Site Admin - When copying a Quality Center project whose repository is
stored in the database to a target Quality Center project whose
repository is stored in the file system, the copy process fails if the
source project repository contains a file that cannot be saved for any
reason (for example, it has an illegal name).
 Note: After applying the patch the copy process skips such files and
inserts ‘warning’ message into the site admin log file.

QC 9.0 Patch 7
1. Defects module - When renaming the Defects module using the
REPLACE_TITLE site configuration parameter, not all name values in
the Analysis menu are changed.
2. Test Plan module – In the Test Plan module, the Text Search feature
does not work on projects with version control enabled.
3. Login – Quality Center does not allow European special characters to
be used in a password.
Limitation: The fix does not allow ‘€’ (Euro) sign characters in the
password.
4. Customization – Quality Center is unable to display non-English
characters in user-defined lists that allow multiple values.
5. Test Lab module - The browser stops responding when checking in a
test script to a Visual SourceSafe-enabled project stored in a
Microsoft SQL database server.
6. Core – Quality Center does not support a Microsoft SQL 2005 database.
SQL Server 2005 SP1 is now supported! This allows you to use the Text
Search capability using a SQL Server database type.
Note: If MSSQL strong password is enabled the default password of
Quality Center projects database user can’t be used.
7. Requirements module – When generating a test from a requirement, the
length of the test name is limited to a maximum of 70 characters.
8. Core – When upgrading a Quality Center project, the generated log
messages are not always helpful and do not match the defined log
level.
9. Core – The Open Test Architecture method tdconnecton.DBName returns
an empty string.
10. Test Lab module - When scheduling a test to run in the Execution Flow,
the session is disconnected after Wait before disconnect time.
11. Requirements module – In the Requirements module, paste as sibling
action fails to maintain requirements order.
12. User Interface - When using Remote Desktop to view the Quality Center
client, incorrect colors appear in the UI.
13. Customization – The User Properties window (Customize -> Change User
Properties) can only be accessed by one user at a time. When
additional users try to access the window, Quality Center displays a
message that the object is locked.
14. Customization – The Workflow event TestLab_RunTestsManually(Tests) is
not triggered when you mark a single test for execution.
15. Analysis - When exporting requirements coverage analysis to Word, Word
displays an error message, and the report document is not created.
Limitation: In non English environments the generated document
doesn’t contain document footer.
16. Core – In a project whose repository is stored in a database, the last
modified time for attachments is shown as universal time (UTC)
instead of the client machine local time.
17. Core – When copying a Quality Center project in which the source and
destination project schemas are stored in an Oracle database, Quality
Center displays an error.
18. Core - Quality Center does not close the VAPI-XP test connection when
test execution is finished.
Note:
Before the first execution of VAPI-XP test you need to install
 Quality Center Client on the test machine.
That action ensures you have the fixed client side components.
19. Integration – When LDAP user tries to login to Quality Center with
wrong credentials the related LDAP Connection Thread is left open,
and is never closed in Quality Center server.
20. Upgrade – Upgrade of Quality Center project which is using Oracle
database server fails, Site Admin server log file shows database
‘socket write error’ message.

QC 9.0 Patch 8
1. Problem description:
Customization – Quality Center allows you to add up to three user-
defined fields of Memo type to each Quality Center entity.
Fix description:
The number user-defined fields of Memo type that you can add to each
Quality Center entity has been increased to five.

2. Problem description:
Version Control – When Version Control actions are performed,
Quality Center does not update fields related to the run entity in
the project schema.
Fix description:
The problem was fixed. There is no functional change.

3. Problem description:
Version Control – Design steps of a checked out test are mixed up in
user interface when an undo checkout action is performed after
adding a new step.
Fix description:
The problem was fixed. There is no functional change.

4. Problem description:
LDAP – When more than one LDAP server is used by Quality Center, if
one of the additional LDAP parameters defined in Site Configuration
contains '-' character the authentication operation fails with
'access denied' error.
Fix description:
The problem was fixed. There is no functional change.

5. Problem description:
Test Lab module – When adding tests to a test set, if you filter
subject folders in the test plan tree in the right pane, and drag
tests from the tree to the Execution Grid, Quality Center displays
an error.
Fix description:
The problem was fixed. There is no functional change.

6. Problem description:
Defects module – When grouping defects by the Subject field, Quality
Center displays an error.
Fix description:
The problem was fixed. There is no functional change.
Limitations:
 The grouped defects view presents subjects by their ID numbers, not
by their names.

7. Problem description:
Test Lab module – The VAPI-XP remote agent window is designated as
the ‘on top’ window.
Fix description:
A parameter was added to Quality Center that enables you to choose
whether you want the VAPI-XP remote agent window to be designated as
the ‘on top’ window. To prevent the VAPI-XP remote agent window
being designated as the ‘on top’ window, add the SR_WIN_NO_TOP_MOST
parameter to the Site Configuration tab in Site Administration, and
set its value to ‘Y’. If the parameter does not exist, is empty, or
is set to “N”, the remote agent window is designated as the ‘on top’
window.
8. Problem description:
Integration – The qcdb_get_step_value function used within QuickTest
Professional and WinRunner returns an empty value.
Fix description:
The problem was fixed. There is no functional change.

QC 9.0 Patch 9.1

Test Lab - When Quality Center repository is
stored in a data base: low performance and
users sessions loss might occur when
performing test execution in ?manual runner?
or when saving tests into version control
application. The problem is relevant only for tests with
attachments or tests containing design steps
with attachments.
Fix description: The problem was fixed. There was no
functional change.

QC 9.0 Patch 9.2

1. Problem description:
Defects module – If the Defects_Bug_FieldCanChange workflow event
contains code that sets the current changed field to read-only, the
Quality Center browser might crash when changing a field in the
Defects module grid.
Fix description:
The problem was fixed. There was no functional change.
Limitations:
No limitations.

QC 9.0 Patch 10
1. Problem description:
Enhancement – The Quality Center client does not support Internet
Explorer 7.
Fix description:
The Quality Center client now supports Internet Explorer 7.
Limitations:
• When Internet Explorer 7 is in full screen mode, the Quality
Center user interface loses focus when opening child windows.
 • When clicking on the main menu bar in any Quality Center
module, the mouse pointer freezes. To reactivate the mouse
pointer, click the Internet Explorer icon in the taskbar to
minimize and maximize the browser window.

2. Problem description:
Version Control – When checking in a test, Quality Center loses test
step parameter values.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

3. Problem description:
Requirements module – The status of a requirement linked to a test
instance in the Test Lab module is not updated to reflect the status
of the test instance run.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

4. Problem description:
Test Plan module – When setting the IsReadOnly field object in the
Test Plan module workflow script, Quality Center displays error
messages when switching to the Test Grid.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

5. Problem description:
Analysis – When creating graphs in the Test Plan module, the graph
results are corrupted if the test plan folder names are not unique
(even if they are located in different locations in the folder
tree).
Fix description:
This fix appends the subject ID to the subject name. This ensures
that each folder in the test plan tree has a unique name. To
activate this fix, you must add the ADD_ID_IN_GRAPHS parameter in
the Site Configuration tab of Site Administration, and set its value
to ‘Y’.
Limitations:
No limitations.

6. Problem description:
Version Control – Unable to disable version Control for any project
when Quality Center is integrated with Rational ClearCase.
Fix description:
The problem is fixed. There were no functional changes.
Important: The fix is in the ClearCase Add-in component.
In order to use the fix you need to uninstall the existing ClearCase
add-in. Then activate the matching executable (according to your
Quality Center server OS) in the ‘VCccAddin’ folder in the patch
package.
Limitations:
 No limitations.

7. Problem description:
Version Control - Different Errors while checking in and checking
out tests when using ‘Microsoft Source Safe’ as version control
tool.
Patch_9 solves the problem for new tests but doesn’t solve the
problem for already corrupted tests (see Patch_9 read me file, item
#5 limitations).
Fix description:
The fix accomplishes the fix that was done in patch 9.
It identifies corrupted tests when accessing them by the Quality
Center version control tools.
In such a case the Quality Center server creates a newer, fixed
version of the test in the version control.
Important: The fix is both in the VSS Add-in component and in the
Quality Center patch.
In order to use the fix, besides applying the Quality Center patch,
you need to uninstall the existing VSS add-in: Activate Microsoft
‘Add/Remove Programs’ application and remove ‘Mercury Quality Center
Visual SourceSafe Add-in’ application.
Then activate the ‘setup.exe’ executable in the ‘VSSAddIn’ folder in
the patch package.
Limitations:
Corrupted versions of corrupted tests remain in the version control
history.
However, each such corrupted version contains a comment stating it
is corrupted and redirecting the user to use the next test version –
which is the fixed one.

8. Problem description:
Business Components module – When adding a parameter value to the
Expected Results box of a test step using the Select Parameter
option of the Create/Select Parameter button, Quality Center might
display the following error message: ‘Cannot insert parameter at
this position’.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

9. Problem description:
Business Components module – This defect occurs when importing
component parameters from a Microsoft Excel file. If Quality Center
contains more than one component instance with the same name, only
the first component instance is imported with the correct set of
component parameter values.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

10. Problem description:

Core – The GRANT EXECUTE ON DBMS_LOB TO PUBLIC permission is
required to create a Quality Center project repository in an Oracle
database.
 Fix description:
The grant is no longer required. There were no functional changes.
Limitations:
No limitations.

11. Problem description:

Customization – When setting project users via the 'Set Up Project
Users' customization action, if a user has a not valid email address
an error is prompted.
You can fix this user’s email address and continue setting users
groups; however, all your changes are not saved while performing
this scenario.
Fix description:
A refresh operation was added to keep the server and client
synchronized.
That prevents the scenario above.
Limitations:
No limitations.

QC 9.0 Patch 10.1

1. Problem description:
User Interface – When connecting to Quality Center from an existing
browser instance, a DAX (Developer API eXtension) error appears.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

QC 9.0 Patch 11
1. Problem description:
Test Plan module – When sorting tests in the test plan tree, the
subject order in the tree is not reflected when you filter by
subject in the Test Grid, analysis reports, or Document Generator.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

2. Problem description:
Test Lab module – When sending test set notifications, Quality
Center sends an e-mail with the previous test execution results
instead of the last test execution results.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

3. Problem description:
Core – When you click ‘Authenticate’ in the Quality Center Login
window, Quality Center displays a ‘Failed to Get Visible Domains’
error message if the authenticated user is assigned to more than
1000 projects and the Quality Center Site Administrator schema is
stored in an Oracle database.
Fix description:
The problem is fixed. There were no functional changes.
 Limitations:
No limitations.

4. Problem description:
Defects module – If the Comments field is configured to read-only in
the workflow script, Quality Center does not trigger a workflow
event when clicking the Add Comment button in the defect
description.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

5. Problem description:
Site Administrator – The getConnectionsCount API method fails when
there are one or more user connections.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

QC 9.0 Patch 12
1. Problem description:
Workflow – Quality Center does not reflect the field view order when
setting the field view order in _MoveTo workflow events.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

2. Problem description:
Test Plan module – This defect occurs when a Quality Center project
is stored in a Microsoft SQL 2000 database server and the repository
is in the database. When switching from one BPT test to another in
the Test Plan module while the Test Script tab is displayed, Quality
Center takes a long time to update the user interface. During this
time, the SQL server’s performance is severely reduced, and 100% CPU
utilization is performed by the Quality Center thread.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

3. Problem description:
Test Plan module – When filtering tests by subject in the test plan
tree, there is performance degradation on the client. This fix
solves the performance problem encountered after deploying Patch 11
for Quality Center 9.0 which fixes the subjects filter tree to
reflect the test plan subject tree order (see fix #1 in the Patch 11
readme file).
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

4. Problem description:
 Defects module – The Defects_GetNewBugPageName workflow event is not
triggered when creating a new defect form.
Fix description:
The event is triggered the first time a defect is created on the
client. It is not triggered when creating subsequent defects, since
the defect form is reused. It is triggered again only after the next
log in.
Limitations:
No limitations.

5. Problem description:
Version Control – After migrating a project that is linked to a
version control tool from TestDirector to Quality Center, and then
checking out a version of the migrated project that is not the
latest one, database corruption occurs when checking in or undoing
the check out.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

6. Problem description:
Client Side – Potential security vulnerability has been identified
with Quality Center that could be exploited by remote
unauthenticated users to execute arbitrary code.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

QC 9.0 Patch 12.1

1. Problem description:
Workflow – Quality Center does not reflect the field view order when
setting the field view order in _FieldChange and _FieldCanChange
workflow events.
Fix description:
This fix accomplishes the fix presented in Patch_12 for Quality
Center 9.0. See item #1 in Patch_12 read me file.
The problem is fixed. There were no functional changes.
Limitations:
The workflow code should not contain message box due to focus
collision with the User Interface components.

2. Problem description:
Test Plan module – Tests scripts are not presented when the Quality
Center project repository is stored in the database.
This problem occurs after applying Patch_12 for Quality Center 9.0.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

QC 9.0 Patch 12.2

1. Problem description:
 Workflow – Duplicated fields and redundant spaces between fields
might appear in Quality Center modules after view order modification
executed by workflow code.
Fix description:
This fix accomplishes the fix presented in Patch_12.1 for Quality
Center 9.0. See item #1 in Patch_12.1 read me file.
The problem is fixed. There were no functional changes.
Limitations:
The workflow code should not contain message box due to focus
collision with the User Interface components.

QC 9.0 Patch 13
1. Problem description:
Core – User sessions are not being cleaned when there are more than
1000 unused sessions open in Quality Center.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

2. Problem description:
User Interface – When using Internet Explorer 7 on a client machine,
the mouse pointer freezes after clicking the main menu bar in some
Quality Center forms.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

3. Problem description:
User Interface – When using Internet Explorer 7 on a client machine
with Windows XP, all Quality Center modal windows and dialog boxes
(such as the Defect Details dialog box) lose focus after switching
to full screen.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

4. Problem description:
Test Lab module – The TestSet_Fields("CY_CYCLE_ID").Value workflow
object returns the wrong result when the tree view is used.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

5. Problem description:
Core – Performance degrades when user projects are refreshed on the
Quality Center server. By default, Quality Center refreshes user
projects every two hours.
Fix description:
The fix improves Quality Center performance by changing the default
interval to 24 hours (instead of two hours), and enabling the user
to configure the interval setting. To change the interval, in the
 USERS_PROJECTS_REFRESH_INTERVAL parameter in the Site Configuration
tab of Site Administration, set the parameter value to the desired
interval (in hours).

Limitations:
- The first execution of this job is always 24 hours after start up

time.
- When changing the Site Configuration interval parameter, changes
only take effect after the next execution of the job.

6. Problem description:
Core – When importing a user from LDAP into Quality Center and the
user name contains a character that is not valid in Quality Center,
Quality Center converts the character to an underscore (‘_’).
The imported user is unable to log in to the project, since the
Quality Center Login window does not allow invalid parameters as an
input.
Fix description:
The Quality Center Login window converts invalid user input
characters to the underscore (‘_’) character. This enables a user
with an invalid user name imported from LDAP to log in to the
project.
Limitations:
No limitations.

7. Problem description:
Test Lab module – When the TestLab_Testset_Canpost workflow event
returns ‘false’, the created test set is keep being presented in the
Test Lab module.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

8. Problem description:
Test Plan module – Unable to enter some Chinese characters as the
parameter name in the Design Steps tab.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

9. Problem description:
Site Administration – When terminating a connection in the Site
Connections tab of Site Administration, it may take up to 15 minutes
to update the user quota calculation.
Fix description:
The user quota calculation is now updated immediately after
terminating the connection.
Limitations:
No limitations.

10. Problem description:

Test Plan module – When performing ‘check in’ or ‘check out’
operations in a version control-enabled project, the user interface
does not immediately reflect the test version control state. Unless
 the project is refreshed, a user might be able to edit a ‘checked
in’ test, or unable to edit a ‘checked out’ project.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

11. Problem description:

Analysis – A report document generated by Document Generator does
not show parameter values sent to a called test in the design steps
recursive view.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

12. Problem description:

Analysis – Setting the Document Generator to produce a recursive
view of design steps does not work in the Subject Tests page of the
Document Generator tree (Test Plan -> Subject Tree -> Subject
Tests).
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

13. Problem description:

Analysis – An ‘External Exception’ error occurs during graph
creation when a Quality Center project is stored on a Microsoft SQL
database server. The problem is a result of converting dates to the
format of the local Quality Center server.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

QC 9.0 Patch 14
1. Problem description:
Analysis – When creating Live Analysis graphs for a test subject
folder in the Test Plan module, an error occurs if the Quality
Center project is stored on an Oracle database server and the test
subject folder contains more than 1000 tests.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

2. Problem description:
Test Lab module – When adding more than 90 tests to a test set by
dragging and dropping the containing folder, if there is a required
field in the TEST IN TESTSET entity in the Customize Project
Entities page, Quality Center displays a ‘Failed to post TD Test’
error message.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
 No limitations.

3. Problem description:
Core – Quality Center retrieves the database structure of db tables
for its operations. It does not retrieve database views.
Fix description:
Quality Center server can now read database views structure as well.
Limitations:
No limitations.

4. Problem description:
Core – When the Quality Center project repository is stored in an
Oracle database, the Quality Center client fails to download items
that contain more than 1000 components.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

QC 9.0 Patch 15
1. Problem description:
Test Lab module - The following limitations occur when a Quality
Center Project is stored in an Oracle database and there is a
required user-defined field in the TEST IN TESTSET entity in the
Customize Project Entities page. When dragging a test plan folder
that contains more than three tests into a test set and running the
tests using Manual Runner, the tests point to design steps of a
different test. In addition, when right-clicking a test in a test
set and selecting Go to Test in Test Plan Tree, the wrong test is
selected in the test plan tree.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

2. Problem description:
OTA - The Open Test Architecture AddParam method from the command
object is not working.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

3. Problem description:
Authentication – Password encryption has been broken in the Quality
Center Login window.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

4. Problem description:
Business Components module - When there are a large number of
iterations in a business process test, and the script is displayed
 in the Test Script tab, changing to another business process test in
the Test Lab module results in an error.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
Although you can configure a component to run up to 2000 iterations,
it is not recommended to exceed 500 iterations as performance will
become very slow.

5. Problem description:
Exporting Data - When exporting grid rows to Microsoft Excel, the
date format is converted to English (United States) date format
(month:day:year) even if the machine is set to a different format.
Fix description:
The problem is fixed. The cell date format is according to the
user’s language selection. There were no functional changes.
Limitations:
No limitations.

6. Problem description:
Requirements module - Requirement fields that are defined by the
workflow as read-only are editable in the requirements tree view.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

7. Problem description:
Test plan module - When creating a new test in the workflow,
changing the test prefix is not updated.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

8. Problem description:
Version Control - In a project migrated from TestDirector to Quality
Center, when checking in a migrated test that has a design step with
an attachment, there is a violation of the primary key on the
CROS_REF table.
Fix description:
The problem is caused by corrupt data in the test before it is
migrated to Quality Center 9.0. The VC tables are cleaned and an
error message is displayed when you try to check out the corrupted
data.
Limitations:
No limitations.

9. Problem description:
Security – When a user’s password is changed by another user, there
is no record of this change in the log.
Fix description:
The problem is fixed. This information is now recorded in the log
file.
Limitations:
No limitations.
10. Problem description:
LDAP - When using LDAP, changing a user password from the Project
Customize window does not produce an error message.
Fix description:
The problem is fixed. When LDAP is used, users receive an error
message that it is not possible to externally change the
authentication password.
Limitations:
No limitations.
11. Problem description:
Test Plan module – When copying a folder with attachments to another
location in the same project, this causes deadlock in the database
server when the Quality Center project repository is stored in the
database.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

12. Problem description:

Requirements module – When adding a requirement (including children)
that has more than 120 children requirements to test coverage,
Quality Center displays a ‘Failed to Cover Req’ error message.
Fix description:
The problem is fixed. There were no functional changes.
Limitations:
No limitations.

13. Problem description:

Defect module – The Defects_GetNewBugPageName workflow event is not
triggered.
Fix description:
The problem is fixed. There were no functional changes.
Limitations
No limitations.

III. Installing instructions.

----------------------------
This patch is intended to be installed on top of Quality Center 9.0 only. To
check the version you are using, select Help > About Mercury Quality Center.

Installing the Patch

--------------------

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

Notes:
• Before installing the patch, make sure that all users have logged 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 Quality
Center Client Side Setup Add-in on the Mercury Quality Center Add-ins page,
or contact Mercury Customer Support (http://support.mercury.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.
• Windows: Run the setup.exe file.
• Solaris: In the command prompt, type: ./setupSolaris.bin
• Linux: In the command prompt, type: ./setupLinux.bin

Note: When installing on a Solaris or a Linux platform, 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.
• 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/cgi-
bin/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/cgi-
bin/portal/CSO/kbBrowse.jsp).

4. Start the Quality Center service.

VI. 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.0 Patch1\_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 we moved to a different
directory.