CaliberRMÂ® 2008 - Borland Technical Publications

More documents

Recommendations

Info

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}. 28 | CaliberRM 2008 Release Notes
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. CaliberRM 2008 Release Notes | 29
Page 1 and 2: CaliberRM® 2008 Release Notes
Page 3 and 4: Contents CaliberRM 2008 Release Not
Page 5 and 6: CaliberRM 2008 Release Notes Octobe
Page 7 and 8: Help Content Because of a major doc
Page 9 and 10: System Area Software Requirement
Page 11 and 12: CaliberRM for Eclipse For installat
Page 13 and 14: Category CaliberRM Win32 Client Cal
Page 15 and 16: Category CaliberRM DocFactory Calib
Page 17 and 18: Resolved Issues for Patch 5 The fol
Page 19 and 20: Category CaliberRM Server CaliberRM
Page 21 and 22: Category CaliberRM Client CaliberRM
Page 23 and 24: Resolved Issues for 2006 The follow
Page 25 and 26: Updated Files in Patch This section
Page 27: Localization Only some of the strin
Page 31 and 32: TFSReg /D "C:\Program Files\Borland
Page 33 and 34: On Windows XP SP2 and Windows 2003,
Page 35: To view traceability information, t

CaliberRMÂ® 2008 - Borland Technical Publications

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

Delete template?

Save as template?