CaliberRMÂ® 2008 - Borland Technical Publications

CaliberRM® 2008 

Release Notes

Borland Software Corporation 

8310 North Capital of Texas Hwy 

Building 2, Suite 100 

Austin, Texas 78731 

http://www.borland.com 

Borland Software Corporation may have patents and/or pending patent applications covering subject matter in this document. Please 

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 

any license to these patents. 

Copyright © 2009 Borland Software Corporation and/or its subsidiaries. All Borland brand and product names are trademarks or 

registered trademarks of Borland Software Corporation in the United States and other countries. All other marks are the property of 

their respective owners. 

ii

Contents 

CaliberRM 2008 Release Notes...............................................................................5 

What's New................................................................................................................................5 

Support for Third-Party Integration Tools.........................................................................5 

Enhanced Document Factory..........................................................................................5 

Access to Saved Grid and Matrix Filters in Document Factory.......................................5 

API Changes...................................................................................................................6 

URL Addressability..........................................................................................................6 

Filter Mechanism on Grid................................................................................................6 

Filter Criteria in Grid and Matrix......................................................................................6 

Status Add-In Added to Datamart...................................................................................6 

Visual Improvement to Baseline Maintenance Window...................................................6 

Help Content....................................................................................................................7 

System Requirements and Prerequisites...................................................................................7 

CaliberRM Server............................................................................................................7 

CaliberRM Windows Client..............................................................................................7 

CaliberRM for Eclipse......................................................................................................8 

CaliberRM for Microsoft Team Foundation Server...........................................................8 

CaliberRM Client for Microsoft Visual Studio Team System 2005 and 2008...................8 

CaliberRM Web...............................................................................................................9 

Software Compatibility.....................................................................................................9 

Installation and Upgrade Instructions.......................................................................................10 

CaliberRM Server..........................................................................................................10 

CaliberRM Windows Client............................................................................................10 

CaliberRM for Eclipse....................................................................................................11 

CaliberRM for Microsoft Visual Studio 2005..................................................................11 

CaliberRM for Microsoft Visual Studio 2008..................................................................11 

CaliberRM for Microsoft Visual Studio Team System....................................................11 

Resolved Issues.......................................................................................................................11 

Resolved Issues for Patch 11........................................................................................11 

Resolved Issues for Patch 10........................................................................................11 

Resolved Issues for Patch 9..........................................................................................12 



Contents | 3







Resolved Issues for 2008..............................................................................................22 

Resolved Issues for 2006..............................................................................................23 

Updated Files in Patch..................................................................................................25 

Known Issues...........................................................................................................................26 

CaliberRM Server..........................................................................................................26 

CaliberRM Windows Client............................................................................................26 

CaliberRM for Eclipse....................................................................................................30 

CaliberRM for Microsoft Visual Studio 2008 / Visual Studio Team Foundation 2008.....30 

CaliberRM for Microsoft Visual Studio 2005..................................................................31 

CaliberRM for Microsoft Visual Studio Team System....................................................32 

CaliberRM Web Client...................................................................................................32 

Limitations................................................................................................................................33 

4 | Contents

CaliberRM 2008 Release Notes 

October 2, 2009 

This document contains system requirements, software-compatibility requirements, and other important 

information that might not appear in the Help. It is recommended that you read these Release Notes in their 

entirety. To view the most recent version of this document, visit http://techpubs.borland.com/caliber. 

The CaliberRM SDK Programmers Guide and the CaliberRM Tutorial are not included in the release media. 

However, they are available for download from http://techpubs.borland.com/caliber. 

What's New 

This section provides an overview of the new features found in CaliberRM. 

Support for Third-Party Integration Tools 

HP Quality Center Version 10.0 is supported for non-versioning projects. Support is not provided for Mercury 

Quality Center (QC) 10.0 for versioning-enabled projects that use CaliberRM Mercury Publisher and CaliberRM 

Test Wizard tools. 

Enhanced Document Factory 

A new version of Document Factory has been added to the product. This new version uses a set of XML 

interfaces to Word rather than the COM interfaces. This change results in the faster generation of documents 

and allows the generation of more flexible templates in releases following v2008. Additionally, documents are 

now generated without the use of an intermediate MS Access database because data is pulled directly from 

the server during generation. 

The original Document Factory is still included. For any version of Microsoft Word v2003 or earlier, the default 

version is the original Document Factory. For Word 2003 or 2007, you can choose either the new or the old 

document factory. The new Document Factory works with Microsoft Word version 2003 or later. To continue 

using the previous version of Document Factory for Microsoft Word version 2003 or later, specify the appropriate 

path in the registry. Otherwise, the new Document Factory is initiated by default for Microsoft Word version 

2003 or later. For more information, contact technical support. 

Initial comparison results for document generation indicate that the new version of Document Factory can 

generate a document twice as fast as the previous version. 

Access to Saved Grid and Matrix Filters in Document 

Factory 

Beginning in v2006, the Traceability Matrix filter mechanism allowed users to save their filters. In v2008, that 

filter capability was added to the Requirements Grid. The filters that are created and saved can be accessed 

by keyword in the new Document Factory. As a result, the output is captured in the Document Factory when 

the filter is executed. 

CaliberRM 2008 Release Notes | 5

API Changes 

New methods are provided for the following actions: 

• Managing licenses though the SDK 

• Obtaining a checkpoint to view changes since a previous checkpoint 

URL Addressability 

URL addressability allows you to create a URL for any given requirement. Navigation of the URL requires the 

user to have installed the CaliberRM Client. The URL does not follow the traditional HTTP style because the 

target is directed to the CaliberRM application. The URL can be pasted into a browser or the Windows Run 

dialog box for execution. Users must log on if they are not already logged on to the target project. 

Filter Mechanism on Grid 

The same filter mechanism that was added to the Traceability Matrix in v2006 is now available on the 

Requirements Grid, allowing you to build more complex filters and save those filters for reuse. Unlike filters in 

version 2006, filters in the current version are saved on the server side. Consequently, performance is improved 

due to less data being sent across the network to the client. 

Saving filters on a user's computer saves the column layout in an RGV file. 

Filter Criteria in Grid and Matrix 

Baseline filter criteria has been added to the Traceability Matrix and to the Requirements Grid. 

Hierarchies and the most recently modified information exist only as views. Filtering capability is not available 

for these fields. 

Status Add-In Added to Datamart 

The status attribute of items that are traced to CaliberRM by way of the traceability add-in are now included 

in the Datamart extract. Users can include them in reports. For example, the status of a test case linked to 

Quality Center is now available in the Datamart extract. 

Visual Improvement to Baseline Maintenance Window 

Requirements can be deleted from the current baseline (but not from a selected baseline) yet remain available 

because they are part of another baseline. In the Baseline Maintenance window, a visual clue differentiates 

requirements that are deleted from requirements that simply do not appear in the selected baseline. 

Requirements can be identified by their fonts and colors, as follows: 

• Requirements in the selected baseline appear in bold 

• Requirements in the current baseline but not in the selected baseline appear in normal font 

• Requirements that do not reside in either the current or selected baseline are teal in color 

6 | CaliberRM 2008 Release Notes

Help Content 

Because of a major documentation conversion that was underway during the 2006 release, that version did 

not contain all of the Help topics that were available in previous releases. The 2008 release completes the 

conversion and includes the missing topics that are relevant to v2008. 

System Requirements and Prerequisites 

This section identifies the system requirements and prerequisites for the various CaliberRM components. 

CaliberRM Server 

The following table identifies the system requirements for installing and running CaliberRM Server. 

System Area 

Platforms 

Hardware requirements 

VMware 

Hard disk space 

Requirement 

• Windows Server 2003 Enterprise Edition (SP1, 32-bit 

version) 

• Windows Server 2003 R2 Standard Edition (SP1, 32-bit 

version) 

• Windows Server 2003 R2 Enterprise Edition (SP1, 32-bit 

version) 

Recommended configuration by OS provider 

VMware ESX Server 3.0.1 

1 GB (minimum); 30 GB or higher (recommended). Existing 

customers must have at least 2.5 times their current 

database size prior to upgrading. 

Note: The actual amount varies, depending on your 

use of the product. 

CaliberRM Windows Client 

The CaliberRM Windows Client is available in English, Japanese, French, and German. Only one of the 

supported languages can be installed, and most of the supported languages must be installed on the matching 

operating system. However, English can be installed on non-English operating systems. 

The following table identifies the system requirements for installing and running CaliberRM Windows Client. 

System Area 

Platforms 


Web browser 

Requirement 

• Windows XP Professional (SP2) 

• Windows Vista Enterprise Edition 

Configuration recommended by OS provider 

Internet Explorer 7.0 


CaliberRM for Eclipse 

The following table identifies the system requirements for installing and running CaliberRM for Eclipse. 

System Area 

Software 


Requirement 

Eclipse 3.2, 3.3 (available for download from 

http://www.eclipse.org) 

Configuration recommended by Eclipse 

CaliberRM for Microsoft Team Foundation Server 

The following table identifies the system requirements for installing and running CaliberRM for Microsoft Team 

Foundation Server. 

System Area 

Platforms 

Software 

Requirement 

Refer to Visual Studio Team Foundation Installation Guide, 

available for download at 

htp:/www.microsoft.com/downloads/details.aspx?familyid=f12844f-398c-4fe9-8b0d-9e84181d9923&displaylang=en 

• Microsoft Visual Studio 2008 Team Foundation Server 

• Microsoft Visual Studio 2005 Team Foundation Server 

Note: Support for Microsoft Team Foundation Server 2003 has been removed. 

CaliberRM Client for Microsoft Visual Studio Team System 

2005 and 2008 

CaliberRM for Microsoft Visual Studio Team System is available in English and Japanese. Only one of the 

supported languages can be installed, and it must be installed on the matching operating system. 

The following table identifies the system requirements for installing and running CaliberRM Client for Microsoft 

Visual Studio Team System 2005 and 2008. 

System Area 

Platforms 

Processor, RAM 

Requirement 

Refer to the Microsoft system requirements at 

http://msdn.microsoft.com/en-us/vsts2008/aa718944.aspx 

Refer to the Microsoft system requirements at the following 

locations: 

• http://msdn.microsoft.com/en-us/vsts2008/aa718687.aspx 

for Visual Studio 2005 Team Edition for Software 

Developers 

• htp:/download.microsoft.com/download/A/2/8/A2807F78-C861-4B66-9B31-9205C3F22252/VS2008SP1Readme.htm 

for Visual Studio 2008 Team Edition for Software 

Developers 


System Area 

Software 

Requirement 

• Visual Studio 2005 Team Suite 

• Visual Studio 2008 Team Suite 

• Microsoft Visual Studio 2005 Team Explorer 

• Microsoft Visual Studio 2008 Team Explorer 

Note: Microsoft VS 2003 integration is no longer supported because mainstream support from Microsoft 

ended in October 2008. Nevertheless, a defect in the installer shows the option to install VS 2003 integration. 

A future version of the CaliberRM installer will fix this bug and remove this installation option. 

CaliberRM Web 

The following table identifies the system requirements for installing and running CaliberRM Web. 

System Area 

Web server 

Client browser 

JDK/JRE 

Requirement 

• Apache (provided) 

• IIS 

Internet Explorer 6.0 SP1, 7.0 

1.6, 1.6.x.x 

Software Compatibility 

The following table lists supported, third-party products with integrations have been tested. 

CaliberRM Feature 

Traceability 

Supported Product 

Borland StarTeam 

Borland Together for Eclipse 

Borland Silk Central Test Manager 

IBM Rational ClearCase 

Merant PVCS Version Manager 

Mercury Quality Center 

Microsoft Visual SourceSafe 

Tested Version 

2006, 2008 

2006, 2007 

2006 (8.5), 2007 (8.6), 2008 (8.8) 

2003 

6.8 

9.0, 9.2, 10.0 

6.0 SP6 

Document Factory reports, document 

references, and requirements export (to 

Access) and import (from Word) 

• Microsoft Office 2000 (reports using 

older Document Factory only), 2003, 

2007 

• MS Word 2000, 2003, 2003 SP2, 

2003 SP3, 2007 

• MS Excel 2000, 2003, 2003 SP2, 

2003 SP3, 2007 

Datamart extraction targets and analysis 

tools 

Business Objects 

Microsoft Access 

6.5, 11 

2003, 2007 


CaliberRM Feature 

Integrated Development Environment 

(IDE) integrations 

Web server 

Software license servers 

Microsoft Windows Server Internet 

Information Services (IIS) 

VMware 

Supported Product 

Microsoft SQL Server 

Oracle Database Server 

Borland Developer Studio © ++ Builder, 

C# Builder, Delphi) 

Borland JBuilder 

Microsoft Visual Studio 

Microsoft Visual Studio Team System 

Eclipse 

Apache Web Server 

Microsoft Windows Server Internet 

Information Services (IIS) 

MacroVision FlexLM 

2000 (5.0), 2003 (6.0) 

VMware ESX Server 

Tested Version 

2000, 2005 

10g 

2006 

2005, 2006 

Visual Studio 2005 SP1, 2008 

2005 SP1, 2008 

3.2, 3.3 

2.0 

2000 (5.0), 2003 (6.0) 

8.2a 

— 

3.0.1 

Installation and Upgrade Instructions 

The upgrade procedure has changed from previous releases. Existing customers are encouraged to review 

the Performing an Upgrade section of the Installation Guide, which is available from the Borland 

Documentation Web site at http://techpubs.borland.com/caliber. 


If the database contains a large number of traces, the server database size might grow noticeably during the 

upgrade.This growth is due to the introduction of traceability versioning in this release. If you have unnecessary 

traces that are either created manually or copied and pasted from a previous requirement, it is recommended 

that you remove them before upgrading. For more information, contact support or visit Borland Answers at 

http://support.borland.com/entry.jspa?externalID=5313. 

If your existing SDK application must connect to a server that is not yet upgraded to this release, do not 

recompile your application with the included SDK. In general, when writing SDK applications, use the same 

version of the SDK as the version of the oldest server to which the application must connect.You must recompile 

your .NET/COM SDK applications to make use of the new SDK functionality provided in this release, such as 

creating and assigning security profiles.The recompiled application is compatible with this release of the server. 

To restore a backup made with a previous version of CaliberRM, first upgrade the backup to 2008. 


Installation instructions for the CaliberRM Windows Client depend on whether the client is installed on a machine 

that is different from the server. For more information, refer to the Installation Guide. 



For installation instructions, refer to the Installation Guide. 

CaliberRM for Microsoft Visual Studio 2005 


CaliberRM for Microsoft Visual Studio 2008 


CaliberRM for Microsoft Visual Studio Team System 

Prior to installing the CaliberRM Client for Visual Studio Team System (VSTS), your VSTS administrator must 

install CaliberRM for Team Foundation Server on the machine that hosts Team Foundation Server. The 

CaliberRM client for Microsoft Visual Studio Team System component must be installed by each VSTS user 

(architect, developer, tester, etc) to access CaliberRM requirements from within Visual Studio and establish 

traceability between requirements and VSTS work items as well as tests from Visual Studio. 


Resolved Issues 

This section identifies issues that have been resolved by the various patches for CaliberRM 2008 WW release. 

Resolved Issues for Patch 11 

The following table identifies issues that have been resolved by Patch 10 for CaliberRM 2008 WW release. 

Category 

Traceability Matrix 


Change Request Number 

44061 

43991 

Description 

In the traceability matrix, the action of 

right-clicking the cell that represents a 

trace between a requirement and an 

external vendor object causes the 

matrix to hang. 

Prevents CaliberRM Server from 

exposing the physical host name to 

Caliber Client. 




Category 

CaliberRM Win32 Client 


Migration 

Datamart 


Integration with DefineIT 

Patch installer 

Datamart 

Datamart 

Requirements Grid 


44049 

44033 

44032 

44031 

44028 

44022 

44022 

43968 

43967 

23993 

Description 

Error message CaliberRM 

Internal Error: 91-CD opens 

for a requirement while saving a child 

requirement on the References page. 

Deleted users can still be edited in the 

multiple selection user list (MSUL) UDA 

for Win32 Client. 

Data is duplicated when migrating DB 

from 2005 to 2008. 

Datamart cannot complete extractions 

on large databases. 

Deleted users can still be selected in 

the MSUL UDA for Win32 Client. 

Synchronization from DefineIT 

generates a namespace error in 

CaliberRM Client's history view. 

Synchronization from a DefineIT 

requirement with a specific word tag 

causes the error NameSpace error 

in the History view of the CaliberRM 

Client. 

After installing the current version of the 

patch, the previous patch still appears 

in the Add or Remove Programs 

Control Panel applet . 

When running Datamart with the option 

-update -depth 1, the number of 

updated traces is larger than expected. 

Datamart crashes when trying to extract 

traces from a large database. 

When user filters for a UDA value in the 

Requirements Grid return no matches, 

the column disappears from the grid. 



Category 

CaliberRM SDK 

CaliberRM Datamart 


43952 

43890 

Description 

Error Object_does_not_exist 

occurs when you call 

projectmanager.getproject(projectid) 

for an empty project. 

When you create a UDA of type 

multiple-line text and set the maximum 

length to 10,000 (i.e., when a 

requirement is set with value of 10,000 


Category 




CaliberRM DocFactory 





43854 

43821 

43803 

43771 

43705 

42701 

41623 

Description 

characters), it is truncated to 2,048 

characters when extracted to MS 

Access. 

Deleted values of the MSUL attribute 

still appear in the Requirements Grid. 

Requirements can be modified through 

the Requirements Grid with deleted 

values. 

In the General Options section of the 

Spelling page (CaliberRM ➤ Tools ➤ 

Options ➤ Spelling), parent-child 

relationship are not followed by check 

boxes. 

Parent: Always check spelling before 

saving requirements. 

Child: Check spelling only if the 

requirement's description is modified. 

Broken functionality with the client-side 

option to create a child-to-parent trace 

upon requirement creation. 

The new Document Factory refuses to 

log on if password is expired. Unlike the 

new Document Factory, the previous 

version handles this situation by 

prompting the user for a new password. 

External Trace Status does not work 

with Silk Central Test Manager (SCTM) 

2008 R2 SP1. 

Linking Service fails to log on to SCTM. 

MPX event notification in Framework 

Administrator; changes made to a group 

are not saved if the same record is 

edited on another instance. 



Category 


CaliberRM Client 


43830 

43633 

Description 

After navigating backward in the new 

Document Factory wizard, the last 

button clicked is presented as the 

default selection instead of Next or 

Finish. 

The Import from Word function 

inappropriately imports text into the 

requirement description that is specified 


Category 












43849 

43867 

43858 

43786 

43732 

43720 

43691 

42799 

42499 

42520 

Description 

by a style to become the requirement 

name. 

When you invoke the Document 

Factory, the StarTeam toolbar does not 

cache the logon information. The first 

page is prepopulated with the last 

logged-on server, and the user name is 

retrieved from the registry. 

The Password text box also appears 

to be prepopulated. However, the 

Password text box is always 

prepopulated with the password 

admin. 

The new Documentation Factory throws 

an unhandled exception if a user clicks 

OK to close the message and then 

navigates back to Page 1 from Page 2. 

The new Documentation Factory hangs 

when you click Close on forms other 

than the Startup form. 

Any changes to the old versions of 

requirements are not displayed in the 

history. 

A requirement and its children appear 

as read-only objects. The CaliberRM 

Client shows the previous requirement 

version instead of the current one. 

When running a Datamart extraction to 

MS Access or SQL, the special 

character " " is stripped out along with 

all HTML tags.This action removes any 

spaces that lie between words in the 

resulting requirement description. 

The extension of the default result file 

is .doc. The new Documentation 

Factory does not support the extension 

.docx. 

When performing Datamart extractions, 

the requirement name is truncated if it 

contains more that 64 characters. 

In the new Document Factory, all line 

returns are removed from the validation 

procedure in the resulting document. 

The new Document Factory does not 

remember form data, such as a user's 

password, if the previous operation 

failed. 


Category 





41810 

41780 

41172 

Description 

Unable to use more than one 

$REQTREE command in Document 

Factory reports. 

When you start the new Document 

Factory from within CaliberRM 2008, it 

does not save the user name and 

password even though it appears to 

save them. 


return any requirements if the 

requirement type is more than 64 

characters in length. 



Category 

CaliberRM Client/Server 








43723 

43719 

43666 

41957 

43688 

43690 

42496 

Description 

Requirement names that contain the 

following characters fail to publish to 

Quality Center. 

Users do not have the rights to modify 

the registry key to launch the old 

Document Factory. The registry key is 

based on HKEY_LOCAL_MACHINE 

instead of HKEY_CURRENT_USER. 

The Datamart -update command 

does not manage deletions from the 

Responsibilities list. 

Running the new Document Factory 

from the CaliberRM Client produces a 

different result from running the new 

Document Factory directly from the 

executable. Baseline information is 

ignored in the new Document Factory 

template when it is run from the client. 

The requirement description is affected 

when the font family or font is changed 

in Internet Explorer (IE). However, if the 

font family and size are not defined 

within the HTML code, they are 

reflected in the requirement's 

description when you change the IE 

settings. 

Project descriptions are printed 

incorrectly. 

After the new Document Factory 

generates a document, it does not 


Category 




43736 

43692 

Description 

prompt the user to open the resulting 

XML or DOC file. 

Exporting a large matrix to XML causes 

it to crash. 

Incorrect focus cycle among GUI input 

fields on the wizard pages of the 

Document Factory. 



Category 








CaliberRM SDK 



43596 

43562 

43518 

43517 

43484 

43342 

41327 

43542 

43703 

Description 

Data inconsistencies are encountered 

from concurrent Requirements Grid 

modifications. 

CaliberRM hangs when defining a 

numeric filter for a grid. 

When you right-click a trace and choose 

properties on the UDA page, the UDAs 

for the target requirement are not visible 

when using a newer database. 

A Last Transaction 

Incomplete message is displayed 

on the Traceability page when the 

requirement version is not from the 

current baseline. 

When using the Customer database, 

one of the multiple Requirements Grids 

crashes when launched in parallel. If a 

timeout exception from the server 

already exists, the client must request 

the data again. 

A message states that requirements 

have been deleted when they have not 

created a new message, most likely 

because it was reusing an existing 

message not intended for this use. 

Hyperlinks to files on a server do not 

work on save. 

Java API can perform only the mapping 

of requirements, not unmapping. 

In the new Document Factory, 

requirements with date and multitext 

line UDAs are not generated properly 

in reports. 




Category 





43344 

43118 

43317 

Description 

When you choose Tools ➤ Options ➤ 

Spelling to open the Spelling page in 

a non-English CaliberRM client, the 

client crashes with a debug error. 

Deleted traces between a file object and 

a requirement that is present in a 

non-current baseline appear in the 

Traceability Matrix. 

Default values for options in the Versant 

file profile.be need to be updated. 



Category 






CaliberRM SDK 


42957 

42560 

43077 

42516 

43163 

43167 

Description 

WorkItem properties do not open for 

VSTS 2008 traces. Properties have 

been re-referenced to correct the 

Microsoft Visual Studio Team System 

2008 DLLs based on the location of the 

installation. 

The status and project paths of traces 

to StarTeam items are not refreshed 

when the items are moved or deleted. 

Because this fix requires StarTeam SDK 

changes, it is recommended that you 

upgrade to StarTeam SDK 10.0.60 or 

10.1. 

When a StarTeam item is checked out, 

the status of the trace must be changed 

to suspect. The behavior of the 

checkout operation is changed in the 

CaliberRM client to change the trace 

status to suspect. 

When the MPX component for Borland 

Search Server is enabled, an error 

occurs if the MPX server is installed on 

a different machine. 

When a trace to Team System Test is 

removed through Win32 Client, an error 

is displayed for longer strings. 

SDK fails to save baseline information. 

This issue was introduced in 


Category 

CaliberRM SDK 


42919 

Description 

Hotfix34c-2006. 

BaseLineTreeNode object is 

converted back to UTF8 when 

communicating with the server. 

CaliberRM SDK throws various types 

of exceptions due to data corruption or 

the mishandling of data while parsing. 

The issue was fixed by converting the 

xHTML/XML string into an XML 

document while parsing and validating 

requirement descriptions. 



Category 











41351 

42713 

42860 

42864 

41469 

42751 

42867 

42087 

42358 

Description 

The cursor jumps to the top of the 

paragraph after pasting text into a table. 

The Import from Word function fails 

when using MS Office 2007. When 

importing from Word, the import fails 

when using the plain-text option, 

resulting in an orphaned 

Winword.exe. 

The Datamart outputs unnecessary 

information. 

The time format is inconsistent when 

running Document Factory. 

Requirement Viewer takes a long time 

to load requirement information based 

on change request management (CRM). 

CaliberRM license status is Missing 

after it is assigned from the Borland 

License Server page. 

The -depth command does not 

update for MS SQL server and Oracle 

server usage. Only MS Access has 

update information for -depth. 

Customers requested to remove 

Hotfix54-2006 behavior because they 

want to revert the earlier request to 

create the same Hotfix. 

Performance decreases when using 

2008 filters to filter subrequirements of 

requirement IDs within a range. 


Category 



CaliberRM SDK 


42837 

42882 

41285 

Description 

Unable to log on to CaliberRM by using 

LDAP if the password contains a 

localized character, such as é or à. 

CaliberRM SDK 2008 fails to retrieve 

traces for project. 

Borland Search continually fails with the 

message 

java.lang.OutOfMemoryError: 

Java heap space. 



Category 








41141 

41797 

42457 

42458 

42627 

42648 

Description 

Limit the number of traces output in the 

Datamart extraction to a set number or 

level. 

Fails when running an extraction with 

the -update command with Datamart. 

Datamart -update option fails while 

extracting large volume of requirements. 

Datamart -update option does not 

use paging. 

Datamart -update option does not 

properly export the Responsibilities 

list. 

When performing maintenance on 

various projects and baselines, the error 

last transaction 

incomplete is thrown. 



Category 





40779 

41705 

41737 

Description 

Sorting does not function properly on 

the Add Baseline Signatories dialog 

box. 

Deleting the current baseline version of 

a requirement does not mark the 

attributes as deleted. 

When traces are deleted, new versions 

of trace objects are created. 


Category 

















41865 

41943 

42034 

42171 

42215 

42330 

42402 

42352 

42404 

42442 

42293 

41969 

40321 

41711 

42195 

Description 

UDA issues occur when making 

changes to the requirement baseline or 

to the requirement type. 

The new Document Factory cannot 

handle German special characters. 

When using Datamart to extract history, 

the changes in requirements relating to 

multiple-selection UDAs are not 

exported appropriately. 

Deleted users are unavailable for 

assignment to Project Administrator 

status. 

Creation of Caliber requirements in 

Together 2007 SP1 fails. 


embed images and other objects into 

the resulting document. Instead, it 

creates them as links. 

HTML code is displayed in QC 

Integration property windows. 

When Document Factory fails from the 

command-line interface, a 

winword.exe orphan is left running 

as a process. 

Document Factory $Begin_List 

$End_List repeats the first 

reference. 

While launching a new Document 

Factory from CaliberRM Win32 Client, 

the server credentials are not passed 

to the Document Factory client. 

The Document Factory keywords do not 

output glossary terms in alphabetical 

order. 

The new Document Factory 

experiences usability issues in default 

server credentials, user names, error 

handling, and the display behavior of 

windows. 

Some German characters do not appear 

properly in the Web client. 

Cannot view images in the new 

Document Factory output. 

Datamart configuration does not support 

the exporting of all baselines when the 

All Projects option is selected. 


Category 


















41790 

41975 

42020, 41050, 41679 

41951 

42350 

41899 

42137 

42451 

40441 

42131 

42159 

42014 

41797 

23436 

42087 

42140 

Description 

Datamart extraction fails when 

SQLLDR's input file exceeds 2 GB. 

Datamart Configurator does not properly 

edit saved configuration files with more 

than 200 projects. 

Trace Set status is not displayed in 

Win32, Document Factory, Datamart, 

and Web Client. 

Exclude external traces for Export to 

Access function. 

Cannot filter on the User 

multiple-selection listbox UDA in the 

Traceability Matrix. 

If you filter by responsibility in the 2008 

Requirements Grid, no requirements 

are returned. 

New or modified UDAs do not appear 

for most requirements. The 

Requirements Grid returns incorrect 

lists. 

The Requirements Grid and the 

CaliberRM Client display different UDA 

dates. 

Grid export to CSV defect. The 

Description text box is truncated to 256 

characters in Requirements Grid Print 

Preview. 

CaliberRM Client crashes when editing 

multiple requirement fields in the 

Requirements Grid while requirements 

are locked by other users. 

When adding a glossary term to a 

glossary that already exists, the client 

does not refresh appropriately. 

Caliber Connection to HP Quality 

Center 9.2 over HTTPS. Caliber 2008 

Publish to Quality Center / Test Wizard 

over HTTPS is not working. 

Regression issues with Datamart’s 

-update option. 

Error message while deleting a 

requirement when the audit log is 

enabled. 

Read-only users can shift requirements. 

Performing baseline maintenance on a 

newly created baseline throws a Last 

transaction incomplete error. 


Category 

CaliberRM Web Client 

VS 2005 Integration 


42255 

42032 

Description 

German umlauts are not displayed 

appropriately in the CaliberRM 2008 

Web Client. 

Visual Studio 2005 integration does not 

release the logon credentials. 

Resolved Issues for 2008 

The following table identifies issues that have been resolved in CaliberRM 2008 WW release. 

Hot Fix 

Hot Fix 01C 

Hot Fix 01C 

Hot Fix 01C 

Hot Fix 01C 

Hot Fix 01C 

Hot Fix 01C 

Hot Fix 01C 

Hot Fix 01C 

Hot Fix 2 

Hot Fix 2, 3 


41815 

41770 

41812 

41205 

41457 

41502 

40811 

41487 

41850 

21768 

Description 

The Caliber Datamart project fails for 

large databases. The job hangs for 

approximately an hour and then fails 

with a Get requirement tree 

error or a getserver error. 

Document Factory does not take into 

account any of the changes to the 

default security profile. 

Users who are not part of the Admin 

group are unable to run Document 

Factory. They receive a User not 

authorized message. 

Datamart extraction fails. 

Datamart needs to utilize the parameter 

-SQLLDR during Oracle extractions to 

improve performance. 

The -update parameter does not 

function when used with Oracle. Its 

usage causes a failure without building 

the database. 

Document Factory stops with a Value 

out of range message. 

SCM traces the output ERROR: 

Invalid ID instead of the traced-to 

object's name in Document Factory. 

The Requirements Grid filter returns 

incorrect results when filtering on the 

description. 

When using the Paste Special 

functionality to copy a requirement with 

traces, the suspect statuses of the 

traces are lost. 


Resolved Issues for 2006 

The following table identifies issues that have been resolved in CaliberRM 2006 WW release. 

Hot Fix 

Hot Fix 16 

Hot Fix 17 

Hot Fix 18 

Hot Fix 18 

Hot Fix 18 

Hot Fix 19, 20 

Hot Fix 20 

Hot Fix 22, 22c 

Hot Fix 24 

Hot Fix 24 

Hot Fix 25 

Hot Fix 26 

Hot Fix 27c 

Hot Fix 28c 

Hot Fix 29c 

Hot Fix 31c 

Hot Fix 32c 


40728 

40811 

23417 

23399 

22479 

40929 

22479 

41205 

40538 

40538 

40811 

40538 

41457 

41326 

41487 

41502 

41577 

Description 

CaliberRM CRMDiag Tool not included 

in v2008. 

CaliberRM CRMDiag Tool not included 

in v2008. 

CaliberRM SDK application error. 



Traceability Matrix shows requirements 

for projects to which the user does not 

have access. 


Datamart Extraction failing. 

When a requirement is deleted in 2006, 

it appears to be left in a hanging status 

but still appears in searches, Document 

Factory reports, and stopping-baseline 

abilities. 

After deleting a requirement, unread 

discussions still appear. The owner of 

the discussion appears as 

?|?. 

CaliberRM 2006. Docfactory.exe 

version 9.0.906.0. 

The Traceability Matrix displays 

requirements for projects to which the 

user does not have access. 

Datamart does not utilize the parameter 

-SQLLDR during Oracle extractions. 

When importing from Word, a 

requirement name is truncated to 64 

characters even though the CaliberRM 

Client supports requirements with 

names of 128 characters. 

SCM traces the output ERROR: 

Invalid ID instead of the traced-to 

object's name in Document Factory. 

The usage of the -update parameter 

with Oracle results in a failure without 

building the database. 

The map-requirement functionality 

cannot be used with the SDK (applies 


Hot Fix 

Hot Fix 33c 

Hot Fix 34c 

Hot Fix 37 

Hot Fix 38c 

Hot Fix 38c 

Hot Fix 39c 

Hot Fix 40 

Hot Fix 41c 

Hot Fix 42c 

Hot Fix 42c 

Hot Fix 43c 

Hot Fix 44c 

Hot Fix 45c 


41595 

41261 

41594 

41674 

41619 

41626 

41681 

40321 

41664 

41741 

41626 

41351 

41910 

Description 

only to COM-based code, such as C# 

and VB.NET). 

Datamart-to-SQL extraction fails, 

throwing an INVALID_QUERY(0) 

error on the appropriate requirement. 

HTML returned from a requirement 

object contains inappropriate UTF-8 

characters for symbols pasted from 

Word documents, such as curly quotes, 

minus signs, and bullets. 

CaliberRM does not delete projects 

appropriately. 

When using the Traceability Matrix with 

filters, CaliberRM returns a 

GeneralObject message. 

The User multiple-selection listbox 

displays deleted users. 

When you move a value within a 

multiple-selection listbox, the filter within 

the Traceability Matrix breaks. 

CaliberRM displays duplicate 

requirement versions and traces. 

Some German and unicode characters 

do not appear properly in the Web 

Client. 

No pop-up messages, such as object 

does not exist, should occur 

when running Datamart extractions. 

This feature is designed as a 

command-line tool for use with 

automated scripts. As such, it does not 

feature any GUI components. 

Information messages should be logged 

to the screen and/or log files with more 

detailed information. 

After applying Hotfix 33c (extractor), the 

Direction text box in the TRACE table 

contains unreadable values. 

When you move a value within a 

multiple-selection listbox, the filter within 

the Traceability Matrix breaks. 

The cursor jumps to the top of the 

paragraph after pasting text into a table. 

Using the $RGVFILE tag in Document 

Factory to filter requirements on 

Hierarchy# returns incorrect results. 


Updated Files in Patch 

This section describes files that are updated in the current patch of CaliberRM 2008 WW release. 


The following files, which are listed relative to the installation directory, are updated in CaliberRM Client: 

• de\CaliberRMRes.dll 

• en\CaliberRMRes.dll 

• fr\CaliberRMRes.dll 

• ja\CaliberRMRes.dll 

• de-DE\DocFactory2.resources.dll 

• fr-FR\DocFactory2.resources.dll 

• ja-JP\DocFactory2.resources.dll 

• de-DE\QueryBuilder.Resources.dll 

• fr-FR\DocFactory2.resources.dll 

• ja-JP\DocFactory2.resources.dll 

• Traceability Addins\QCIntegrationAddin.dll 

• Traceability Addins\StarTeamAddIn.exe 

• Borland.CaliberRM.DocFactory.Parser.dll 

• CaliberAddinBridge.dll 

• CaliberCommon.dll 

• CaliberEvent.dll 

• CaliberFACommon.dll 

• CaliberRM.exe 

• CaliberRMAdmin.exe 

• CaliberRMSDK100.dll 

• CaliberRMSDK100.NET.dll 

• CaliberRMViewer.exe 

• CaliberSpelling.dll 

• Configurator.exe 

• CRMSBToolbarIF.dll 

• DocFactory.exe 

• DocFactory2.exe 

• DocFactory2.exe.config 

• Export.exe 

• Extractor.exe 

• MercuryPublisher.exe 

• QueryBuilder.dll 

• readme_en.html 

• TestWizard.exe 

• XMLCommonEx.dll 


The following files, which are listed relative to the installation directory, are updated in CaliberRM Server: 


• bin\caliber_srv.exe 

• lib\dbmgr.exe 

• lib\profile.be 

CaliberRM SDK 

The following files, which are listed relative to the installation directory, are updated in CaliberRM SDK: 

• bin\CaliberCommon.dll 

• bin\CaliberRMSDK100.dll 

• lib\CaliberRMSDK100.jar 

• lib\CaliberRMSDK100.NET.dll 

• lib\CaliberRMSDK4COM100.jar 

• lib\jvb.dll 

Known Issues 

This section identifies known issues with the various CaliberRM components. 


The released software download displays Unknown Publisher instead of is signed by Borland. For 

more information, visit http://support.microsoft.com/kb/922225/en-us#appliesto. 

MPX users: When you upgrade your server from CaliberRM 2005 Release 2, MPX events are disabled by 

default. If you used MPX events with your CaliberRM 2005 Release 2 Server and are planning to continue 

using MPX events, click Enable MPX Events on the MPX Configuration dialog box. This option requires 

StarTeam Message Broker. 

Evaluation users: If you reinstall a trial version of CaliberRM 2008 Server on a Windows XP machine, your 

installation might fail. To prevent failure, stop the SQM Monitor and SQM Database Windows Services before 

reinstalling. 

During the upgrade, the CaliberRM Server settings in the Control Panel applet are lost. Save these settings 

prior to upgrading and restore them afterward. 

When attempting to install the CaliberRM Server from a remote location, the message Error 1706: no 

valid source could be found appears. Avoid this message by running the installer locally from the 

server machine. 

Borland License Server users: The per-user license assignment (named or concurrent) needs to be manually 

restored after an upgrade. If your CaliberRM server is configured to use Borland License Server (BLS) licenses 

only, change the Admin user license type to BLS to log on to the CaliberRM Server while using the CaliberRM 

Client as Admin. In this case, connections of the Admin user to the CaliberRM Server by using the CaliberRM 

Client are counted by the BLS Server against the available licenses. The type of license acquired (named or 

concurrent) depends on the type of the particular BLS license assigned to the Admin user. 


This section identifies known issues with CaliberRM Windows Client. 


Localization 

Only some of the strings have been localized. 

The spell checker reports contracted, non-English words, such as l'eau, as misspelled. 

Dictionary 

When CaliberRM Client is launched for the first time, it tries to create dictionary files in the directory Program 

files by default. This attempt might fail if the user does not possess write access to Program files. 

Documentation 

On Windows XP SP2, choosing Help ➤ Help Content sometimes generates an error. To avoid this error, 

perform the following steps: 

1. Open Internet Explorer. 

2. Choose Tools ➤ Internet Options. 

3. Click the Advanced tab. 

4. Under Security options, click Allow active content to run in files on My Computer. 

5. Click OK. 

For more information, visit http://support.microsoft.com/kb/843017. 

The documentation lacks information about tracing files. To trace files, perform the following steps: 

1. On the Traceability Modification dialog box, click the Files tab. 

2. Click Browse, select the file to or from which to trace, and click OK. 

3. Click Trace From or Trace To, to create the trace, as appropriate. 

4. Click Save Changes. 

Help 

The topic Importing Requirements from Microsoft Word states that you can import requirement names with 

delimiters or keywords. Instead, the topic needs to state that you can import requirement descriptions only 

with delimiters and keywords. 

The Datamart topic launched from the Configurator wizard contains an inappropriate path for launching the 

Configurator. The appropriate path is Borland CaliberRM ➤ Administration ➤ Datamart. 

Windows Client 

Inconsistent behavior might result when inserting objects. JPEG objects are displayed by their file names, 

while BMP files are shown as images. This behavior is consistent with OLE behavior in MS Word. 

Traces added by previous users are visible and available, even after logging off, to a different user who might 

not possess the SCTM rights to view a particular project from which the traces were added. 

In the case of the trace-to-SCTM artifact, the trace filter for the Requirements Grid does not work for remote 

traces. When you select these filters, the requirements with remote traces are not displayed. 

On Japanese Vista, some dialog boxes appear too big, and some labels appear too small. This effect is due 

to the change in the default font from MS UI Gothic to Meiryo. To return dialog boxes to their normal sizes, 

change the window design from Windows Vista Basic to Windows Standard. 

Importing an exported project into a new project generates multiple, consecutive Object does not exist 

messages, and the import is not successful. A second run of the import succeeds. 


When you use the CaliberRM SDK to create a user, the User Can Manage Glossary Terms permission 

is enabled by default. No SDK option exists to deselect this permission. However, if this permission needs to 

be disabled, you can disable it on the Security page of the CaliberRM Administrator. 

Do not use surrogate pair characters, which the CaliberRM SDK does not support surrogate. Clients that use 

the SDK cannot process surrogate pair characters appropriately. 

If you do not have the corresponding OLE object software installed, the Edit object command, without 

warning, does not open the OLE object software. 

The Export to MS Access function does not include StarTeam traces. Use the Datamart extractor to MS Access. 

Mercury QC traces are not exported to MS Access when you choose File ➤ Export to Access. Consequently, 

you must log on to QC before initiating the Export to Access function. 

Traces to deleted requirements are displayed as Retrieving on the Traceability page. 

Rows and columns in the Traceability Matrix cannot display non-requirement objects without displaying some 

requirements. To avoid this issue, use ID equals as a filter criteria to display one 

requirement along with the external objects. 

Saved traceability matrices do not persist the traceability matrix layout or the user filter. 

In user baselines, the message Retrieving... is displayed instead of the trace to requirement deleted in 

current baseline. 

Due to the versioning of traces, creating some baselines might take longer in the current version than in 

CaliberRM 2005. 

Traceability cannot be included when pasting requirements after a copy. Instead, use the Paste Special 

functionality. 

Document Factory 

Due to a localization issue, the Document Factory's logging directory is changed from C:\Documents and 

settings\Local Settings\Application Data\Borland\CaliberRM\Log to C:\Documents and 

settings\\Local Settings\Application Data\Borland Software 

Corporation\Borland\CaliberRM\Log. 

If you are generating Document Factory with requirement trace-to-SCTM linking service, the external trace 

does not appear in the document. 

When running a previous version of Document Factory (with MS office 2000), you must click the Multiple 

option instead of Once to replace the keywords properly for all the records. 

In new Documentation Factory for versions 2003 and 2007, an Invalid Query message appears during 

document generation when the $filter command, which contains the old Document Factory syntax, is used 

in the template.To avoid this message, create and save a new filter on the server, and then modify the $filter 

tag with new filter criteria. 

The new Documentation Factory for versions 2003 and 2007 does not support filtering in SQL format. 

Consequently, you must create and save a new filter on the server, and then modify the $filter tag with 

new filter criteria. 

The Document Factory option in the Requirements Grid is not available when the grid displays a single 

requirement. To make this option available, display the grid with multiple requirements and manually select 

the requirement. 

The current baseline is specified with $BASELINE{Current Baseline} instead of $BASELINE{Current}. 


Datamart 

Due to new enhancements, such as the versioning of traces, a Datamart extraction takes more time than it 

did with CaliberRM 2005. 

Borland Search 

Choosing Tools ➤ Borland Search does not open a Web browser if one is not already open. As a result, you 

must open a browser before choosing this menu item. 

Estimate Professional 

Clicking Close to close the project browser generates an error. To avoid this error, choose the menu item that 

allows you to close the project browser. 

The Import Project Data topic in the EstimatePro Help erroneously claims that MS Project 97 is supported. 

StarTeam Integration 

When opening several views on different tabs on the StarTeam page on the Traceability Modification dialog 

box, you might receive java.lang.Out.Of.Memory... messages. To avoid these messages, add an 

options=-Xmx256m or options=-Xmx512m line to the file StarTeamSDK10.ini, which is located in 

C:\Program Files\Borland\StarTeamSDK2008\Lib by default. 

An Out of memory message might appear when attempting to view the StarTeam trace history. 

Mercury Quality Center Integration 

CaliberRM 2006 to 2008 have default values for configuration files after upgrading in Mercury QC. 

If you use a non-English CaliberRM client with an English version of QC, characters other than English do not 

appear correctly in QC. To avoid this issue, install the corresponding QC language pack. 

Custom fields that are created in QC are also displayed in the Publish to Quality Center wizard, even though 

these fields are not modified when requirements are published. 

SilkCentral Test Manager Integration 

CaliberRM 2008 does not support SCTM 8.6 for synchronization. 

On the Traceability page, the project/ID text box lists the test type instead of its location. 

If a user is not connected to the SilkCentral database, attempting to create a trace to a SilkCentral test definition 

from the Traceability page generates an error. To avoid this error, connect to SilkCentral first. 

SCM Integration 

A trace to a file in Rational ClearCase does not appear on the Traceability page.To view a trace to a ClearCase 

file, refresh the Traceability page after creating the trace. 

CaliberRM SDK Installation 

CaliberRM SDK installation features a The system administrator has set policies to prevent 

this installation error from the CaliberRM SDK installer as well as the CaliberRM Server Install Caliber 

SDK option with an admin account. When installing CaliberRM SDK with the main installer (server and client), 

the running installer launches the CaliberRM SDK installer (.msi). This feature, known as nested installation 

or concurrent installation, has been deprecated because of the problems it causes for users. 

To avoid this issue, remove HKEY_CLASSES_ROOT\Installer\Products. 



The Requirements Grid slows down when viewing a large number of requirements. It is recommended that 

you use the document view instead. 

The Compare Baselines report is difficult to read when using the default width. Use the Windows Client to 

compare baselines. 

The options to trace to Borland StarTeam, Borland Together, Borland Silk, or Mercury QC do not allow users 

to create traces. Contact support to install the necessary add-ins. 

When MPX is enabled and the requirement tree is refreshed by MPX events, the current cursor position is 

lost. To avoid this situation, turn off MPX events on the Logon dialog box. 

Navigating to non-requirement software artifacts, such as Borland StarTeam elements, from a requirement 

might generate an error. It is recommended that you use the Windows Client to view these traces. 

After a refresh, the requirement navigator displays requirements as locked even though they are not locked 

and can be edited. 

In both Eclipse 3.2 and 3.3, when you view the Traceability page of a requirement with an SCTM trace attached 

to it in SCTM, the SCTM trace is not displayed. However, when you view the same requirement in CaliberRM, 

the SCTM trace is displayed. 

CaliberRM for Microsoft Visual Studio 2008 / Visual Studio 

Team Foundation 2008 

In Visual Studio 2008 integration, when you click Refresh on the CaliberRM Explorer toolbar, an empty message 

opens, and the Refresh command does not work. To close the empty message, click the left button. To refresh 

your CaliberRM project, either click Refresh after any requirements are opened or restart Visual Studio. 

In VSTS 2008 integration, changing the direction of two traces and saving them from the Traceability 

Modification dialog box results in an infinite hourglass prompt. Additionally, only one trace is displayed on 

the Traceability page. Closing the requirement and opening it again displays the appropriate traces. 

In Visual Studio 2008 integration, Visual Studio hangs when a CaliberRM project is removed. When multiple 

baselines for the same CaliberRM project are added to CaliberRM Explorer, Visual Studio sometimes hangs 

when you remove a project. This issue occurs only when requirements are opened in the Editor pane. To 

avoid this issue, close all requirements before removing a project. 

In Visual Studio 2008 Integration, when opening CaliberRM Explorer on Visual Studio 2008, a package load 

error occurs. CaliberRM Explorer is not displayed. In VSTS 2008 Integration, when connecting to CaliberRM 

Server from Team Explorer on Visual Studio 2008, the request never finishes. Both problems are caused by 

a missing J# library. As a result, users must install the J# redistributable separately because Visual Studio 

2008 no longer includes J#. It is recommended that you download Microsoft Visual J# ® 2.0 Redistributable 

Package, Second Edition (x86) from 

http://www.microsoft.com/downloads/details.aspx?FamilyId=E9D87F37-2ADC-4C32-95B3-B5E3A21BAB2C 

and install it before installing Visual Studio 2008 or VSTS 2008 Integrations. 

In Visual Studio Team foundation 2005 and 2008, while uninstalling CaliberRM for Team Foundation Server 

(TFS Integration), the uninstaller fails to unregister the CaliberRM entry. To remove the CaliberRM entries 

manually from the Microsoft Visual Studio Team Foundation Server 2005 (TFS 2005), perform the following 

steps: 

1. Run the command TFSReg with the /D switch before uninstalling, as the following example shows. 


TFSReg /D "C:\Program Files\Borland\CaliberRM For Team Foundation 

Server\Registration.xml" TfsIntegration 

TFSReg resides in the \Tools folder. 

Note: If you have uninstalled TFS Integration but cannot locate the file Registration.xml, contact 

support or reinstall TFS Integration. 

2. Uninstall TFS Integration. 

To remove the CaliberRM entries manually from Microsoft Visual Studio Team Foundation Server 2008 (TFS 

2008), perform the following steps: 

1. Run the command TFSReg with the /EXPORT switch, as the following example shows. 

TFSReg /EXPORT c:\temp\Registration.xml TfsIntegration 

TFSReg resides in the \Tools folder. 

2. Open the exported file. 

3. Search for the CaliberRM Type element. 

4. Remove the element, including the CaliberRM Type element, and save the file. 

5. Run the command TFSReg with the /OVERWRITE switch, as the following example shows. 

TFSReg /OVERWRITE c:\temp\Registration.xml TfsIntegration 

The following features of VS/VSTS2008 integration do not function properly on Vista: 

• Previewing in the Requirements Grid — Nothing is available for preview in the Print Preview view. 

• Adding multiple projects to CaliberRM Explorer — VS2008 crashes. 

• Storing CaliberRM connection information — Users must add a CaliberRM project every time. 

• Viewing images — Images in descriptions are always missing. 

• Opening the VSTS Tests page in Traceability Modification — An error occurs while opening the test list. 

This error occurs because a Visual Studio or VSTS integration requires administrative privileges to proceed 

with these features. To avoid this error, choose Run As Administrator from the context menu when you 

run Visual Studio. 

Copy the Visibroker.Net files to the corresponding directory of the Visual Studio installation. If the user 

has installed Visual Studio on another drive, VSTS integration cannot connect to the CaliberRM Server even 

though the VSTS Integration installer is hardcoded to install the Visibroker.Net DLL files in the directory 

C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies. If Visual 

Studio is installed on a drive other than the C:\ drive, copy the Visibroker.NET files to the corresponding 

directory of the Visual Studio installation after the integration. 

In the English and Japanese versions, VSTS hangs when trying to use 'Traceability 

modification'>'VSTS Test tab' to add TFS Server. In the French version, VSTS 2008 crashes when 

trying to use 'Traceability modification'>'VSTS Test tab' to add TFS Server. 


In VSTS 2005 and 2008 integration, changing the direction of two traces and saving them from the Traceability 

Modification dialog box results in an infinite hourglass prompt. Additionally, only one trace is displayed on 

the Traceability page. Closing the requirement and opening it again displays the appropriate traces. 

The options to trace to Borland StarTeam, Borland Together, Borland Silk, or Mercury QC do not allow users 

to create traces. Contact support to install the necessary add-ins. 


The integration cannot connect to CaliberRM servers with Secure Sockets Layer (SSL) enabled. To overcome 

this obstacle, perform the following steps: 

1. Open the folder in which the VSTS client is installed, such as C:\Program Files\Borland\CaliberRM 

Client For Visual Studio Team System. 

2. Right-click CaliberRM SSL.crt and choose Install Certificate. 

3. Click Next. 


5. Click Finish. 

Traceability to external software artifacts is not available. 

In Visual Studio 2005 integration, when you click Refresh on the CaliberRM Explorer toolbar, an empty 

message opens, and the Refresh command does not work. To close the empty message, click the left button. 

To refresh your CaliberRM project, either click Refresh after any requirements are opened or restart Visual 

Studio. 

In Visual Studio 2005 integration, Visual Studio hangs when a CaliberRM project is removed. When multiple 

baselines for the same CaliberRM project are added to CaliberRM Explorer, Visual Studio sometimes hangs 

when you remove a project. This issue occurs only when requirements are opened in the Editor pane. To 

avoid this issue, close all requirements before removing a project. 


When you view the Traceability page of a requirement with an SCTM trace attached to it from SCTM, the 

SCTM trace is not displayed. However, when you view the Traceability page of the same requirement in 

CaliberRM, the trace is visible. This limitation exists in Microsoft Visual studio as well. 

After uninstalling CaliberRM for Microsoft Visual Studio, Borland CaliberRM is still displayed among the installed 

products on the Visual Studio splash screen. 

The Owner text box of some requirements is not displayed on the Details page. 

The integration cannot connect to CaliberRM servers with SSL enabled. To overcome this obstacle, perform 

the following steps: 

1. Open the folder in which the VSTS client is installed, such as C:\Program Files\Borland\CaliberRM 

Client For Visual Studio Team System. 

2. Right-click CaliberRM SSL.crt and choose Install Certificate. 



5. Click Finish. 

Traceability to external software artifacts (other than VSTS work items and tests) is not available. 

When tracing a requirement to a VSTS test, an inner exception error might occur. Click OK to create the 

trace properly. 

CaliberRM Web Client 

Web Client 2008 does not display existing traces to SCTM 2007 artifacts. If a trace is created to an SCTM 

2007 artifact by using the Win32 Client, it is not visible under the Web Client. The Web Client displays traces 

only to SCTM 2008 artifacts. 

Upgrading CaliberRM Web keeps the previous version installed. 


On Windows XP SP2 and Windows 2003, choosing Help ➤ Help Content sometimes generates an error. To 

avoid this error, perform the following steps: 

1. Open Internet Explorer. 

2. Choose Tools ➤ Internet Options. 

3. Click the Advanced tab. 

4. Under Security options, click Allow active content to run in files on My Computer. 

5. Click OK. 

For more information, visit http://support.microsoft.com/kb/843017. 

Non-alphanumeric characters in requirement descriptions might not appear. Similarly, WMF files that are 

inserted into requirement descriptions might not appear properly. The hyperlinks in requirement descriptions 

are displayed but are not active. 

The Description text box of a trace to a Mercury QC object displays unreadable HTML code if the original QC 

object description is in HTML. 

Windows XP update (KB912945) and Update for Internet Explorer for Windows Server 2003 

64-bit Itanium Edition (KB912945) on Windows Server 2003 SP1 are incompatible with the Web 

Client. It is recommended that you uninstall the Microsoft update. 

Requirement names longer than 64 characters are not displayed. 

Properties of traces to Visual Studio work items are displayed incorrectly. 

The new Requirements Grid filter functionality works only in the Windows Client. The Web Client uses the 

previous Requirements Grid filter functionality for filtering. 

Limitations 

This section identifies the current limitations of the various CaliberRM components. 


Database administrative tasks cannot be performed by users other than the specific user who created the 

database. When creating the database, use a generic user ID like crmdb, which is not tied to a specific user. 

The following CaliberRM 2008 administration tools work only with the latest 2008 server: 

• CaliberRM Administrator 

• Datamart 

• RM Import 

• RM Export 

• LDAP Quick Start Manager 


You can run the client and the server on the same machine or on different machines. 

HP Quality Center Version 10.0 is supported for non-versioning projects. 

Note: Mercury QC 10.0 for Versioning Enabled Projects using CaliberRM Mercury Publisher and CaliberRM 

Test Wizard tools is not yet supported. 


While using Datamart to extract data to SQL Server 2000, the extraction fails if the data exceeds a row size 

of 8,060 bytes. This restriction is due to the limitations of SQL Server 2000. However, if the row sizes are less 

than 8,060 bytes, Datamart extraction is successful for SQL Server 2000. 

When you synchronize a requirement from SCTM, images added to the description of the requirement in SCTM 

are not displayed in CaliberRM after synchronization.The description pane displays only the URL of the image. 

To view the image, you must paste the image URL into a Web browser. 

The Import from Word function might not import tables properly. 

To install CaliberRM, users must possess write access to the directory /Program 

Files/Borland/CaliberRM. 

Information exported from the Requirement Grid into Excel is truncated at 255 characters per column. 

Large requirement descriptions might not appear in the grid. 

Pasting text from MS Word to requirement descriptions might result in lost formatting. It is recommended that 

you save documents as Web Page, Filtered first and then copy and paste the appropriate text in CaliberRM. 

The traceability diagram is not available from baselines. 

Information about Rational ClearCase files traced to requirements cannot be viewed in the traceability diagram. 

Matrix and grid filters are private to users and cannot be shared with other users. 

When starting CaliberRM 2008, grid and matrix filters are saved on the server instead of as RGV files on the 

user’s computer. Clicking Save saves the column layout in an RGV file. 

Previous versions of Document Factory (default for MS Word 2000 and earlier) cannot use grid and matrix 

filters (saved on server). If users have any filters (RGV files) from CaliberRM 2006, they can still use those 

filters in the previous version. Additionally, the string-based filtering mechanism can be used with previous 

versions of Document Factory. 

CaliberRM 2006 filters that are saved as RGV files cannot be used in the current Document Factory (default 

for MS word 2003 and later). 


Displaying a traceability matrix for a large set of requirements might take a long time 

Viewing traces might generate errors. As a result, it is recommended that you view traceability in the Windows 

Client. 

Use the default MPX port in the CaliberRM Server (Control Panel) for requirements to be automatically updated. 

To view traceability information, the current baseline must be opened. 


Document references that are set as key references are not displayed. It is recommended that you store 

requirement descriptions in CaliberRM. 

The ability to create traces to Borland StarTeam, Borland Together, Borland Silk, or Mercury QC is not available. 



Work items created in CaliberRM are not visible in Team Explorer until the user refreshes Team Explorer. 

Users must possess a non-empty CaliberRM authentication password. 

The ability to create traces to Borland StarTeam, Borland Together, Borland Silk, or Mercury QC is not available. 




Microsoft VS 2003 integration is no longer supported because mainstream support from Microsoft ended in 

October 2008. However, a defect in the installer displays the option to install VS 2003 integration. A future 

version of the CaliberRM installer will fix this bug and remove this installation option. 

For more information, visit http://support.microsoft.com/lifecycle/?LN=en-us&p1=3040&x=5&y=11. 

CaliberRM for Web 

Lengthy requirement descriptions might take a long time to appear. 

Traceability views might display errors. As a result, it is recommended that you view traceability in the Windows 

Client.

CaliberRMÂ® 2008 - Borland Technical Publications

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?