CaliberRM 2008 - Micro Focus Supportline · 2010-12-22 · • Microsoft Visual Studio 2008 Team...

CaliberRM® 2008Release Notes

Borland Software Corporation8310 North Capital of Texas HwyBuilding 2, Suite 100Austin,Texas 78731http://www.borland.com

Borland Software Corporation may have patents and/or pending patent applications covering subject matter in this document. Pleaserefer to the product CD or the About dialog box for the list of applicable patents.The furnishing of this document does not give youany license to these patents.

Copyright © 2009 Borland Software Corporation and/or its subsidiaries. All Borland brand and product names are trademarks orregistered trademarks of Borland Software Corporation in the United States and other countries. All other marks are the property oftheir respective owners.

ii

Contents

CaliberRM 2008 Release Notes...............................................................................5What'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 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 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 importantinformation that might not appear in the Help. It is recommended that you read these Release Notes in theirentirety. 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 NewThis section provides an overview of the new features found in CaliberRM.

Support for Third-Party Integration ToolsHP Quality Center Version 10.0 is supported for non-versioning projects. Support is not provided for MercuryQuality Center (QC) 10.0 for versioning-enabled projects that use CaliberRM Mercury Publisher and CaliberRMTest Wizard tools.

Enhanced Document FactoryA new version of Document Factory has been added to the product. This new version uses a set of XMLinterfaces to Word rather than the COM interfaces. This change results in the faster generation of documentsand allows the generation of more flexible templates in releases following v2008. Additionally, documents arenow generated without the use of an intermediate MS Access database because data is pulled directly fromthe server during generation.

The original Document Factory is still included. For any version of Microsoft Word v2003 or earlier, the defaultversion is the original Document Factory. For Word 2003 or 2007, you can choose either the new or the olddocument factory. The new Document Factory works with Microsoft Word version 2003 or later. To continueusing the previous version of Document Factory for Microsoft Word version 2003 or later, specify the appropriatepath in the registry. Otherwise, the new Document Factory is initiated by default for Microsoft Word version2003 or later. For more information, contact technical support.

Initial comparison results for document generation indicate that the new version of Document Factory cangenerate a document twice as fast as the previous version.

Access to Saved Grid and Matrix Filters in DocumentFactoryBeginning in v2006, the Traceability Matrix filter mechanism allowed users to save their filters. In v2008, thatfilter capability was added to the Requirements Grid. The filters that are created and saved can be accessedby keyword in the new Document Factory. As a result, the output is captured in the Document Factory whenthe filter is executed.

CaliberRM 2008 Release Notes | 5

http://techpubs.borland.com/caliber


API ChangesNew methods are provided for the following actions:

• Managing licenses though the SDK• Obtaining a checkpoint to view changes since a previous checkpoint

URL AddressabilityURL addressability allows you to create a URL for any given requirement. Navigation of the URL requires theuser to have installed the CaliberRM Client. The URL does not follow the traditional HTTP style because thetarget is directed to the CaliberRM application. The URL can be pasted into a browser or the Windows Rundialog box for execution. Users must log on if they are not already logged on to the target project.

Filter Mechanism on GridThe same filter mechanism that was added to the Traceability Matrix in v2006 is now available on theRequirements Grid, allowing you to build more complex filters and save those filters for reuse. Unlike filters inversion 2006, filters in the current version are saved on the server side. Consequently, performance is improveddue 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 MatrixBaseline 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 availablefor these fields.

Status Add-In Added to DatamartThe status attribute of items that are traced to CaliberRM by way of the traceability add-in are now includedin the Datamart extract. Users can include them in reports. For example, the status of a test case linked toQuality Center is now available in the Datamart extract.

Visual Improvement to Baseline Maintenance WindowRequirements can be deleted from the current baseline (but not from a selected baseline) yet remain availablebecause they are part of another baseline. In the Baseline Maintenance window, a visual clue differentiatesrequirements 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 ContentBecause of a major documentation conversion that was underway during the 2006 release, that version didnot contain all of the Help topics that were available in previous releases. The 2008 release completes theconversion and includes the missing topics that are relevant to v2008.

System Requirements and PrerequisitesThis section identifies the system requirements and prerequisites for the various CaliberRM components.

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

RequirementSystem Area

Platforms• 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 providerHardware requirements

VMware ESX Server 3.0.1VMware

1 GB (minimum); 30 GB or higher (recommended). Existingcustomers must have at least 2.5 times their currentdatabase size prior to upgrading.

Hard disk space

Note: The actual amount varies, depending on youruse of the product.

CaliberRM Windows ClientThe CaliberRM Windows Client is available in English, Japanese, French, and German. Only one of thesupported languages can be installed, and most of the supported languages must be installed on the matchingoperating 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.


Platforms• Windows XP Professional (SP2)• Windows Vista Enterprise Edition

Configuration recommended by OS providerHardware requirements

Internet Explorer 7.0Web browser


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


Eclipse 3.2, 3.3 (available for download fromhttp://www.eclipse.org)

Software

Configuration recommended by EclipseHardware requirements

CaliberRM for Microsoft Team Foundation ServerThe following table identifies the system requirements for installing and running CaliberRM for Microsoft TeamFoundation Server.


Refer to Visual Studio Team Foundation Installation Guide,available for download athttp://www.microsoft.com/downloads/details.aspx?familyid=ff12844f-398c-4fe9-8b0d-9e84181d9923&displaylang=en

Platforms

Software• 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 System2005 and 2008CaliberRM for Microsoft Visual Studio Team System is available in English and Japanese. Only one of thesupported 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 MicrosoftVisual Studio Team System 2005 and 2008.


Refer to the Microsoft system requirements athttp://msdn.microsoft.com/en-us/vsts2008/aa718944.aspx

Platforms

Refer to the Microsoft system requirements at the followinglocations:

Processor, RAM

• http://msdn.microsoft.com/en-us/vsts2008/aa718687.aspxfor Visual Studio 2005 Team Edition for SoftwareDevelopers

• http://download.microsoft.com/download/A/2/8/A2807F78-C861-4B66-9B31-9205C3F22252/VS2008SP1Readme.htmfor Visual Studio 2008 Team Edition for SoftwareDevelopers


http://www.eclipse.org

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

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

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

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


Software• 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 Microsoftended 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 WebThe following table identifies the system requirements for installing and running CaliberRM Web.


Web server• Apache (provided)• IIS

Internet Explorer 6.0 SP1, 7.0Client browser

1.6, 1.6.x.xJDK/JRE

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

Tested VersionSupported ProductCaliberRM Feature

2006, 2008Borland StarTeamTraceability

2006, 2007Borland Together for Eclipse

2006 (8.5), 2007 (8.6), 2008 (8.8)Borland Silk Central Test Manager

2003IBM Rational ClearCase

6.8Merant PVCS Version Manager

9.0, 9.2, 10.0Mercury Quality Center

6.0 SP6Microsoft Visual SourceSafe

Document Factory reports, documentreferences, and requirements export (toAccess) and import (from Word)

• Microsoft Office 2000 (reports usingolder Document Factory only), 2003,2007

• MS Word 2000, 2003, 2003 SP2,2003 SP3, 2007

• MS Excel 2000, 2003, 2003 SP2,2003 SP3, 2007

6.5, 11Business ObjectsDatamart extraction targets and analysistools

2003, 2007Microsoft Access


Tested VersionSupported ProductCaliberRM Feature

2000, 2005Microsoft SQL Server

10gOracle Database Server

2006Borland Developer Studio ©++ Builder,C# Builder, Delphi)

Integrated Development Environment(IDE) integrations

2005, 2006Borland JBuilder

Visual Studio 2005 SP1, 2008Microsoft Visual Studio

2005 SP1, 2008Microsoft Visual Studio Team System

3.2, 3.3Eclipse

2.0Apache Web ServerWeb server

2000 (5.0), 2003 (6.0)Microsoft Windows Server InternetInformation Services (IIS)

8.2aMacroVision FlexLMSoftware license servers

—2000 (5.0), 2003 (6.0)Microsoft Windows Server InternetInformation Services (IIS)

3.0.1VMware ESX ServerVMware

Installation and Upgrade InstructionsThe upgrade procedure has changed from previous releases. Existing customers are encouraged to reviewthe Performing an Upgrade section of the Installation Guide, which is available from the BorlandDocumentation Web site at http://techpubs.borland.com/caliber.

CaliberRM ServerIf the database contains a large number of traces, the server database size might grow noticeably during theupgrade.This growth is due to the introduction of traceability versioning in this release. If you have unnecessarytraces that are either created manually or copied and pasted from a previous requirement, it is recommendedthat you remove them before upgrading. For more information, contact support or visit Borland Answers athttp://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 notrecompile your application with the included SDK. In general, when writing SDK applications, use the sameversion of the SDK as the version of the oldest server to which the application must connect.You must recompileyour .NET/COM SDK applications to make use of the new SDK functionality provided in this release, such ascreating 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.

CaliberRM Windows ClientInstallation instructions for the CaliberRM Windows Client depend on whether the client is installed on a machinethat is different from the server. For more information, refer to the Installation Guide.



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

CaliberRM for EclipseFor installation instructions, refer to the Installation Guide.

CaliberRM for Microsoft Visual Studio 2005For installation instructions, refer to the Installation Guide.

CaliberRM for Microsoft Visual Studio 2008For installation instructions, refer to the Installation Guide.

CaliberRM for Microsoft Visual Studio Team SystemPrior to installing the CaliberRM Client for Visual Studio Team System (VSTS), your VSTS administrator mustinstall CaliberRM for Team Foundation Server on the machine that hosts Team Foundation Server. TheCaliberRM 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 establishtraceability between requirements and VSTS work items as well as tests from Visual Studio.

For installation instructions, refer to the Installation Guide.

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

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

DescriptionChange Request NumberCategory

In the traceability matrix, the action ofright-clicking the cell that represents a

44061Traceability Matrix

trace between a requirement and anexternal vendor object causes thematrix to hang.

Prevents CaliberRM Server fromexposing the physical host name toCaliber Client.

43991CaliberRM Server




Error message CaliberRMInternal Error: 91-CD opens

44049CaliberRM Win32 Client

for a requirement while saving a childrequirement on the References page.

Deleted users can still be edited in themultiple selection user list (MSUL) UDAfor Win32 Client.


Data is duplicated when migrating DBfrom 2005 to 2008.

44032Migration

Datamart cannot complete extractionson large databases.

44031Datamart

Deleted users can still be selected inthe MSUL UDA for Win32 Client.

Synchronization from DefineITgenerates a namespace error inCaliberRM Client's history view.


Synchronization from a DefineITrequirement with a specific word tag

44022Integration with DefineIT

causes the error NameSpace errorin the History view of the CaliberRMClient.

After installing the current version of thepatch, the previous patch still appears

44022Patch installer

in the Add or Remove ProgramsControl Panel applet .

When running Datamart with the option-update -depth 1, the number ofupdated traces is larger than expected.

43968Datamart

Datamart crashes when trying to extracttraces from a large database.

43967Datamart

When user filters for a UDA value in theRequirements Grid return no matches,the column disappears from the grid.

23993Requirements Grid



Error Object_does_not_existoccurs when you call

43952CaliberRM SDK

projectmanager.getproject(projectid)for an empty project.

When you create a UDA of typemultiple-line text and set the maximum

43890CaliberRM Datamart

length to 10,000 (i.e., when arequirement is set with value of 10,000



characters), it is truncated to 2,048characters when extracted to MSAccess.

Deleted values of the MSUL attributestill appear in the Requirements Grid.


Requirements can be modified throughthe Requirements Grid with deletedvalues.

In the General Options section of theSpelling page (CaliberRM ➤ Tools ➤


Options ➤ Spelling), parent-childrelationship are not followed by checkboxes.

Parent: Always check spelling beforesaving requirements.

Child: Check spelling only if therequirement's description is modified.

Broken functionality with the client-sideoption to create a child-to-parent traceupon requirement creation.


The new Document Factory refuses tolog on if password is expired. Unlike the

43771CaliberRM DocFactory

new Document Factory, the previousversion handles this situation byprompting the user for a new password.

External Trace Status does not workwith Silk Central Test Manager (SCTM)2008 R2 SP1.


Linking Service fails to log on to SCTM.42701CaliberRM Win32 Client

MPX event notification in FrameworkAdministrator; changes made to a group


are not saved if the same record isedited on another instance.



After navigating backward in the newDocument Factory wizard, the last


button clicked is presented as thedefault selection instead of Next orFinish.

The Import from Word functioninappropriately imports text into the

43633CaliberRM Client

requirement description that is specified



by a style to become the requirementname.

When you invoke the DocumentFactory, the StarTeam toolbar does not


cache the logon information. The firstpage is prepopulated with the lastlogged-on server, and the user name isretrieved from the registry.

The Password text box also appearsto be prepopulated. However, thePassword text box is alwaysprepopulated with the passwordadmin.

The new Documentation Factory throwsan unhandled exception if a user clicks


OK to close the message and thennavigates back to Page 1 from Page 2.

The new Documentation Factory hangswhen you click Close on forms otherthan the Startup form.


Any changes to the old versions ofrequirements are not displayed in thehistory.


A requirement and its children appearas read-only objects. The CaliberRM


Client shows the previous requirementversion instead of the current one.

When running a Datamart extraction toMS Access or SQL, the special


character " " is stripped out along withall HTML tags.This action removes anyspaces that lie between words in theresulting requirement description.

The extension of the default result fileis .doc. The new Documentation


Factory does not support the extension.docx.

When performing Datamart extractions,the requirement name is truncated if itcontains more that 64 characters.


In the new Document Factory, all linereturns are removed from the validationprocedure in the resulting document.


The new Document Factory does notremember form data, such as a user's


password, if the previous operationfailed.



Unable to use more than one$REQTREE command in DocumentFactory reports.


When you start the new DocumentFactory from within CaliberRM 2008, it


does not save the user name andpassword even though it appears tosave them.

The new Document Factory does notreturn any requirements if the


requirement type is more than 64characters in length.



Requirement names that contain thefollowing characters fail to publish toQuality Center.

43723CaliberRM Client/Server

Users do not have the rights to modifythe registry key to launch the old


Document Factory. The registry key isbased on HKEY_LOCAL_MACHINEinstead of HKEY_CURRENT_USER.

The Datamart -update commanddoes not manage deletions from theResponsibilities list.


Running the new Document Factoryfrom the CaliberRM Client produces a


different result from running the newDocument Factory directly from theexecutable. Baseline information isignored in the new Document Factorytemplate when it is run from the client.

The requirement description is affectedwhen the font family or font is changed


in Internet Explorer (IE). However, if thefont family and size are not definedwithin the HTML code, they arereflected in the requirement'sdescription when you change the IEsettings.

Project descriptions are printedincorrectly.


After the new Document Factorygenerates a document, it does not




prompt the user to open the resultingXML or DOC file.

Exporting a large matrix to XML causesit to crash.


Incorrect focus cycle among GUI inputfields on the wizard pages of theDocument Factory.




Data inconsistencies are encounteredfrom concurrent Requirements Gridmodifications.


CaliberRM hangs when defining anumeric filter for a grid.


When you right-click a trace and chooseproperties on the UDA page, the UDAs


for the target requirement are not visiblewhen using a newer database.

A Last TransactionIncomplete message is displayed


on the Traceability page when therequirement version is not from thecurrent baseline.

When using the Customer database,one of the multiple Requirements Grids


crashes when launched in parallel. If atimeout exception from the serveralready exists, the client must requestthe data again.

A message states that requirementshave been deleted when they have not


created a new message, most likelybecause it was reusing an existingmessage not intended for this use.

Hyperlinks to files on a server do notwork on save.


Java API can perform only the mappingof requirements, not unmapping.

43542CaliberRM SDK

In the new Document Factory,requirements with date and multitext


line UDAs are not generated properlyin reports.




When you choose Tools ➤ Options ➤Spelling to open the Spelling page in


a non-English CaliberRM client, theclient crashes with a debug error.

Deleted traces between a file object anda requirement that is present in a


non-current baseline appear in theTraceability Matrix.

Default values for options in the Versantfile profile.be need to be updated.




WorkItem properties do not open forVSTS 2008 traces. Properties have


been re-referenced to correct theMicrosoft Visual Studio Team System2008 DLLs based on the location of theinstallation.

The status and project paths of tracesto StarTeam items are not refreshed


when the items are moved or deleted.Because this fix requires StarTeam SDKchanges, it is recommended that youupgrade to StarTeam SDK 10.0.60 or10.1.

When a StarTeam item is checked out,the status of the trace must be changed


to suspect. The behavior of thecheckout operation is changed in theCaliberRM client to change the tracestatus to suspect.

When the MPX component for BorlandSearch Server is enabled, an error


occurs if the MPX server is installed ona different machine.

When a trace to Team System Test isremoved through Win32 Client, an erroris displayed for longer strings.


SDK fails to save baseline information.This issue was introduced in

43167CaliberRM SDK



Hotfix34c-2006.BaseLineTreeNode object isconverted back to UTF8 whencommunicating with the server.

CaliberRM SDK throws various typesof exceptions due to data corruption or

42919CaliberRM SDK

the mishandling of data while parsing.The issue was fixed by converting thexHTML/XML string into an XMLdocument while parsing and validatingrequirement descriptions.



The cursor jumps to the top of theparagraph after pasting text into a table.


The Import from Word function failswhen using MS Office 2007. When


importing from Word, the import failswhen using the plain-text option,resulting in an orphanedWinword.exe.

The Datamart outputs unnecessaryinformation.


The time format is inconsistent whenrunning Document Factory.


Requirement Viewer takes a long timeto load requirement information basedon change request management (CRM).


CaliberRM license status is Missingafter it is assigned from the BorlandLicense Server page.


The -depth command does notupdate for MS SQL server and Oracle


server usage. Only MS Access hasupdate information for -depth.

Customers requested to removeHotfix54-2006 behavior because they


want to revert the earlier request tocreate the same Hotfix.

Performance decreases when using2008 filters to filter subrequirements ofrequirement IDs within a range.




Unable to log on to CaliberRM by usingLDAP if the password contains alocalized character, such as é or à.


CaliberRM SDK 2008 fails to retrievetraces for project.


Borland Search continually fails with themessage

41285CaliberRM SDK

java.lang.OutOfMemoryError:Java heap space.



Limit the number of traces output in theDatamart extraction to a set number orlevel.


Fails when running an extraction withthe -update command with Datamart.


Datamart -update option fails whileextracting large volume of requirements.


Datamart -update option does notuse paging.


Datamart -update option does notproperly export the Responsibilitieslist.


When performing maintenance onvarious projects and baselines, the error


last transactionincomplete is thrown.



Sorting does not function properly onthe Add Baseline Signatories dialogbox.


Deleting the current baseline version ofa requirement does not mark theattributes as deleted.


When traces are deleted, new versionsof trace objects are created.




UDA issues occur when makingchanges to the requirement baseline orto the requirement type.


The new Document Factory cannothandle German special characters.


When using Datamart to extract history,the changes in requirements relating to


multiple-selection UDAs are notexported appropriately.

Deleted users are unavailable forassignment to Project Administratorstatus.


Creation of Caliber requirements inTogether 2007 SP1 fails.


The new Document Factory does notembed images and other objects into


the resulting document. Instead, itcreates them as links.

HTML code is displayed in QCIntegration property windows.


When Document Factory fails from thecommand-line interface, a


winword.exe orphan is left runningas a process.

Document Factory $Begin_List<> $End_List repeats the firstreference.


While launching a new DocumentFactory from CaliberRM Win32 Client,


the server credentials are not passedto the Document Factory client.

The Document Factory keywords do notoutput glossary terms in alphabeticalorder.


The new Document Factoryexperiences usability issues in default


server credentials, user names, errorhandling, and the display behavior ofwindows.

Some German characters do not appearproperly in the Web client.


Cannot view images in the newDocument Factory output.


Datamart configuration does not supportthe exporting of all baselines when theAll Projects option is selected.




Datamart extraction fails whenSQLLDR's input file exceeds 2 GB.


Datamart Configurator does not properlyedit saved configuration files with morethan 200 projects.


Trace Set status is not displayed inWin32, Document Factory, Datamart,and Web Client.

42020, 41050, 41679CaliberRM Client

Exclude external traces for Export toAccess function.


Cannot filter on the Usermultiple-selection listbox UDA in theTraceability Matrix.


If you filter by responsibility in the 2008Requirements Grid, no requirementsare returned.


New or modified UDAs do not appearfor most requirements. The


Requirements Grid returns incorrectlists.

The Requirements Grid and theCaliberRM Client display different UDAdates.


Grid export to CSV defect. TheDescription text box is truncated to 256


characters in Requirements Grid PrintPreview.

CaliberRM Client crashes when editingmultiple requirement fields in the


Requirements Grid while requirementsare locked by other users.

When adding a glossary term to aglossary that already exists, the clientdoes not refresh appropriately.


Caliber Connection to HP QualityCenter 9.2 over HTTPS. Caliber 2008


Publish to Quality Center / Test Wizardover HTTPS is not working.

Regression issues with Datamart’s-update option.


Error message while deleting arequirement when the audit log isenabled.


Read-only users can shift requirements.42087CaliberRM Server

Performing baseline maintenance on anewly created baseline throws a Lasttransaction incomplete error.




German umlauts are not displayedappropriately in the CaliberRM 2008Web Client.

42255CaliberRM Web Client

Visual Studio 2005 integration does notrelease the logon credentials.

42032VS 2005 Integration

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

DescriptionChange Request NumberHot Fix

The Caliber Datamart project fails forlarge databases. The job hangs for

41815Hot Fix 01C

approximately an hour and then failswith a Get requirement treeerror or a getserver error.

Document Factory does not take intoaccount any of the changes to thedefault security profile.

41770Hot Fix 01C

Users who are not part of the Admingroup are unable to run Document

41812Hot Fix 01C

Factory. They receive a User notauthorized message.

Datamart extraction fails.41205Hot Fix 01C

Datamart needs to utilize the parameter-SQLLDR during Oracle extractions toimprove performance.

41457Hot Fix 01C

The -update parameter does notfunction when used with Oracle. Its

41502Hot Fix 01C

usage causes a failure without buildingthe database.

Document Factory stops with a Valueout of range message.

40811Hot Fix 01C

SCM traces the output ERROR:Invalid ID instead of the traced-toobject's name in Document Factory.

41487Hot Fix 01C

The Requirements Grid filter returnsincorrect results when filtering on thedescription.

41850Hot Fix 2

When using the Paste Specialfunctionality to copy a requirement with

21768Hot Fix 2, 3

traces, the suspect statuses of thetraces are lost.


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


CaliberRM CRMDiag Tool not includedin v2008.

40728Hot Fix 16

CaliberRM CRMDiag Tool not includedin v2008.

40811Hot Fix 17

CaliberRM SDK application error.23417Hot Fix 18



Traceability Matrix shows requirementsfor projects to which the user does nothave access.

40929Hot Fix 19, 20


Datamart Extraction failing.41205Hot Fix 22, 22c

When a requirement is deleted in 2006,it appears to be left in a hanging status

40538Hot Fix 24

but still appears in searches, DocumentFactory reports, and stopping-baselineabilities.

After deleting a requirement, unreaddiscussions still appear. The owner of

40538Hot Fix 24

the discussion appears as?<*>|<*>?.

CaliberRM 2006. Docfactory.exeversion 9.0.906.0.

40811Hot Fix 25

The Traceability Matrix displaysrequirements for projects to which theuser does not have access.

40538Hot Fix 26

Datamart does not utilize the parameter-SQLLDR during Oracle extractions.

41457Hot Fix 27c

When importing from Word, arequirement name is truncated to 64

41326Hot Fix 28c

characters even though the CaliberRMClient supports requirements withnames of 128 characters.

SCM traces the output ERROR:Invalid ID instead of the traced-toobject's name in Document Factory.

41487Hot Fix 29c

The usage of the -update parameterwith Oracle results in a failure withoutbuilding the database.

41502Hot Fix 31c

The map-requirement functionalitycannot be used with the SDK (applies

41577Hot Fix 32c



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.

41595Hot Fix 33c

HTML returned from a requirementobject contains inappropriate UTF-8

41261Hot Fix 34c

characters for symbols pasted fromWord documents, such as curly quotes,minus signs, and bullets.

CaliberRM does not delete projectsappropriately.

41594Hot Fix 37

When using the Traceability Matrix withfilters, CaliberRM returns aGeneralObject message.

41674Hot Fix 38c

The User multiple-selection listboxdisplays deleted users.

41619Hot Fix 38c

When you move a value within amultiple-selection listbox, the filter withinthe Traceability Matrix breaks.

41626Hot Fix 39c

CaliberRM displays duplicaterequirement versions and traces.

41681Hot Fix 40

Some German and unicode charactersdo not appear properly in the WebClient.

40321Hot Fix 41c

No pop-up messages, such as objectdoes not exist, should occur

41664Hot Fix 42c

when running Datamart extractions.This feature is designed as acommand-line tool for use withautomated scripts. As such, it does notfeature any GUI components.Information messages should be loggedto the screen and/or log files with moredetailed information.

After applying Hotfix 33c (extractor), theDirection text box in the TRACE tablecontains unreadable values.

41741Hot Fix 42c

When you move a value within amultiple-selection listbox, the filter withinthe Traceability Matrix breaks.

41626Hot Fix 43c

The cursor jumps to the top of theparagraph after pasting text into a table.

41351Hot Fix 44c

Using the $RGVFILE tag in DocumentFactory to filter requirements onHierarchy# returns incorrect results.

41910Hot Fix 45c


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

CaliberRM Client

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

CaliberRM Server

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 IssuesThis section identifies known issues with the various CaliberRM components.

CaliberRM ServerThe released software download displays Unknown Publisher instead of is signed by Borland. Formore 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 bydefault. If you used MPX events with your CaliberRM 2005 Release 2 Server and are planning to continueusing MPX events, click Enable MPX Events on the MPX Configuration dialog box. This option requiresStarTeam Message Broker.

Evaluation users: If you reinstall a trial version of CaliberRM 2008 Server on a Windows XP machine, yourinstallation might fail. To prevent failure, stop the SQM Monitor and SQM Database Windows Services beforereinstalling.

During the upgrade, the CaliberRM Server settings in the Control Panel applet are lost. Save these settingsprior to upgrading and restore them afterward.

When attempting to install the CaliberRM Server from a remote location, the message Error 1706: novalid source could be found appears. Avoid this message by running the installer locally from theserver machine.

Borland License Server users: The per-user license assignment (named or concurrent) needs to be manuallyrestored after an upgrade. If your CaliberRM server is configured to use Borland License Server (BLS) licensesonly, change the Admin user license type to BLS to log on to the CaliberRM Server while using the CaliberRMClient as Admin. In this case, connections of the Admin user to the CaliberRM Server by using the CaliberRMClient are counted by the BLS Server against the available licenses. The type of license acquired (named orconcurrent) depends on the type of the particular BLS license assigned to the Admin user.

CaliberRM Windows ClientThis section identifies known issues with CaliberRM Windows Client.


http://support.microsoft.com/kb/922225/en-us#appliesto

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 Programfiles 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 withdelimiters or keywords. Instead, the topic needs to state that you can import requirement descriptions onlywith delimiters and keywords.

The Datamart topic launched from the Configurator wizard contains an inappropriate path for launching theConfigurator. 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 mightnot 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 remotetraces. 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 dueto 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 existmessages, and the import is not successful. A second run of the import succeeds.


http://support.microsoft.com/kb/843017

When you use the CaliberRM SDK to create a user, the User Can Manage Glossary Terms permissionis enabled by default. No SDK option exists to deselect this permission. However, if this permission needs tobe 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 usethe SDK cannot process surrogate pair characters appropriately.

If you do not have the corresponding OLE object software installed, the Edit object command, withoutwarning, 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 somerequirements. To avoid this issue, use ID equals <requirement ID> as a filter criteria to display onerequirement 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 incurrent baseline.

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

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

Document Factory

Due to a localization issue, the Document Factory's logging directory is changed from C:\Documents andsettings\Local Settings\Application Data\Borland\CaliberRM\Log to C:\Documents andsettings\\Local Settings\Application Data\Borland SoftwareCorporation\Borland\CaliberRM\Log.

If you are generating Document Factory with requirement trace-to-SCTM linking service, the external tracedoes not appear in the document.

When running a previous version of Document Factory (with MS office 2000), you must click the Multipleoption 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 duringdocument generation when the $filter command, which contains the old Document Factory syntax, is usedin the template.To avoid this message, create and save a new filter on the server, and then modify the $filtertag 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 withnew filter criteria.

The Document Factory option in the Requirements Grid is not available when the grid displays a singlerequirement. To make this option available, display the grid with multiple requirements and manually selectthe 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 itdid with CaliberRM 2005.

Borland Search

Choosing Tools ➤ Borland Search does not open a Web browser if one is not already open. As a result, youmust 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 thatallows 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 dialogbox, you might receive java.lang.Out.Of.Memory... messages. To avoid these messages, add anoptions=-Xmx256m or options=-Xmx512m line to the file StarTeamSDK10.ini, which is located inC:\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 notappear 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 thoughthese 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 definitionfrom 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 ClearCasefile, refresh the Traceability page after creating the trace.

CaliberRM SDK Installation

CaliberRM SDK installation features a The system administrator has set policies to preventthis installation error from the CaliberRM SDK installer as well as the CaliberRM Server Install CaliberSDK 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 installationor concurrent installation, has been deprecated because of the problems it causes for users.

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


CaliberRM for EclipseThe Requirements Grid slows down when viewing a large number of requirements. It is recommended thatyou use the document view instead.

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

The options to trace to Borland StarTeam, Borland Together, Borland Silk, or Mercury QC do not allow usersto 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 islost. 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 requirementmight 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 lockedand can be edited.

In both Eclipse 3.2 and 3.3, when you view the Traceability page of a requirement with an SCTM trace attachedto 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 StudioTeam Foundation 2008In Visual Studio 2008 integration, when you click Refresh on the CaliberRM Explorer toolbar, an empty messageopens, and the Refresh command does not work. To close the empty message, click the left button. To refreshyour 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 TraceabilityModification dialog box results in an infinite hourglass prompt. Additionally, only one trace is displayed onthe 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 multiplebaselines for the same CaliberRM project are added to CaliberRM Explorer, Visual Studio sometimes hangswhen you remove a project. This issue occurs only when requirements are opened in the Editor pane. Toavoid this issue, close all requirements before removing a project.

In Visual Studio 2008 Integration, when opening CaliberRM Explorer on Visual Studio 2008, a package loaderror occurs. CaliberRM Explorer is not displayed. In VSTS 2008 Integration, when connecting to CaliberRMServer from Team Explorer on Visual Studio 2008, the request never finishes. Both problems are caused bya missing J# library. As a result, users must install the J# redistributable separately because Visual Studio2008 no longer includes J#. It is recommended that you download Microsoft Visual J#® 2.0 RedistributablePackage, Second Edition (x86) fromhttp://www.microsoft.com/downloads/details.aspx?FamilyId=E9D87F37-2ADC-4C32-95B3-B5E3A21BAB2Cand 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 entriesmanually from the Microsoft Visual Studio Team Foundation Server 2005 (TFS 2005), perform the followingsteps:

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


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

TFSReg /D "C:\Program Files\Borland\CaliberRM For Team FoundationServer\Registration.xml" TfsIntegration

TFSReg resides in the \Tools folder.

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

2. Uninstall TFS Integration.

To remove the CaliberRM entries manually from Microsoft Visual Studio Team Foundation Server 2008 (TFS2008), 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 proceedwith these features. To avoid this error, choose Run As Administrator from the context menu when yourun Visual Studio.

Copy the Visibroker.Net files to the corresponding directory of the Visual Studio installation. If the userhas installed Visual Studio on another drive, VSTS integration cannot connect to the CaliberRM Server eventhough the VSTS Integration installer is hardcoded to install the Visibroker.Net DLL files in the directoryC:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies. If VisualStudio is installed on a drive other than the C:\ drive, copy the Visibroker.NET files to the correspondingdirectory of the Visual Studio installation after the integration.

In the English and Japanese versions, VSTS hangs when trying to use 'Traceabilitymodification'>'VSTS Test tab' to add TFS Server. In the French version, VSTS 2008 crashes whentrying to use 'Traceability modification'>'VSTS Test tab' to add TFS Server.

CaliberRM for Microsoft Visual Studio 2005In VSTS 2005 and 2008 integration, changing the direction of two traces and saving them from the TraceabilityModification dialog box results in an infinite hourglass prompt. Additionally, only one trace is displayed onthe 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 usersto create traces. Contact support to install the necessary add-ins.


The integration cannot connect to CaliberRM servers with Secure Sockets Layer (SSL) enabled. To overcomethis obstacle, perform the following steps:

1. Open the folder in which the VSTS client is installed, such as C:\Program Files\Borland\CaliberRMClient For Visual Studio Team System.

2. Right-click CaliberRM SSL.crt and choose Install Certificate.3. Click Next.4. 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 emptymessage 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 VisualStudio.

In Visual Studio 2005 integration, Visual Studio hangs when a CaliberRM project is removed. When multiplebaselines for the same CaliberRM project are added to CaliberRM Explorer, Visual Studio sometimes hangswhen you remove a project. This issue occurs only when requirements are opened in the Editor pane. Toavoid this issue, close all requirements before removing a project.

CaliberRM for Microsoft Visual Studio Team SystemWhen you view the Traceability page of a requirement with an SCTM trace attached to it from SCTM, theSCTM trace is not displayed. However, when you view the Traceability page of the same requirement inCaliberRM, 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 installedproducts 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, performthe following steps:

1. Open the folder in which the VSTS client is installed, such as C:\Program Files\Borland\CaliberRMClient For Visual Studio Team System.

2. Right-click CaliberRM SSL.crt and choose Install Certificate.3. Click Next.4. Click Next.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 thetrace properly.

CaliberRM Web ClientWeb Client 2008 does not display existing traces to SCTM 2007 artifacts. If a trace is created to an SCTM2007 artifact by using the Win32 Client, it is not visible under the Web Client. The Web Client displays tracesonly 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. Toavoid 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 areinserted into requirement descriptions might not appear properly. The hyperlinks in requirement descriptionsare displayed but are not active.

The Description text box of a trace to a Mercury QC object displays unreadable HTML code if the original QCobject description is in HTML.

Windows XP update (KB912945) and Update for Internet Explorer for Windows Server 200364-bit Itanium Edition (KB912945) on Windows Server 2003 SP1 are incompatible with the WebClient. 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 theprevious Requirements Grid filter functionality for filtering.

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

CaliberRM Server

Database administrative tasks cannot be performed by users other than the specific user who created thedatabase. 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

CaliberRM Windows Client

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 CaliberRMTest Wizard tools is not yet supported.


Refer to http://support.microsoft.com/kb/843017

While using Datamart to extract data to SQL Server 2000, the extraction fails if the data exceeds a row sizeof 8,060 bytes. This restriction is due to the limitations of SQL Server 2000. However, if the row sizes are lessthan 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 SCTMare 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 /ProgramFiles/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 thatyou 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 theuser’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 matrixfilters (saved on server). If users have any filters (RGV files) from CaliberRM 2006, they can still use thosefilters in the previous version. Additionally, the string-based filtering mechanism can be used with previousversions of Document Factory.

CaliberRM 2006 filters that are saved as RGV files cannot be used in the current Document Factory (defaultfor MS word 2003 and later).

CaliberRM for Eclipse

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 WindowsClient.

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.

CaliberRM for Microsoft Visual Studio 2005

Document references that are set as key references are not displayed. It is recommended that you storerequirement descriptions in CaliberRM.

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


CaliberRM for Microsoft Visual Studio Team System

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.



CaliberRM for Microsoft Visual Studio 2003

Microsoft VS 2003 integration is no longer supported because mainstream support from Microsoft ended inOctober 2008. However, a defect in the installer displays the option to install VS 2003 integration. A futureversion 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 WindowsClient.



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

CaliberRM 2008 - Micro Focus Supportline · 2010-12-22 · • Microsoft Visual Studio 2008 Team...

Documents

Transcript of CaliberRM 2008 - Micro Focus Supportline · 2010-12-22 · • Microsoft Visual Studio 2008 Team...