CaliberRM® 2008 - Borland Technical Publications
CaliberRM® 2008 - Borland Technical Publications
CaliberRM® 2008 - Borland Technical Publications
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
CaliberRM® <strong>2008</strong><br />
Release Notes
<strong>Borland</strong> Software Corporation<br />
8310 North Capital of Texas Hwy<br />
Building 2, Suite 100<br />
Austin, Texas 78731<br />
http://www.borland.com<br />
<strong>Borland</strong> Software Corporation may have patents and/or pending patent applications covering subject matter in this document. Please<br />
refer to the product CD or the About dialog box for the list of applicable patents. The furnishing of this document does not give you<br />
any license to these patents.<br />
Copyright © 2009 <strong>Borland</strong> Software Corporation and/or its subsidiaries. All <strong>Borland</strong> brand and product names are trademarks or<br />
registered trademarks of <strong>Borland</strong> Software Corporation in the United States and other countries. All other marks are the property of<br />
their respective owners.<br />
ii
Contents<br />
CaliberRM <strong>2008</strong> Release Notes...............................................................................5<br />
What's New................................................................................................................................5<br />
Support for Third-Party Integration Tools.........................................................................5<br />
Enhanced Document Factory..........................................................................................5<br />
Access to Saved Grid and Matrix Filters in Document Factory.......................................5<br />
API Changes...................................................................................................................6<br />
URL Addressability..........................................................................................................6<br />
Filter Mechanism on Grid................................................................................................6<br />
Filter Criteria in Grid and Matrix......................................................................................6<br />
Status Add-In Added to Datamart...................................................................................6<br />
Visual Improvement to Baseline Maintenance Window...................................................6<br />
Help Content....................................................................................................................7<br />
System Requirements and Prerequisites...................................................................................7<br />
CaliberRM Server............................................................................................................7<br />
CaliberRM Windows Client..............................................................................................7<br />
CaliberRM for Eclipse......................................................................................................8<br />
CaliberRM for Microsoft Team Foundation Server...........................................................8<br />
CaliberRM Client for Microsoft Visual Studio Team System 2005 and <strong>2008</strong>...................8<br />
CaliberRM Web...............................................................................................................9<br />
Software Compatibility.....................................................................................................9<br />
Installation and Upgrade Instructions.......................................................................................10<br />
CaliberRM Server..........................................................................................................10<br />
CaliberRM Windows Client............................................................................................10<br />
CaliberRM for Eclipse....................................................................................................11<br />
CaliberRM for Microsoft Visual Studio 2005..................................................................11<br />
CaliberRM for Microsoft Visual Studio <strong>2008</strong>..................................................................11<br />
CaliberRM for Microsoft Visual Studio Team System....................................................11<br />
Resolved Issues.......................................................................................................................11<br />
Resolved Issues for Patch 11........................................................................................11<br />
Resolved Issues for Patch 10........................................................................................11<br />
Resolved Issues for Patch 9..........................................................................................12<br />
Resolved Issues for Patch 8..........................................................................................13<br />
Resolved Issues for Patch 7..........................................................................................15<br />
Contents | 3
Resolved Issues for Patch 6..........................................................................................16<br />
Resolved Issues for Patch 5..........................................................................................17<br />
Resolved Issues for Patch 4..........................................................................................17<br />
Resolved Issues for Patch 3..........................................................................................18<br />
Resolved Issues for Patch 2..........................................................................................19<br />
Resolved Issues for Patch 1..........................................................................................19<br />
Resolved Issues for <strong>2008</strong>..............................................................................................22<br />
Resolved Issues for 2006..............................................................................................23<br />
Updated Files in Patch..................................................................................................25<br />
Known Issues...........................................................................................................................26<br />
CaliberRM Server..........................................................................................................26<br />
CaliberRM Windows Client............................................................................................26<br />
CaliberRM for Eclipse....................................................................................................30<br />
CaliberRM for Microsoft Visual Studio <strong>2008</strong> / Visual Studio Team Foundation <strong>2008</strong>.....30<br />
CaliberRM for Microsoft Visual Studio 2005..................................................................31<br />
CaliberRM for Microsoft Visual Studio Team System....................................................32<br />
CaliberRM Web Client...................................................................................................32<br />
Limitations................................................................................................................................33<br />
4 | Contents
CaliberRM <strong>2008</strong> Release Notes<br />
October 2, 2009<br />
This document contains system requirements, software-compatibility requirements, and other important<br />
information that might not appear in the Help. It is recommended that you read these Release Notes in their<br />
entirety. To view the most recent version of this document, visit http://techpubs.borland.com/caliber.<br />
The CaliberRM SDK Programmers Guide and the CaliberRM Tutorial are not included in the release media.<br />
However, they are available for download from http://techpubs.borland.com/caliber.<br />
What's New<br />
This section provides an overview of the new features found in CaliberRM.<br />
Support for Third-Party Integration Tools<br />
HP Quality Center Version 10.0 is supported for non-versioning projects. Support is not provided for Mercury<br />
Quality Center (QC) 10.0 for versioning-enabled projects that use CaliberRM Mercury Publisher and CaliberRM<br />
Test Wizard tools.<br />
Enhanced Document Factory<br />
A new version of Document Factory has been added to the product. This new version uses a set of XML<br />
interfaces to Word rather than the COM interfaces. This change results in the faster generation of documents<br />
and allows the generation of more flexible templates in releases following v<strong>2008</strong>. Additionally, documents are<br />
now generated without the use of an intermediate MS Access database because data is pulled directly from<br />
the server during generation.<br />
The original Document Factory is still included. For any version of Microsoft Word v2003 or earlier, the default<br />
version is the original Document Factory. For Word 2003 or 2007, you can choose either the new or the old<br />
document factory. The new Document Factory works with Microsoft Word version 2003 or later. To continue<br />
using the previous version of Document Factory for Microsoft Word version 2003 or later, specify the appropriate<br />
path in the registry. Otherwise, the new Document Factory is initiated by default for Microsoft Word version<br />
2003 or later. For more information, contact technical support.<br />
Initial comparison results for document generation indicate that the new version of Document Factory can<br />
generate a document twice as fast as the previous version.<br />
Access to Saved Grid and Matrix Filters in Document<br />
Factory<br />
Beginning in v2006, the Traceability Matrix filter mechanism allowed users to save their filters. In v<strong>2008</strong>, that<br />
filter capability was added to the Requirements Grid. The filters that are created and saved can be accessed<br />
by keyword in the new Document Factory. As a result, the output is captured in the Document Factory when<br />
the filter is executed.<br />
CaliberRM <strong>2008</strong> Release Notes | 5
API Changes<br />
New methods are provided for the following actions:<br />
• Managing licenses though the SDK<br />
• Obtaining a checkpoint to view changes since a previous checkpoint<br />
URL Addressability<br />
URL addressability allows you to create a URL for any given requirement. Navigation of the URL requires the<br />
user to have installed the CaliberRM Client. The URL does not follow the traditional HTTP style because the<br />
target is directed to the CaliberRM application. The URL can be pasted into a browser or the Windows Run<br />
dialog box for execution. Users must log on if they are not already logged on to the target project.<br />
Filter Mechanism on Grid<br />
The same filter mechanism that was added to the Traceability Matrix in v2006 is now available on the<br />
Requirements Grid, allowing you to build more complex filters and save those filters for reuse. Unlike filters in<br />
version 2006, filters in the current version are saved on the server side. Consequently, performance is improved<br />
due to less data being sent across the network to the client.<br />
Saving filters on a user's computer saves the column layout in an RGV file.<br />
Filter Criteria in Grid and Matrix<br />
Baseline filter criteria has been added to the Traceability Matrix and to the Requirements Grid.<br />
Hierarchies and the most recently modified information exist only as views. Filtering capability is not available<br />
for these fields.<br />
Status Add-In Added to Datamart<br />
The status attribute of items that are traced to CaliberRM by way of the traceability add-in are now included<br />
in the Datamart extract. Users can include them in reports. For example, the status of a test case linked to<br />
Quality Center is now available in the Datamart extract.<br />
Visual Improvement to Baseline Maintenance Window<br />
Requirements can be deleted from the current baseline (but not from a selected baseline) yet remain available<br />
because they are part of another baseline. In the Baseline Maintenance window, a visual clue differentiates<br />
requirements that are deleted from requirements that simply do not appear in the selected baseline.<br />
Requirements can be identified by their fonts and colors, as follows:<br />
• Requirements in the selected baseline appear in bold<br />
• Requirements in the current baseline but not in the selected baseline appear in normal font<br />
• Requirements that do not reside in either the current or selected baseline are teal in color<br />
6 | CaliberRM <strong>2008</strong> Release Notes
Help Content<br />
Because of a major documentation conversion that was underway during the 2006 release, that version did<br />
not contain all of the Help topics that were available in previous releases. The <strong>2008</strong> release completes the<br />
conversion and includes the missing topics that are relevant to v<strong>2008</strong>.<br />
System Requirements and Prerequisites<br />
This section identifies the system requirements and prerequisites for the various CaliberRM components.<br />
CaliberRM Server<br />
The following table identifies the system requirements for installing and running CaliberRM Server.<br />
System Area<br />
Platforms<br />
Hardware requirements<br />
VMware<br />
Hard disk space<br />
Requirement<br />
• Windows Server 2003 Enterprise Edition (SP1, 32-bit<br />
version)<br />
• Windows Server 2003 R2 Standard Edition (SP1, 32-bit<br />
version)<br />
• Windows Server 2003 R2 Enterprise Edition (SP1, 32-bit<br />
version)<br />
Recommended configuration by OS provider<br />
VMware ESX Server 3.0.1<br />
1 GB (minimum); 30 GB or higher (recommended). Existing<br />
customers must have at least 2.5 times their current<br />
database size prior to upgrading.<br />
Note: The actual amount varies, depending on your<br />
use of the product.<br />
CaliberRM Windows Client<br />
The CaliberRM Windows Client is available in English, Japanese, French, and German. Only one of the<br />
supported languages can be installed, and most of the supported languages must be installed on the matching<br />
operating system. However, English can be installed on non-English operating systems.<br />
The following table identifies the system requirements for installing and running CaliberRM Windows Client.<br />
System Area<br />
Platforms<br />
Hardware requirements<br />
Web browser<br />
Requirement<br />
• Windows XP Professional (SP2)<br />
• Windows Vista Enterprise Edition<br />
Configuration recommended by OS provider<br />
Internet Explorer 7.0<br />
CaliberRM <strong>2008</strong> Release Notes | 7
CaliberRM for Eclipse<br />
The following table identifies the system requirements for installing and running CaliberRM for Eclipse.<br />
System Area<br />
Software<br />
Hardware requirements<br />
Requirement<br />
Eclipse 3.2, 3.3 (available for download from<br />
http://www.eclipse.org)<br />
Configuration recommended by Eclipse<br />
CaliberRM for Microsoft Team Foundation Server<br />
The following table identifies the system requirements for installing and running CaliberRM for Microsoft Team<br />
Foundation Server.<br />
System Area<br />
Platforms<br />
Software<br />
Requirement<br />
Refer to Visual Studio Team Foundation Installation Guide,<br />
available for download at<br />
htp:/www.microsoft.com/downloads/details.aspx?familyid=f12844f-398c-4fe9-8b0d-9e84181d9923&displaylang=en<br />
• Microsoft Visual Studio <strong>2008</strong> Team Foundation Server<br />
• Microsoft Visual Studio 2005 Team Foundation Server<br />
Note: Support for Microsoft Team Foundation Server 2003 has been removed.<br />
CaliberRM Client for Microsoft Visual Studio Team System<br />
2005 and <strong>2008</strong><br />
CaliberRM for Microsoft Visual Studio Team System is available in English and Japanese. Only one of the<br />
supported languages can be installed, and it must be installed on the matching operating system.<br />
The following table identifies the system requirements for installing and running CaliberRM Client for Microsoft<br />
Visual Studio Team System 2005 and <strong>2008</strong>.<br />
System Area<br />
Platforms<br />
Processor, RAM<br />
Requirement<br />
Refer to the Microsoft system requirements at<br />
http://msdn.microsoft.com/en-us/vsts<strong>2008</strong>/aa718944.aspx<br />
Refer to the Microsoft system requirements at the following<br />
locations:<br />
• http://msdn.microsoft.com/en-us/vsts<strong>2008</strong>/aa718687.aspx<br />
for Visual Studio 2005 Team Edition for Software<br />
Developers<br />
• htp:/download.microsoft.com/download/A/2/8/A2807F78-C861-4B66-9B31-9205C3F22252/VS<strong>2008</strong>SP1Readme.htm<br />
for Visual Studio <strong>2008</strong> Team Edition for Software<br />
Developers<br />
8 | CaliberRM <strong>2008</strong> Release Notes
System Area<br />
Software<br />
Requirement<br />
• Visual Studio 2005 Team Suite<br />
• Visual Studio <strong>2008</strong> Team Suite<br />
• Microsoft Visual Studio 2005 Team Explorer<br />
• Microsoft Visual Studio <strong>2008</strong> Team Explorer<br />
Note: Microsoft VS 2003 integration is no longer supported because mainstream support from Microsoft<br />
ended in October <strong>2008</strong>. Nevertheless, a defect in the installer shows the option to install VS 2003 integration.<br />
A future version of the CaliberRM installer will fix this bug and remove this installation option.<br />
CaliberRM Web<br />
The following table identifies the system requirements for installing and running CaliberRM Web.<br />
System Area<br />
Web server<br />
Client browser<br />
JDK/JRE<br />
Requirement<br />
• Apache (provided)<br />
• IIS<br />
Internet Explorer 6.0 SP1, 7.0<br />
1.6, 1.6.x.x<br />
Software Compatibility<br />
The following table lists supported, third-party products with integrations have been tested.<br />
CaliberRM Feature<br />
Traceability<br />
Supported Product<br />
<strong>Borland</strong> StarTeam<br />
<strong>Borland</strong> Together for Eclipse<br />
<strong>Borland</strong> Silk Central Test Manager<br />
IBM Rational ClearCase<br />
Merant PVCS Version Manager<br />
Mercury Quality Center<br />
Microsoft Visual SourceSafe<br />
Tested Version<br />
2006, <strong>2008</strong><br />
2006, 2007<br />
2006 (8.5), 2007 (8.6), <strong>2008</strong> (8.8)<br />
2003<br />
6.8<br />
9.0, 9.2, 10.0<br />
6.0 SP6<br />
Document Factory reports, document<br />
references, and requirements export (to<br />
Access) and import (from Word)<br />
• Microsoft Office 2000 (reports using<br />
older Document Factory only), 2003,<br />
2007<br />
• MS Word 2000, 2003, 2003 SP2,<br />
2003 SP3, 2007<br />
• MS Excel 2000, 2003, 2003 SP2,<br />
2003 SP3, 2007<br />
Datamart extraction targets and analysis<br />
tools<br />
Business Objects<br />
Microsoft Access<br />
6.5, 11<br />
2003, 2007<br />
CaliberRM <strong>2008</strong> Release Notes | 9
CaliberRM Feature<br />
Integrated Development Environment<br />
(IDE) integrations<br />
Web server<br />
Software license servers<br />
Microsoft Windows Server Internet<br />
Information Services (IIS)<br />
VMware<br />
Supported Product<br />
Microsoft SQL Server<br />
Oracle Database Server<br />
<strong>Borland</strong> Developer Studio © ++ Builder,<br />
C# Builder, Delphi)<br />
<strong>Borland</strong> JBuilder<br />
Microsoft Visual Studio<br />
Microsoft Visual Studio Team System<br />
Eclipse<br />
Apache Web Server<br />
Microsoft Windows Server Internet<br />
Information Services (IIS)<br />
MacroVision FlexLM<br />
2000 (5.0), 2003 (6.0)<br />
VMware ESX Server<br />
Tested Version<br />
2000, 2005<br />
10g<br />
2006<br />
2005, 2006<br />
Visual Studio 2005 SP1, <strong>2008</strong><br />
2005 SP1, <strong>2008</strong><br />
3.2, 3.3<br />
2.0<br />
2000 (5.0), 2003 (6.0)<br />
8.2a<br />
—<br />
3.0.1<br />
Installation and Upgrade Instructions<br />
The upgrade procedure has changed from previous releases. Existing customers are encouraged to review<br />
the Performing an Upgrade section of the Installation Guide, which is available from the <strong>Borland</strong><br />
Documentation Web site at http://techpubs.borland.com/caliber.<br />
CaliberRM Server<br />
If the database contains a large number of traces, the server database size might grow noticeably during the<br />
upgrade.This growth is due to the introduction of traceability versioning in this release. If you have unnecessary<br />
traces that are either created manually or copied and pasted from a previous requirement, it is recommended<br />
that you remove them before upgrading. For more information, contact support or visit <strong>Borland</strong> Answers at<br />
http://support.borland.com/entry.jspa?externalID=5313.<br />
If your existing SDK application must connect to a server that is not yet upgraded to this release, do not<br />
recompile your application with the included SDK. In general, when writing SDK applications, use the same<br />
version of the SDK as the version of the oldest server to which the application must connect.You must recompile<br />
your .NET/COM SDK applications to make use of the new SDK functionality provided in this release, such as<br />
creating and assigning security profiles.The recompiled application is compatible with this release of the server.<br />
To restore a backup made with a previous version of CaliberRM, first upgrade the backup to <strong>2008</strong>.<br />
CaliberRM Windows Client<br />
Installation instructions for the CaliberRM Windows Client depend on whether the client is installed on a machine<br />
that is different from the server. For more information, refer to the Installation Guide.<br />
10 | CaliberRM <strong>2008</strong> Release Notes
CaliberRM for Eclipse<br />
For installation instructions, refer to the Installation Guide.<br />
CaliberRM for Microsoft Visual Studio 2005<br />
For installation instructions, refer to the Installation Guide.<br />
CaliberRM for Microsoft Visual Studio <strong>2008</strong><br />
For installation instructions, refer to the Installation Guide.<br />
CaliberRM for Microsoft Visual Studio Team System<br />
Prior to installing the CaliberRM Client for Visual Studio Team System (VSTS), your VSTS administrator must<br />
install CaliberRM for Team Foundation Server on the machine that hosts Team Foundation Server. The<br />
CaliberRM client for Microsoft Visual Studio Team System component must be installed by each VSTS user<br />
(architect, developer, tester, etc) to access CaliberRM requirements from within Visual Studio and establish<br />
traceability between requirements and VSTS work items as well as tests from Visual Studio.<br />
For installation instructions, refer to the Installation Guide.<br />
Resolved Issues<br />
This section identifies issues that have been resolved by the various patches for CaliberRM <strong>2008</strong> WW release.<br />
Resolved Issues for Patch 11<br />
The following table identifies issues that have been resolved by Patch 10 for CaliberRM <strong>2008</strong> WW release.<br />
Category<br />
Traceability Matrix<br />
CaliberRM Server<br />
Change Request Number<br />
44061<br />
43991<br />
Description<br />
In the traceability matrix, the action of<br />
right-clicking the cell that represents a<br />
trace between a requirement and an<br />
external vendor object causes the<br />
matrix to hang.<br />
Prevents CaliberRM Server from<br />
exposing the physical host name to<br />
Caliber Client.<br />
Resolved Issues for Patch 10<br />
The following table identifies issues that have been resolved by Patch 10 for CaliberRM <strong>2008</strong> WW release.<br />
CaliberRM <strong>2008</strong> Release Notes | 11
Category<br />
CaliberRM Win32 Client<br />
CaliberRM Win32 Client<br />
Migration<br />
Datamart<br />
CaliberRM Win32 Client<br />
Integration with DefineIT<br />
Patch installer<br />
Datamart<br />
Datamart<br />
Requirements Grid<br />
Change Request Number<br />
44049<br />
44033<br />
44032<br />
44031<br />
44028<br />
44022<br />
44022<br />
43968<br />
43967<br />
23993<br />
Description<br />
Error message CaliberRM<br />
Internal Error: 91-CD opens<br />
for a requirement while saving a child<br />
requirement on the References page.<br />
Deleted users can still be edited in the<br />
multiple selection user list (MSUL) UDA<br />
for Win32 Client.<br />
Data is duplicated when migrating DB<br />
from 2005 to <strong>2008</strong>.<br />
Datamart cannot complete extractions<br />
on large databases.<br />
Deleted users can still be selected in<br />
the MSUL UDA for Win32 Client.<br />
Synchronization from DefineIT<br />
generates a namespace error in<br />
CaliberRM Client's history view.<br />
Synchronization from a DefineIT<br />
requirement with a specific word tag<br />
causes the error NameSpace error<br />
in the History view of the CaliberRM<br />
Client.<br />
After installing the current version of the<br />
patch, the previous patch still appears<br />
in the Add or Remove Programs<br />
Control Panel applet .<br />
When running Datamart with the option<br />
-update -depth 1, the number of<br />
updated traces is larger than expected.<br />
Datamart crashes when trying to extract<br />
traces from a large database.<br />
When user filters for a UDA value in the<br />
Requirements Grid return no matches,<br />
the column disappears from the grid.<br />
Resolved Issues for Patch 9<br />
The following table identifies issues that have been resolved by Patch 9 for CaliberRM <strong>2008</strong> WW release.<br />
Category<br />
CaliberRM SDK<br />
CaliberRM Datamart<br />
Change Request Number<br />
43952<br />
43890<br />
Description<br />
Error Object_does_not_exist<br />
occurs when you call<br />
projectmanager.getproject(projectid)<br />
for an empty project.<br />
When you create a UDA of type<br />
multiple-line text and set the maximum<br />
length to 10,000 (i.e., when a<br />
requirement is set with value of 10,000<br />
12 | CaliberRM <strong>2008</strong> Release Notes
Category<br />
CaliberRM Win32 Client<br />
CaliberRM Win32 Client<br />
CaliberRM Win32 Client<br />
CaliberRM DocFactory<br />
CaliberRM Win32 Client<br />
CaliberRM Win32 Client<br />
CaliberRM Server<br />
Change Request Number<br />
43854<br />
43821<br />
43803<br />
43771<br />
43705<br />
42701<br />
41623<br />
Description<br />
characters), it is truncated to 2,048<br />
characters when extracted to MS<br />
Access.<br />
Deleted values of the MSUL attribute<br />
still appear in the Requirements Grid.<br />
Requirements can be modified through<br />
the Requirements Grid with deleted<br />
values.<br />
In the General Options section of the<br />
Spelling page (CaliberRM ➤ Tools ➤<br />
Options ➤ Spelling), parent-child<br />
relationship are not followed by check<br />
boxes.<br />
Parent: Always check spelling before<br />
saving requirements.<br />
Child: Check spelling only if the<br />
requirement's description is modified.<br />
Broken functionality with the client-side<br />
option to create a child-to-parent trace<br />
upon requirement creation.<br />
The new Document Factory refuses to<br />
log on if password is expired. Unlike the<br />
new Document Factory, the previous<br />
version handles this situation by<br />
prompting the user for a new password.<br />
External Trace Status does not work<br />
with Silk Central Test Manager (SCTM)<br />
<strong>2008</strong> R2 SP1.<br />
Linking Service fails to log on to SCTM.<br />
MPX event notification in Framework<br />
Administrator; changes made to a group<br />
are not saved if the same record is<br />
edited on another instance.<br />
Resolved Issues for Patch 8<br />
The following table identifies issues that have been resolved by Patch 8 for CaliberRM <strong>2008</strong> WW release.<br />
Category<br />
CaliberRM DocFactory<br />
CaliberRM Client<br />
Change Request Number<br />
43830<br />
43633<br />
Description<br />
After navigating backward in the new<br />
Document Factory wizard, the last<br />
button clicked is presented as the<br />
default selection instead of Next or<br />
Finish.<br />
The Import from Word function<br />
inappropriately imports text into the<br />
requirement description that is specified<br />
CaliberRM <strong>2008</strong> Release Notes | 13
Category<br />
CaliberRM DocFactory<br />
CaliberRM DocFactory<br />
CaliberRM DocFactory<br />
CaliberRM Server<br />
CaliberRM Server<br />
CaliberRM Datamart<br />
CaliberRM DocFactory<br />
CaliberRM Datamart<br />
CaliberRM DocFactory<br />
CaliberRM DocFactory<br />
Change Request Number<br />
43849<br />
43867<br />
43858<br />
43786<br />
43732<br />
43720<br />
43691<br />
42799<br />
42499<br />
42520<br />
Description<br />
by a style to become the requirement<br />
name.<br />
When you invoke the Document<br />
Factory, the StarTeam toolbar does not<br />
cache the logon information. The first<br />
page is prepopulated with the last<br />
logged-on server, and the user name is<br />
retrieved from the registry.<br />
The Password text box also appears<br />
to be prepopulated. However, the<br />
Password text box is always<br />
prepopulated with the password<br />
admin.<br />
The new Documentation Factory throws<br />
an unhandled exception if a user clicks<br />
OK to close the message and then<br />
navigates back to Page 1 from Page 2.<br />
The new Documentation Factory hangs<br />
when you click Close on forms other<br />
than the Startup form.<br />
Any changes to the old versions of<br />
requirements are not displayed in the<br />
history.<br />
A requirement and its children appear<br />
as read-only objects. The CaliberRM<br />
Client shows the previous requirement<br />
version instead of the current one.<br />
When running a Datamart extraction to<br />
MS Access or SQL, the special<br />
character " " is stripped out along with<br />
all HTML tags.This action removes any<br />
spaces that lie between words in the<br />
resulting requirement description.<br />
The extension of the default result file<br />
is .doc. The new Documentation<br />
Factory does not support the extension<br />
.docx.<br />
When performing Datamart extractions,<br />
the requirement name is truncated if it<br />
contains more that 64 characters.<br />
In the new Document Factory, all line<br />
returns are removed from the validation<br />
procedure in the resulting document.<br />
The new Document Factory does not<br />
remember form data, such as a user's<br />
password, if the previous operation<br />
failed.<br />
14 | CaliberRM <strong>2008</strong> Release Notes
Category<br />
CaliberRM DocFactory<br />
CaliberRM DocFactory<br />
CaliberRM DocFactory<br />
Change Request Number<br />
41810<br />
41780<br />
41172<br />
Description<br />
Unable to use more than one<br />
$REQTREE command in Document<br />
Factory reports.<br />
When you start the new Document<br />
Factory from within CaliberRM <strong>2008</strong>, it<br />
does not save the user name and<br />
password even though it appears to<br />
save them.<br />
The new Document Factory does not<br />
return any requirements if the<br />
requirement type is more than 64<br />
characters in length.<br />
Resolved Issues for Patch 7<br />
The following table identifies issues that have been resolved by Patch 7 for CaliberRM <strong>2008</strong> WW release.<br />
Category<br />
CaliberRM Client/Server<br />
CaliberRM DocFactory<br />
CaliberRM Datamart<br />
CaliberRM DocFactory<br />
CaliberRM Client/Server<br />
CaliberRM Win32 Client<br />
CaliberRM DocFactory<br />
Change Request Number<br />
43723<br />
43719<br />
43666<br />
41957<br />
43688<br />
43690<br />
42496<br />
Description<br />
Requirement names that contain the<br />
following characters fail to publish to<br />
Quality Center.<br />
Users do not have the rights to modify<br />
the registry key to launch the old<br />
Document Factory. The registry key is<br />
based on HKEY_LOCAL_MACHINE<br />
instead of HKEY_CURRENT_USER.<br />
The Datamart -update command<br />
does not manage deletions from the<br />
Responsibilities list.<br />
Running the new Document Factory<br />
from the CaliberRM Client produces a<br />
different result from running the new<br />
Document Factory directly from the<br />
executable. Baseline information is<br />
ignored in the new Document Factory<br />
template when it is run from the client.<br />
The requirement description is affected<br />
when the font family or font is changed<br />
in Internet Explorer (IE). However, if the<br />
font family and size are not defined<br />
within the HTML code, they are<br />
reflected in the requirement's<br />
description when you change the IE<br />
settings.<br />
Project descriptions are printed<br />
incorrectly.<br />
After the new Document Factory<br />
generates a document, it does not<br />
CaliberRM <strong>2008</strong> Release Notes | 15
Category<br />
CaliberRM Win32 Client<br />
CaliberRM DocFactory<br />
Change Request Number<br />
43736<br />
43692<br />
Description<br />
prompt the user to open the resulting<br />
XML or DOC file.<br />
Exporting a large matrix to XML causes<br />
it to crash.<br />
Incorrect focus cycle among GUI input<br />
fields on the wizard pages of the<br />
Document Factory.<br />
Resolved Issues for Patch 6<br />
The following table identifies issues that have been resolved by Patch 6 for CaliberRM <strong>2008</strong> WW release.<br />
Category<br />
CaliberRM Client/Server<br />
CaliberRM Client/Server<br />
CaliberRM Client/Server<br />
CaliberRM Client/Server<br />
CaliberRM Client/Server<br />
CaliberRM Client/Server<br />
CaliberRM Client/Server<br />
CaliberRM SDK<br />
CaliberRM DocFactory<br />
Change Request Number<br />
43596<br />
43562<br />
43518<br />
43517<br />
43484<br />
43342<br />
41327<br />
43542<br />
43703<br />
Description<br />
Data inconsistencies are encountered<br />
from concurrent Requirements Grid<br />
modifications.<br />
CaliberRM hangs when defining a<br />
numeric filter for a grid.<br />
When you right-click a trace and choose<br />
properties on the UDA page, the UDAs<br />
for the target requirement are not visible<br />
when using a newer database.<br />
A Last Transaction<br />
Incomplete message is displayed<br />
on the Traceability page when the<br />
requirement version is not from the<br />
current baseline.<br />
When using the Customer database,<br />
one of the multiple Requirements Grids<br />
crashes when launched in parallel. If a<br />
timeout exception from the server<br />
already exists, the client must request<br />
the data again.<br />
A message states that requirements<br />
have been deleted when they have not<br />
created a new message, most likely<br />
because it was reusing an existing<br />
message not intended for this use.<br />
Hyperlinks to files on a server do not<br />
work on save.<br />
Java API can perform only the mapping<br />
of requirements, not unmapping.<br />
In the new Document Factory,<br />
requirements with date and multitext<br />
line UDAs are not generated properly<br />
in reports.<br />
16 | CaliberRM <strong>2008</strong> Release Notes
Resolved Issues for Patch 5<br />
The following table identifies issues that have been resolved by Patch 5 for CaliberRM <strong>2008</strong> WW release.<br />
Category<br />
CaliberRM Client<br />
CaliberRM Server<br />
CaliberRM Server<br />
Change Request Number<br />
43344<br />
43118<br />
43317<br />
Description<br />
When you choose Tools ➤ Options ➤<br />
Spelling to open the Spelling page in<br />
a non-English CaliberRM client, the<br />
client crashes with a debug error.<br />
Deleted traces between a file object and<br />
a requirement that is present in a<br />
non-current baseline appear in the<br />
Traceability Matrix.<br />
Default values for options in the Versant<br />
file profile.be need to be updated.<br />
Resolved Issues for Patch 4<br />
The following table identifies issues that have been resolved by Patch 4 for CaliberRM <strong>2008</strong> WW release.<br />
Category<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Server<br />
CaliberRM Server<br />
CaliberRM SDK<br />
Change Request Number<br />
42957<br />
42560<br />
43077<br />
42516<br />
43163<br />
43167<br />
Description<br />
WorkItem properties do not open for<br />
VSTS <strong>2008</strong> traces. Properties have<br />
been re-referenced to correct the<br />
Microsoft Visual Studio Team System<br />
<strong>2008</strong> DLLs based on the location of the<br />
installation.<br />
The status and project paths of traces<br />
to StarTeam items are not refreshed<br />
when the items are moved or deleted.<br />
Because this fix requires StarTeam SDK<br />
changes, it is recommended that you<br />
upgrade to StarTeam SDK 10.0.60 or<br />
10.1.<br />
When a StarTeam item is checked out,<br />
the status of the trace must be changed<br />
to suspect. The behavior of the<br />
checkout operation is changed in the<br />
CaliberRM client to change the trace<br />
status to suspect.<br />
When the MPX component for <strong>Borland</strong><br />
Search Server is enabled, an error<br />
occurs if the MPX server is installed on<br />
a different machine.<br />
When a trace to Team System Test is<br />
removed through Win32 Client, an error<br />
is displayed for longer strings.<br />
SDK fails to save baseline information.<br />
This issue was introduced in<br />
CaliberRM <strong>2008</strong> Release Notes | 17
Category<br />
CaliberRM SDK<br />
Change Request Number<br />
42919<br />
Description<br />
Hotfix34c-2006.<br />
BaseLineTreeNode object is<br />
converted back to UTF8 when<br />
communicating with the server.<br />
CaliberRM SDK throws various types<br />
of exceptions due to data corruption or<br />
the mishandling of data while parsing.<br />
The issue was fixed by converting the<br />
xHTML/XML string into an XML<br />
document while parsing and validating<br />
requirement descriptions.<br />
Resolved Issues for Patch 3<br />
The following table identifies issues that have been resolved by Patch 3 for CaliberRM <strong>2008</strong> WW release.<br />
Category<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Server<br />
CaliberRM Server<br />
Change Request Number<br />
41351<br />
42713<br />
42860<br />
42864<br />
41469<br />
42751<br />
42867<br />
42087<br />
42358<br />
Description<br />
The cursor jumps to the top of the<br />
paragraph after pasting text into a table.<br />
The Import from Word function fails<br />
when using MS Office 2007. When<br />
importing from Word, the import fails<br />
when using the plain-text option,<br />
resulting in an orphaned<br />
Winword.exe.<br />
The Datamart outputs unnecessary<br />
information.<br />
The time format is inconsistent when<br />
running Document Factory.<br />
Requirement Viewer takes a long time<br />
to load requirement information based<br />
on change request management (CRM).<br />
CaliberRM license status is Missing<br />
after it is assigned from the <strong>Borland</strong><br />
License Server page.<br />
The -depth command does not<br />
update for MS SQL server and Oracle<br />
server usage. Only MS Access has<br />
update information for -depth.<br />
Customers requested to remove<br />
Hotfix54-2006 behavior because they<br />
want to revert the earlier request to<br />
create the same Hotfix.<br />
Performance decreases when using<br />
<strong>2008</strong> filters to filter subrequirements of<br />
requirement IDs within a range.<br />
18 | CaliberRM <strong>2008</strong> Release Notes
Category<br />
CaliberRM Server<br />
CaliberRM Server<br />
CaliberRM SDK<br />
Change Request Number<br />
42837<br />
42882<br />
41285<br />
Description<br />
Unable to log on to CaliberRM by using<br />
LDAP if the password contains a<br />
localized character, such as é or à.<br />
CaliberRM SDK <strong>2008</strong> fails to retrieve<br />
traces for project.<br />
<strong>Borland</strong> Search continually fails with the<br />
message<br />
java.lang.OutOfMemoryError:<br />
Java heap space.<br />
Resolved Issues for Patch 2<br />
The following table identifies issues that have been resolved by Patch 2 for CaliberRM <strong>2008</strong> WW release.<br />
Category<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
Change Request Number<br />
41141<br />
41797<br />
42457<br />
42458<br />
42627<br />
42648<br />
Description<br />
Limit the number of traces output in the<br />
Datamart extraction to a set number or<br />
level.<br />
Fails when running an extraction with<br />
the -update command with Datamart.<br />
Datamart -update option fails while<br />
extracting large volume of requirements.<br />
Datamart -update option does not<br />
use paging.<br />
Datamart -update option does not<br />
properly export the Responsibilities<br />
list.<br />
When performing maintenance on<br />
various projects and baselines, the error<br />
last transaction<br />
incomplete is thrown.<br />
Resolved Issues for Patch 1<br />
The following table identifies issues that have been resolved by Patch 1 for CaliberRM <strong>2008</strong> WW release.<br />
Category<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
Change Request Number<br />
40779<br />
41705<br />
41737<br />
Description<br />
Sorting does not function properly on<br />
the Add Baseline Signatories dialog<br />
box.<br />
Deleting the current baseline version of<br />
a requirement does not mark the<br />
attributes as deleted.<br />
When traces are deleted, new versions<br />
of trace objects are created.<br />
CaliberRM <strong>2008</strong> Release Notes | 19
Category<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
Change Request Number<br />
41865<br />
41943<br />
42034<br />
42171<br />
42215<br />
42330<br />
42402<br />
42352<br />
42404<br />
42442<br />
42293<br />
41969<br />
40321<br />
41711<br />
42195<br />
Description<br />
UDA issues occur when making<br />
changes to the requirement baseline or<br />
to the requirement type.<br />
The new Document Factory cannot<br />
handle German special characters.<br />
When using Datamart to extract history,<br />
the changes in requirements relating to<br />
multiple-selection UDAs are not<br />
exported appropriately.<br />
Deleted users are unavailable for<br />
assignment to Project Administrator<br />
status.<br />
Creation of Caliber requirements in<br />
Together 2007 SP1 fails.<br />
The new Document Factory does not<br />
embed images and other objects into<br />
the resulting document. Instead, it<br />
creates them as links.<br />
HTML code is displayed in QC<br />
Integration property windows.<br />
When Document Factory fails from the<br />
command-line interface, a<br />
winword.exe orphan is left running<br />
as a process.<br />
Document Factory $Begin_List<br />
$End_List repeats the first<br />
reference.<br />
While launching a new Document<br />
Factory from CaliberRM Win32 Client,<br />
the server credentials are not passed<br />
to the Document Factory client.<br />
The Document Factory keywords do not<br />
output glossary terms in alphabetical<br />
order.<br />
The new Document Factory<br />
experiences usability issues in default<br />
server credentials, user names, error<br />
handling, and the display behavior of<br />
windows.<br />
Some German characters do not appear<br />
properly in the Web client.<br />
Cannot view images in the new<br />
Document Factory output.<br />
Datamart configuration does not support<br />
the exporting of all baselines when the<br />
All Projects option is selected.<br />
20 | CaliberRM <strong>2008</strong> Release Notes
Category<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Client<br />
CaliberRM Server<br />
CaliberRM Server<br />
CaliberRM Server<br />
CaliberRM Server<br />
Change Request Number<br />
41790<br />
41975<br />
42020, 41050, 41679<br />
41951<br />
42350<br />
41899<br />
42137<br />
42451<br />
40441<br />
42131<br />
42159<br />
42014<br />
41797<br />
23436<br />
42087<br />
42140<br />
Description<br />
Datamart extraction fails when<br />
SQLLDR's input file exceeds 2 GB.<br />
Datamart Configurator does not properly<br />
edit saved configuration files with more<br />
than 200 projects.<br />
Trace Set status is not displayed in<br />
Win32, Document Factory, Datamart,<br />
and Web Client.<br />
Exclude external traces for Export to<br />
Access function.<br />
Cannot filter on the User<br />
multiple-selection listbox UDA in the<br />
Traceability Matrix.<br />
If you filter by responsibility in the <strong>2008</strong><br />
Requirements Grid, no requirements<br />
are returned.<br />
New or modified UDAs do not appear<br />
for most requirements. The<br />
Requirements Grid returns incorrect<br />
lists.<br />
The Requirements Grid and the<br />
CaliberRM Client display different UDA<br />
dates.<br />
Grid export to CSV defect. The<br />
Description text box is truncated to 256<br />
characters in Requirements Grid Print<br />
Preview.<br />
CaliberRM Client crashes when editing<br />
multiple requirement fields in the<br />
Requirements Grid while requirements<br />
are locked by other users.<br />
When adding a glossary term to a<br />
glossary that already exists, the client<br />
does not refresh appropriately.<br />
Caliber Connection to HP Quality<br />
Center 9.2 over HTTPS. Caliber <strong>2008</strong><br />
Publish to Quality Center / Test Wizard<br />
over HTTPS is not working.<br />
Regression issues with Datamart’s<br />
-update option.<br />
Error message while deleting a<br />
requirement when the audit log is<br />
enabled.<br />
Read-only users can shift requirements.<br />
Performing baseline maintenance on a<br />
newly created baseline throws a Last<br />
transaction incomplete error.<br />
CaliberRM <strong>2008</strong> Release Notes | 21
Category<br />
CaliberRM Web Client<br />
VS 2005 Integration<br />
Change Request Number<br />
42255<br />
42032<br />
Description<br />
German umlauts are not displayed<br />
appropriately in the CaliberRM <strong>2008</strong><br />
Web Client.<br />
Visual Studio 2005 integration does not<br />
release the logon credentials.<br />
Resolved Issues for <strong>2008</strong><br />
The following table identifies issues that have been resolved in CaliberRM <strong>2008</strong> WW release.<br />
Hot Fix<br />
Hot Fix 01C<br />
Hot Fix 01C<br />
Hot Fix 01C<br />
Hot Fix 01C<br />
Hot Fix 01C<br />
Hot Fix 01C<br />
Hot Fix 01C<br />
Hot Fix 01C<br />
Hot Fix 2<br />
Hot Fix 2, 3<br />
Change Request Number<br />
41815<br />
41770<br />
41812<br />
41205<br />
41457<br />
41502<br />
40811<br />
41487<br />
41850<br />
21768<br />
Description<br />
The Caliber Datamart project fails for<br />
large databases. The job hangs for<br />
approximately an hour and then fails<br />
with a Get requirement tree<br />
error or a getserver error.<br />
Document Factory does not take into<br />
account any of the changes to the<br />
default security profile.<br />
Users who are not part of the Admin<br />
group are unable to run Document<br />
Factory. They receive a User not<br />
authorized message.<br />
Datamart extraction fails.<br />
Datamart needs to utilize the parameter<br />
-SQLLDR during Oracle extractions to<br />
improve performance.<br />
The -update parameter does not<br />
function when used with Oracle. Its<br />
usage causes a failure without building<br />
the database.<br />
Document Factory stops with a Value<br />
out of range message.<br />
SCM traces the output ERROR:<br />
Invalid ID instead of the traced-to<br />
object's name in Document Factory.<br />
The Requirements Grid filter returns<br />
incorrect results when filtering on the<br />
description.<br />
When using the Paste Special<br />
functionality to copy a requirement with<br />
traces, the suspect statuses of the<br />
traces are lost.<br />
22 | CaliberRM <strong>2008</strong> Release Notes
Resolved Issues for 2006<br />
The following table identifies issues that have been resolved in CaliberRM 2006 WW release.<br />
Hot Fix<br />
Hot Fix 16<br />
Hot Fix 17<br />
Hot Fix 18<br />
Hot Fix 18<br />
Hot Fix 18<br />
Hot Fix 19, 20<br />
Hot Fix 20<br />
Hot Fix 22, 22c<br />
Hot Fix 24<br />
Hot Fix 24<br />
Hot Fix 25<br />
Hot Fix 26<br />
Hot Fix 27c<br />
Hot Fix 28c<br />
Hot Fix 29c<br />
Hot Fix 31c<br />
Hot Fix 32c<br />
Change Request Number<br />
40728<br />
40811<br />
23417<br />
23399<br />
22479<br />
40929<br />
22479<br />
41205<br />
40538<br />
40538<br />
40811<br />
40538<br />
41457<br />
41326<br />
41487<br />
41502<br />
41577<br />
Description<br />
CaliberRM CRMDiag Tool not included<br />
in v<strong>2008</strong>.<br />
CaliberRM CRMDiag Tool not included<br />
in v<strong>2008</strong>.<br />
CaliberRM SDK application error.<br />
CaliberRM SDK application error.<br />
CaliberRM SDK application error.<br />
Traceability Matrix shows requirements<br />
for projects to which the user does not<br />
have access.<br />
CaliberRM SDK application error.<br />
Datamart Extraction failing.<br />
When a requirement is deleted in 2006,<br />
it appears to be left in a hanging status<br />
but still appears in searches, Document<br />
Factory reports, and stopping-baseline<br />
abilities.<br />
After deleting a requirement, unread<br />
discussions still appear. The owner of<br />
the discussion appears as<br />
?|?.<br />
CaliberRM 2006. Docfactory.exe<br />
version 9.0.906.0.<br />
The Traceability Matrix displays<br />
requirements for projects to which the<br />
user does not have access.<br />
Datamart does not utilize the parameter<br />
-SQLLDR during Oracle extractions.<br />
When importing from Word, a<br />
requirement name is truncated to 64<br />
characters even though the CaliberRM<br />
Client supports requirements with<br />
names of 128 characters.<br />
SCM traces the output ERROR:<br />
Invalid ID instead of the traced-to<br />
object's name in Document Factory.<br />
The usage of the -update parameter<br />
with Oracle results in a failure without<br />
building the database.<br />
The map-requirement functionality<br />
cannot be used with the SDK (applies<br />
CaliberRM <strong>2008</strong> Release Notes | 23
Hot Fix<br />
Hot Fix 33c<br />
Hot Fix 34c<br />
Hot Fix 37<br />
Hot Fix 38c<br />
Hot Fix 38c<br />
Hot Fix 39c<br />
Hot Fix 40<br />
Hot Fix 41c<br />
Hot Fix 42c<br />
Hot Fix 42c<br />
Hot Fix 43c<br />
Hot Fix 44c<br />
Hot Fix 45c<br />
Change Request Number<br />
41595<br />
41261<br />
41594<br />
41674<br />
41619<br />
41626<br />
41681<br />
40321<br />
41664<br />
41741<br />
41626<br />
41351<br />
41910<br />
Description<br />
only to COM-based code, such as C#<br />
and VB.NET).<br />
Datamart-to-SQL extraction fails,<br />
throwing an INVALID_QUERY(0)<br />
error on the appropriate requirement.<br />
HTML returned from a requirement<br />
object contains inappropriate UTF-8<br />
characters for symbols pasted from<br />
Word documents, such as curly quotes,<br />
minus signs, and bullets.<br />
CaliberRM does not delete projects<br />
appropriately.<br />
When using the Traceability Matrix with<br />
filters, CaliberRM returns a<br />
GeneralObject message.<br />
The User multiple-selection listbox<br />
displays deleted users.<br />
When you move a value within a<br />
multiple-selection listbox, the filter within<br />
the Traceability Matrix breaks.<br />
CaliberRM displays duplicate<br />
requirement versions and traces.<br />
Some German and unicode characters<br />
do not appear properly in the Web<br />
Client.<br />
No pop-up messages, such as object<br />
does not exist, should occur<br />
when running Datamart extractions.<br />
This feature is designed as a<br />
command-line tool for use with<br />
automated scripts. As such, it does not<br />
feature any GUI components.<br />
Information messages should be logged<br />
to the screen and/or log files with more<br />
detailed information.<br />
After applying Hotfix 33c (extractor), the<br />
Direction text box in the TRACE table<br />
contains unreadable values.<br />
When you move a value within a<br />
multiple-selection listbox, the filter within<br />
the Traceability Matrix breaks.<br />
The cursor jumps to the top of the<br />
paragraph after pasting text into a table.<br />
Using the $RGVFILE tag in Document<br />
Factory to filter requirements on<br />
Hierarchy# returns incorrect results.<br />
24 | CaliberRM <strong>2008</strong> Release Notes
Updated Files in Patch<br />
This section describes files that are updated in the current patch of CaliberRM <strong>2008</strong> WW release.<br />
CaliberRM Client<br />
The following files, which are listed relative to the installation directory, are updated in CaliberRM Client:<br />
• de\CaliberRMRes.dll<br />
• en\CaliberRMRes.dll<br />
• fr\CaliberRMRes.dll<br />
• ja\CaliberRMRes.dll<br />
• de-DE\DocFactory2.resources.dll<br />
• fr-FR\DocFactory2.resources.dll<br />
• ja-JP\DocFactory2.resources.dll<br />
• de-DE\QueryBuilder.Resources.dll<br />
• fr-FR\DocFactory2.resources.dll<br />
• ja-JP\DocFactory2.resources.dll<br />
• Traceability Addins\QCIntegrationAddin.dll<br />
• Traceability Addins\StarTeamAddIn.exe<br />
• <strong>Borland</strong>.CaliberRM.DocFactory.Parser.dll<br />
• CaliberAddinBridge.dll<br />
• CaliberCommon.dll<br />
• CaliberEvent.dll<br />
• CaliberFACommon.dll<br />
• CaliberRM.exe<br />
• CaliberRMAdmin.exe<br />
• CaliberRMSDK100.dll<br />
• CaliberRMSDK100.NET.dll<br />
• CaliberRMViewer.exe<br />
• CaliberSpelling.dll<br />
• Configurator.exe<br />
• CRMSBToolbarIF.dll<br />
• DocFactory.exe<br />
• DocFactory2.exe<br />
• DocFactory2.exe.config<br />
• Export.exe<br />
• Extractor.exe<br />
• MercuryPublisher.exe<br />
• QueryBuilder.dll<br />
• readme_en.html<br />
• TestWizard.exe<br />
• XMLCommonEx.dll<br />
CaliberRM Server<br />
The following files, which are listed relative to the installation directory, are updated in CaliberRM Server:<br />
CaliberRM <strong>2008</strong> Release Notes | 25
• bin\caliber_srv.exe<br />
• lib\dbmgr.exe<br />
• lib\profile.be<br />
CaliberRM SDK<br />
The following files, which are listed relative to the installation directory, are updated in CaliberRM SDK:<br />
• bin\CaliberCommon.dll<br />
• bin\CaliberRMSDK100.dll<br />
• lib\CaliberRMSDK100.jar<br />
• lib\CaliberRMSDK100.NET.dll<br />
• lib\CaliberRMSDK4COM100.jar<br />
• lib\jvb.dll<br />
Known Issues<br />
This section identifies known issues with the various CaliberRM components.<br />
CaliberRM Server<br />
The released software download displays Unknown Publisher instead of is signed by <strong>Borland</strong>. For<br />
more information, visit http://support.microsoft.com/kb/922225/en-us#appliesto.<br />
MPX users: When you upgrade your server from CaliberRM 2005 Release 2, MPX events are disabled by<br />
default. If you used MPX events with your CaliberRM 2005 Release 2 Server and are planning to continue<br />
using MPX events, click Enable MPX Events on the MPX Configuration dialog box. This option requires<br />
StarTeam Message Broker.<br />
Evaluation users: If you reinstall a trial version of CaliberRM <strong>2008</strong> Server on a Windows XP machine, your<br />
installation might fail. To prevent failure, stop the SQM Monitor and SQM Database Windows Services before<br />
reinstalling.<br />
During the upgrade, the CaliberRM Server settings in the Control Panel applet are lost. Save these settings<br />
prior to upgrading and restore them afterward.<br />
When attempting to install the CaliberRM Server from a remote location, the message Error 1706: no<br />
valid source could be found appears. Avoid this message by running the installer locally from the<br />
server machine.<br />
<strong>Borland</strong> License Server users: The per-user license assignment (named or concurrent) needs to be manually<br />
restored after an upgrade. If your CaliberRM server is configured to use <strong>Borland</strong> License Server (BLS) licenses<br />
only, change the Admin user license type to BLS to log on to the CaliberRM Server while using the CaliberRM<br />
Client as Admin. In this case, connections of the Admin user to the CaliberRM Server by using the CaliberRM<br />
Client are counted by the BLS Server against the available licenses. The type of license acquired (named or<br />
concurrent) depends on the type of the particular BLS license assigned to the Admin user.<br />
CaliberRM Windows Client<br />
This section identifies known issues with CaliberRM Windows Client.<br />
26 | CaliberRM <strong>2008</strong> Release Notes
Localization<br />
Only some of the strings have been localized.<br />
The spell checker reports contracted, non-English words, such as l'eau, as misspelled.<br />
Dictionary<br />
When CaliberRM Client is launched for the first time, it tries to create dictionary files in the directory Program<br />
files by default. This attempt might fail if the user does not possess write access to Program files.<br />
Documentation<br />
On Windows XP SP2, choosing Help ➤ Help Content sometimes generates an error. To avoid this error,<br />
perform the following steps:<br />
1. Open Internet Explorer.<br />
2. Choose Tools ➤ Internet Options.<br />
3. Click the Advanced tab.<br />
4. Under Security options, click Allow active content to run in files on My Computer.<br />
5. Click OK.<br />
For more information, visit http://support.microsoft.com/kb/843017.<br />
The documentation lacks information about tracing files. To trace files, perform the following steps:<br />
1. On the Traceability Modification dialog box, click the Files tab.<br />
2. Click Browse, select the file to or from which to trace, and click OK.<br />
3. Click Trace From or Trace To, to create the trace, as appropriate.<br />
4. Click Save Changes.<br />
Help<br />
The topic Importing Requirements from Microsoft Word states that you can import requirement names with<br />
delimiters or keywords. Instead, the topic needs to state that you can import requirement descriptions only<br />
with delimiters and keywords.<br />
The Datamart topic launched from the Configurator wizard contains an inappropriate path for launching the<br />
Configurator. The appropriate path is <strong>Borland</strong> CaliberRM ➤ Administration ➤ Datamart.<br />
Windows Client<br />
Inconsistent behavior might result when inserting objects. JPEG objects are displayed by their file names,<br />
while BMP files are shown as images. This behavior is consistent with OLE behavior in MS Word.<br />
Traces added by previous users are visible and available, even after logging off, to a different user who might<br />
not possess the SCTM rights to view a particular project from which the traces were added.<br />
In the case of the trace-to-SCTM artifact, the trace filter for the Requirements Grid does not work for remote<br />
traces. When you select these filters, the requirements with remote traces are not displayed.<br />
On Japanese Vista, some dialog boxes appear too big, and some labels appear too small. This effect is due<br />
to the change in the default font from MS UI Gothic to Meiryo. To return dialog boxes to their normal sizes,<br />
change the window design from Windows Vista Basic to Windows Standard.<br />
Importing an exported project into a new project generates multiple, consecutive Object does not exist<br />
messages, and the import is not successful. A second run of the import succeeds.<br />
CaliberRM <strong>2008</strong> Release Notes | 27
When you use the CaliberRM SDK to create a user, the User Can Manage Glossary Terms permission<br />
is enabled by default. No SDK option exists to deselect this permission. However, if this permission needs to<br />
be disabled, you can disable it on the Security page of the CaliberRM Administrator.<br />
Do not use surrogate pair characters, which the CaliberRM SDK does not support surrogate. Clients that use<br />
the SDK cannot process surrogate pair characters appropriately.<br />
If you do not have the corresponding OLE object software installed, the Edit object command, without<br />
warning, does not open the OLE object software.<br />
The Export to MS Access function does not include StarTeam traces. Use the Datamart extractor to MS Access.<br />
Mercury QC traces are not exported to MS Access when you choose File ➤ Export to Access. Consequently,<br />
you must log on to QC before initiating the Export to Access function.<br />
Traces to deleted requirements are displayed as Retrieving on the Traceability page.<br />
Rows and columns in the Traceability Matrix cannot display non-requirement objects without displaying some<br />
requirements. To avoid this issue, use ID equals as a filter criteria to display one<br />
requirement along with the external objects.<br />
Saved traceability matrices do not persist the traceability matrix layout or the user filter.<br />
In user baselines, the message Retrieving... is displayed instead of the trace to requirement deleted in<br />
current baseline.<br />
Due to the versioning of traces, creating some baselines might take longer in the current version than in<br />
CaliberRM 2005.<br />
Traceability cannot be included when pasting requirements after a copy. Instead, use the Paste Special<br />
functionality.<br />
Document Factory<br />
Due to a localization issue, the Document Factory's logging directory is changed from C:\Documents and<br />
settings\Local Settings\Application Data\<strong>Borland</strong>\CaliberRM\Log to C:\Documents and<br />
settings\\Local Settings\Application Data\<strong>Borland</strong> Software<br />
Corporation\<strong>Borland</strong>\CaliberRM\Log.<br />
If you are generating Document Factory with requirement trace-to-SCTM linking service, the external trace<br />
does not appear in the document.<br />
When running a previous version of Document Factory (with MS office 2000), you must click the Multiple<br />
option instead of Once to replace the keywords properly for all the records.<br />
In new Documentation Factory for versions 2003 and 2007, an Invalid Query message appears during<br />
document generation when the $filter command, which contains the old Document Factory syntax, is used<br />
in the template.To avoid this message, create and save a new filter on the server, and then modify the $filter<br />
tag with new filter criteria.<br />
The new Documentation Factory for versions 2003 and 2007 does not support filtering in SQL format.<br />
Consequently, you must create and save a new filter on the server, and then modify the $filter tag with<br />
new filter criteria.<br />
The Document Factory option in the Requirements Grid is not available when the grid displays a single<br />
requirement. To make this option available, display the grid with multiple requirements and manually select<br />
the requirement.<br />
The current baseline is specified with $BASELINE{Current Baseline} instead of $BASELINE{Current}.<br />
28 | CaliberRM <strong>2008</strong> Release Notes
Datamart<br />
Due to new enhancements, such as the versioning of traces, a Datamart extraction takes more time than it<br />
did with CaliberRM 2005.<br />
<strong>Borland</strong> Search<br />
Choosing Tools ➤ <strong>Borland</strong> Search does not open a Web browser if one is not already open. As a result, you<br />
must open a browser before choosing this menu item.<br />
Estimate Professional<br />
Clicking Close to close the project browser generates an error. To avoid this error, choose the menu item that<br />
allows you to close the project browser.<br />
The Import Project Data topic in the EstimatePro Help erroneously claims that MS Project 97 is supported.<br />
StarTeam Integration<br />
When opening several views on different tabs on the StarTeam page on the Traceability Modification dialog<br />
box, you might receive java.lang.Out.Of.Memory... messages. To avoid these messages, add an<br />
options=-Xmx256m or options=-Xmx512m line to the file StarTeamSDK10.ini, which is located in<br />
C:\Program Files\<strong>Borland</strong>\StarTeamSDK<strong>2008</strong>\Lib by default.<br />
An Out of memory message might appear when attempting to view the StarTeam trace history.<br />
Mercury Quality Center Integration<br />
CaliberRM 2006 to <strong>2008</strong> have default values for configuration files after upgrading in Mercury QC.<br />
If you use a non-English CaliberRM client with an English version of QC, characters other than English do not<br />
appear correctly in QC. To avoid this issue, install the corresponding QC language pack.<br />
Custom fields that are created in QC are also displayed in the Publish to Quality Center wizard, even though<br />
these fields are not modified when requirements are published.<br />
SilkCentral Test Manager Integration<br />
CaliberRM <strong>2008</strong> does not support SCTM 8.6 for synchronization.<br />
On the Traceability page, the project/ID text box lists the test type instead of its location.<br />
If a user is not connected to the SilkCentral database, attempting to create a trace to a SilkCentral test definition<br />
from the Traceability page generates an error. To avoid this error, connect to SilkCentral first.<br />
SCM Integration<br />
A trace to a file in Rational ClearCase does not appear on the Traceability page.To view a trace to a ClearCase<br />
file, refresh the Traceability page after creating the trace.<br />
CaliberRM SDK Installation<br />
CaliberRM SDK installation features a The system administrator has set policies to prevent<br />
this installation error from the CaliberRM SDK installer as well as the CaliberRM Server Install Caliber<br />
SDK option with an admin account. When installing CaliberRM SDK with the main installer (server and client),<br />
the running installer launches the CaliberRM SDK installer (.msi). This feature, known as nested installation<br />
or concurrent installation, has been deprecated because of the problems it causes for users.<br />
To avoid this issue, remove HKEY_CLASSES_ROOT\Installer\Products.<br />
CaliberRM <strong>2008</strong> Release Notes | 29
CaliberRM for Eclipse<br />
The Requirements Grid slows down when viewing a large number of requirements. It is recommended that<br />
you use the document view instead.<br />
The Compare Baselines report is difficult to read when using the default width. Use the Windows Client to<br />
compare baselines.<br />
The options to trace to <strong>Borland</strong> StarTeam, <strong>Borland</strong> Together, <strong>Borland</strong> Silk, or Mercury QC do not allow users<br />
to create traces. Contact support to install the necessary add-ins.<br />
When MPX is enabled and the requirement tree is refreshed by MPX events, the current cursor position is<br />
lost. To avoid this situation, turn off MPX events on the Logon dialog box.<br />
Navigating to non-requirement software artifacts, such as <strong>Borland</strong> StarTeam elements, from a requirement<br />
might generate an error. It is recommended that you use the Windows Client to view these traces.<br />
After a refresh, the requirement navigator displays requirements as locked even though they are not locked<br />
and can be edited.<br />
In both Eclipse 3.2 and 3.3, when you view the Traceability page of a requirement with an SCTM trace attached<br />
to it in SCTM, the SCTM trace is not displayed. However, when you view the same requirement in CaliberRM,<br />
the SCTM trace is displayed.<br />
CaliberRM for Microsoft Visual Studio <strong>2008</strong> / Visual Studio<br />
Team Foundation <strong>2008</strong><br />
In Visual Studio <strong>2008</strong> integration, when you click Refresh on the CaliberRM Explorer toolbar, an empty message<br />
opens, and the Refresh command does not work. To close the empty message, click the left button. To refresh<br />
your CaliberRM project, either click Refresh after any requirements are opened or restart Visual Studio.<br />
In VSTS <strong>2008</strong> integration, changing the direction of two traces and saving them from the Traceability<br />
Modification dialog box results in an infinite hourglass prompt. Additionally, only one trace is displayed on<br />
the Traceability page. Closing the requirement and opening it again displays the appropriate traces.<br />
In Visual Studio <strong>2008</strong> integration, Visual Studio hangs when a CaliberRM project is removed. When multiple<br />
baselines for the same CaliberRM project are added to CaliberRM Explorer, Visual Studio sometimes hangs<br />
when you remove a project. This issue occurs only when requirements are opened in the Editor pane. To<br />
avoid this issue, close all requirements before removing a project.<br />
In Visual Studio <strong>2008</strong> Integration, when opening CaliberRM Explorer on Visual Studio <strong>2008</strong>, a package load<br />
error occurs. CaliberRM Explorer is not displayed. In VSTS <strong>2008</strong> Integration, when connecting to CaliberRM<br />
Server from Team Explorer on Visual Studio <strong>2008</strong>, the request never finishes. Both problems are caused by<br />
a missing J# library. As a result, users must install the J# redistributable separately because Visual Studio<br />
<strong>2008</strong> no longer includes J#. It is recommended that you download Microsoft Visual J# ® 2.0 Redistributable<br />
Package, Second Edition (x86) from<br />
http://www.microsoft.com/downloads/details.aspx?FamilyId=E9D87F37-2ADC-4C32-95B3-B5E3A21BAB2C<br />
and install it before installing Visual Studio <strong>2008</strong> or VSTS <strong>2008</strong> Integrations.<br />
In Visual Studio Team foundation 2005 and <strong>2008</strong>, while uninstalling CaliberRM for Team Foundation Server<br />
(TFS Integration), the uninstaller fails to unregister the CaliberRM entry. To remove the CaliberRM entries<br />
manually from the Microsoft Visual Studio Team Foundation Server 2005 (TFS 2005), perform the following<br />
steps:<br />
1. Run the command TFSReg with the /D switch before uninstalling, as the following example shows.<br />
30 | CaliberRM <strong>2008</strong> Release Notes
TFSReg /D "C:\Program Files\<strong>Borland</strong>\CaliberRM For Team Foundation<br />
Server\Registration.xml" TfsIntegration<br />
TFSReg resides in the \Tools folder.<br />
Note: If you have uninstalled TFS Integration but cannot locate the file Registration.xml, contact<br />
support or reinstall TFS Integration.<br />
2. Uninstall TFS Integration.<br />
To remove the CaliberRM entries manually from Microsoft Visual Studio Team Foundation Server <strong>2008</strong> (TFS<br />
<strong>2008</strong>), perform the following steps:<br />
1. Run the command TFSReg with the /EXPORT switch, as the following example shows.<br />
TFSReg /EXPORT c:\temp\Registration.xml TfsIntegration<br />
TFSReg resides in the \Tools folder.<br />
2. Open the exported file.<br />
3. Search for the CaliberRM Type element.<br />
4. Remove the element, including the CaliberRM Type element, and save the file.<br />
5. Run the command TFSReg with the /OVERWRITE switch, as the following example shows.<br />
TFSReg /OVERWRITE c:\temp\Registration.xml TfsIntegration<br />
The following features of VS/VSTS<strong>2008</strong> integration do not function properly on Vista:<br />
• Previewing in the Requirements Grid — Nothing is available for preview in the Print Preview view.<br />
• Adding multiple projects to CaliberRM Explorer — VS<strong>2008</strong> crashes.<br />
• Storing CaliberRM connection information — Users must add a CaliberRM project every time.<br />
• Viewing images — Images in descriptions are always missing.<br />
• Opening the VSTS Tests page in Traceability Modification — An error occurs while opening the test list.<br />
This error occurs because a Visual Studio or VSTS integration requires administrative privileges to proceed<br />
with these features. To avoid this error, choose Run As Administrator from the context menu when you<br />
run Visual Studio.<br />
Copy the Visibroker.Net files to the corresponding directory of the Visual Studio installation. If the user<br />
has installed Visual Studio on another drive, VSTS integration cannot connect to the CaliberRM Server even<br />
though the VSTS Integration installer is hardcoded to install the Visibroker.Net DLL files in the directory<br />
C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies. If Visual<br />
Studio is installed on a drive other than the C:\ drive, copy the Visibroker.NET files to the corresponding<br />
directory of the Visual Studio installation after the integration.<br />
In the English and Japanese versions, VSTS hangs when trying to use 'Traceability<br />
modification'>'VSTS Test tab' to add TFS Server. In the French version, VSTS <strong>2008</strong> crashes when<br />
trying to use 'Traceability modification'>'VSTS Test tab' to add TFS Server.<br />
CaliberRM for Microsoft Visual Studio 2005<br />
In VSTS 2005 and <strong>2008</strong> integration, changing the direction of two traces and saving them from the Traceability<br />
Modification dialog box results in an infinite hourglass prompt. Additionally, only one trace is displayed on<br />
the Traceability page. Closing the requirement and opening it again displays the appropriate traces.<br />
The options to trace to <strong>Borland</strong> StarTeam, <strong>Borland</strong> Together, <strong>Borland</strong> Silk, or Mercury QC do not allow users<br />
to create traces. Contact support to install the necessary add-ins.<br />
CaliberRM <strong>2008</strong> Release Notes | 31
The integration cannot connect to CaliberRM servers with Secure Sockets Layer (SSL) enabled. To overcome<br />
this obstacle, perform the following steps:<br />
1. Open the folder in which the VSTS client is installed, such as C:\Program Files\<strong>Borland</strong>\CaliberRM<br />
Client For Visual Studio Team System.<br />
2. Right-click CaliberRM SSL.crt and choose Install Certificate.<br />
3. Click Next.<br />
4. Click Next.<br />
5. Click Finish.<br />
Traceability to external software artifacts is not available.<br />
In Visual Studio 2005 integration, when you click Refresh on the CaliberRM Explorer toolbar, an empty<br />
message opens, and the Refresh command does not work. To close the empty message, click the left button.<br />
To refresh your CaliberRM project, either click Refresh after any requirements are opened or restart Visual<br />
Studio.<br />
In Visual Studio 2005 integration, Visual Studio hangs when a CaliberRM project is removed. When multiple<br />
baselines for the same CaliberRM project are added to CaliberRM Explorer, Visual Studio sometimes hangs<br />
when you remove a project. This issue occurs only when requirements are opened in the Editor pane. To<br />
avoid this issue, close all requirements before removing a project.<br />
CaliberRM for Microsoft Visual Studio Team System<br />
When you view the Traceability page of a requirement with an SCTM trace attached to it from SCTM, the<br />
SCTM trace is not displayed. However, when you view the Traceability page of the same requirement in<br />
CaliberRM, the trace is visible. This limitation exists in Microsoft Visual studio as well.<br />
After uninstalling CaliberRM for Microsoft Visual Studio, <strong>Borland</strong> CaliberRM is still displayed among the installed<br />
products on the Visual Studio splash screen.<br />
The Owner text box of some requirements is not displayed on the Details page.<br />
The integration cannot connect to CaliberRM servers with SSL enabled. To overcome this obstacle, perform<br />
the following steps:<br />
1. Open the folder in which the VSTS client is installed, such as C:\Program Files\<strong>Borland</strong>\CaliberRM<br />
Client For Visual Studio Team System.<br />
2. Right-click CaliberRM SSL.crt and choose Install Certificate.<br />
3. Click Next.<br />
4. Click Next.<br />
5. Click Finish.<br />
Traceability to external software artifacts (other than VSTS work items and tests) is not available.<br />
When tracing a requirement to a VSTS test, an inner exception error might occur. Click OK to create the<br />
trace properly.<br />
CaliberRM Web Client<br />
Web Client <strong>2008</strong> does not display existing traces to SCTM 2007 artifacts. If a trace is created to an SCTM<br />
2007 artifact by using the Win32 Client, it is not visible under the Web Client. The Web Client displays traces<br />
only to SCTM <strong>2008</strong> artifacts.<br />
Upgrading CaliberRM Web keeps the previous version installed.<br />
32 | CaliberRM <strong>2008</strong> Release Notes
On Windows XP SP2 and Windows 2003, choosing Help ➤ Help Content sometimes generates an error. To<br />
avoid this error, perform the following steps:<br />
1. Open Internet Explorer.<br />
2. Choose Tools ➤ Internet Options.<br />
3. Click the Advanced tab.<br />
4. Under Security options, click Allow active content to run in files on My Computer.<br />
5. Click OK.<br />
For more information, visit http://support.microsoft.com/kb/843017.<br />
Non-alphanumeric characters in requirement descriptions might not appear. Similarly, WMF files that are<br />
inserted into requirement descriptions might not appear properly. The hyperlinks in requirement descriptions<br />
are displayed but are not active.<br />
The Description text box of a trace to a Mercury QC object displays unreadable HTML code if the original QC<br />
object description is in HTML.<br />
Windows XP update (KB912945) and Update for Internet Explorer for Windows Server 2003<br />
64-bit Itanium Edition (KB912945) on Windows Server 2003 SP1 are incompatible with the Web<br />
Client. It is recommended that you uninstall the Microsoft update.<br />
Requirement names longer than 64 characters are not displayed.<br />
Properties of traces to Visual Studio work items are displayed incorrectly.<br />
The new Requirements Grid filter functionality works only in the Windows Client. The Web Client uses the<br />
previous Requirements Grid filter functionality for filtering.<br />
Limitations<br />
This section identifies the current limitations of the various CaliberRM components.<br />
CaliberRM Server<br />
Database administrative tasks cannot be performed by users other than the specific user who created the<br />
database. When creating the database, use a generic user ID like crmdb, which is not tied to a specific user.<br />
The following CaliberRM <strong>2008</strong> administration tools work only with the latest <strong>2008</strong> server:<br />
• CaliberRM Administrator<br />
• Datamart<br />
• RM Import<br />
• RM Export<br />
• LDAP Quick Start Manager<br />
CaliberRM Windows Client<br />
You can run the client and the server on the same machine or on different machines.<br />
HP Quality Center Version 10.0 is supported for non-versioning projects.<br />
Note: Mercury QC 10.0 for Versioning Enabled Projects using CaliberRM Mercury Publisher and CaliberRM<br />
Test Wizard tools is not yet supported.<br />
CaliberRM <strong>2008</strong> Release Notes | 33
While using Datamart to extract data to SQL Server 2000, the extraction fails if the data exceeds a row size<br />
of 8,060 bytes. This restriction is due to the limitations of SQL Server 2000. However, if the row sizes are less<br />
than 8,060 bytes, Datamart extraction is successful for SQL Server 2000.<br />
When you synchronize a requirement from SCTM, images added to the description of the requirement in SCTM<br />
are not displayed in CaliberRM after synchronization.The description pane displays only the URL of the image.<br />
To view the image, you must paste the image URL into a Web browser.<br />
The Import from Word function might not import tables properly.<br />
To install CaliberRM, users must possess write access to the directory /Program<br />
Files/<strong>Borland</strong>/CaliberRM.<br />
Information exported from the Requirement Grid into Excel is truncated at 255 characters per column.<br />
Large requirement descriptions might not appear in the grid.<br />
Pasting text from MS Word to requirement descriptions might result in lost formatting. It is recommended that<br />
you save documents as Web Page, Filtered first and then copy and paste the appropriate text in CaliberRM.<br />
The traceability diagram is not available from baselines.<br />
Information about Rational ClearCase files traced to requirements cannot be viewed in the traceability diagram.<br />
Matrix and grid filters are private to users and cannot be shared with other users.<br />
When starting CaliberRM <strong>2008</strong>, grid and matrix filters are saved on the server instead of as RGV files on the<br />
user’s computer. Clicking Save saves the column layout in an RGV file.<br />
Previous versions of Document Factory (default for MS Word 2000 and earlier) cannot use grid and matrix<br />
filters (saved on server). If users have any filters (RGV files) from CaliberRM 2006, they can still use those<br />
filters in the previous version. Additionally, the string-based filtering mechanism can be used with previous<br />
versions of Document Factory.<br />
CaliberRM 2006 filters that are saved as RGV files cannot be used in the current Document Factory (default<br />
for MS word 2003 and later).<br />
CaliberRM for Eclipse<br />
Displaying a traceability matrix for a large set of requirements might take a long time<br />
Viewing traces might generate errors. As a result, it is recommended that you view traceability in the Windows<br />
Client.<br />
Use the default MPX port in the CaliberRM Server (Control Panel) for requirements to be automatically updated.<br />
To view traceability information, the current baseline must be opened.<br />
CaliberRM for Microsoft Visual Studio 2005<br />
Document references that are set as key references are not displayed. It is recommended that you store<br />
requirement descriptions in CaliberRM.<br />
The ability to create traces to <strong>Borland</strong> StarTeam, <strong>Borland</strong> Together, <strong>Borland</strong> Silk, or Mercury QC is not available.<br />
To view traceability information, the current baseline must be opened.<br />
CaliberRM for Microsoft Visual Studio Team System<br />
Work items created in CaliberRM are not visible in Team Explorer until the user refreshes Team Explorer.<br />
Users must possess a non-empty CaliberRM authentication password.<br />
The ability to create traces to <strong>Borland</strong> StarTeam, <strong>Borland</strong> Together, <strong>Borland</strong> Silk, or Mercury QC is not available.<br />
34 | CaliberRM <strong>2008</strong> Release Notes
To view traceability information, the current baseline must be opened.<br />
CaliberRM for Microsoft Visual Studio 2003<br />
Microsoft VS 2003 integration is no longer supported because mainstream support from Microsoft ended in<br />
October <strong>2008</strong>. However, a defect in the installer displays the option to install VS 2003 integration. A future<br />
version of the CaliberRM installer will fix this bug and remove this installation option.<br />
For more information, visit http://support.microsoft.com/lifecycle/?LN=en-us&p1=3040&x=5&y=11.<br />
CaliberRM for Web<br />
Lengthy requirement descriptions might take a long time to appear.<br />
Traceability views might display errors. As a result, it is recommended that you view traceability in the Windows<br />
Client.<br />
To view traceability information, the current baseline must be opened.<br />
CaliberRM <strong>2008</strong> Release Notes | 35