Borland® Caliber 11.0 Release Notes

11.0.2

Last updated: January 18, 2013

Welcome to Caliber 11

The Caliber 11 release introduces a new product organization, including new and re-written components with innovative capabilities.  The intuitive organization provides three main components:

Author – Requirement authors deserve a rich, robust authoring environment.  Author provides:

• modern Windows requirement authoring environment
• stylish “ribbon” interface grouping common user actions together for better usability
• common user actions grouped together to provide improved productivity for both existing and new users

Visualize – Allows users to see visual representation of use cases, process flows and interactive simulation, and directly relate visualizations to requirements. Visualize provides:

• ability to define/capture visual business scenarios, story boarding, and interactive simulation via a browser interface
• simulation and scenario execution, allowing remote users to stay in sync with requirement development and change
• collection of feedback from stakeholders, early in the development process

Review - Keeps all project stakeholders in sync by facilitating the viewing and searching of Caliber requirements / visualizations, and providing collaborative discussion. Review provides:

• all business stakeholders the ability to review, to contribute and to be fully engaged with project requirements
• immediately synchronized visibility to discussions across all three components (Author, Visualize and Review)

The Caliber Release Notes describes the system requirements/prerequisites and software compatibility requirements for this release of Caliber. For the latest version of this document, go to http://supportline.microfocus.com/productdoc.aspx.

What's New in 11.0.2

Author

No new features in 11.0.2.

Visualize

Usability Enhancements

Visualize has several usability enhancements. They are:

• Smoother function because it blocks updates for objects being deleted. Additionally, persistent backend issues have been resolved.
• In editors, Visualize now supports the Delete key to delete selected object(s).
• Visualize now has rubber-banding capabilities in scenario and simulation editors. Users can drag the mouse to select a group of objects.
• Improved consistency and usability of editor actions.
• When opening a project, the Scenarios screen appears by default.
• Easier to select connectors in editors.
• New rectangle size now defaults to size of last rectangle created.
• Enhanced undo capabilities.
• In simulation and scenario editors if you click Traceability when nothing is selected, the traceability window opens with the simulation or scenario.
• Better mouse actions performance when panning or moving and when cursor leaves editor window or crosses details window.

Review

Filters

Caliber Review uses the same filters created in Caliber Author. These filters are used in the Requirements Grid, in DocFactory, and now in Caliber Review.

Requirement Tree Display Items

Caliber Review now displays all the Visualize elements that Author displays, for example: Scenarios, Simulations, Scenario Steps, screens, logic, decision. These items appear in the tree similarly to how they appear in Caliber Author.

What's New

Author

Modern User Interface in Caliber Author

Caliber Author (formerly CaliberRM Client) has a new look and feel. This new navigation increases usability and brings Caliber in line with today's tools.

Introducing Delivery Status

Stakeholders can now view delivery progress directly from Caliber Author. Simply click the Delivery Status tabs to view progress of requirements and user stories from integrated applications such as Rally and Team Foundation System.

Caliber Visualize simulation snapshots display in Caliber

You now have the ability to view Caliber Visualize simulation snapshots from within the Caliber Author edit panel. Additionally, Caliber Author displays an edit link for the Caliber Visualize simulation screen. This allows you to log into Caliber Visualize and directly edit the simulation screen.

Visualize

Seamless Integration with Caliber Visualize

Caliber Visualize (formerly CaliberRDM) integrates seamlessly with Caliber Author. Now users can create requirements in Caliber Author, visualize scenarios and simulations in Caliber Visualize, and view requirements with their attached related visualizations in Caliber Author.

Visualize Server Load Leveling

Caliber can be configured to assign projects to specific Visualize Servers.  This enhancement provides the ability for Caliber administrators to manually level visualization work load across multiple Caliber Visualize servers, assuring high performance.

Simulation and scenario multiline labels

You can now create labels that span multiple lines. This new feature works with simulations and scenarios.

Generate CSV Files Directly with Notification

Users can request that the test cases CSV file generates a notification when it is finished. If a user requests to see a list of test cases, the list is limited to a user-selected maximum number.

Review

Introducing Caliber Review

A new component to the Caliber lineup, Caliber Review simplifies access and participation across teams. It allows teams to review and discuss requirements through all stages of development. Caliber Review does not require a license and is accessible on browsers.

System Requirements and Prerequisites

Caliber for Eclipse

Caliber for Microsoft Team Foundation Server

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

Caliber for Microsoft Visual Studio Team System

Caliber Web

Recommended Apache or IIS system requirements.

Top

Software Compatibility

Borland has tested integrations with the following Borland and third-party supported products.

Top

Installation and Upgrade Instructions

If you are upgrading from Caliber 2008 SP1 or Caliber 10.1, carefully review the Performing an Upgrade section of the Caliber installation guide, as the upgrade procedure has changed from previous releases. If you are installing via FTP, go to http://supportline.microfocus.com/productdoc.aspx to obtain the latest installation guide or download the media browser from the FTP site.

The following information contains notes regarding installation, but does not replace the entire process.

Components Included in 11.0.2

All upgrades require that Caliber 11.0 be installed prior to running the upgrade process. Note: Caliber Author and Caliber Data Server, you must have the 11.0 version and Hot Fix 1 installed on your machine before you can install 11.0.2.

The following Caliber components are included in 11.0.2.

• Caliber Author
• Caliber Data Server
• Caliber Visualize
• Caliber Review
• Caliber Web Client

Additionally, you must run the intaller as Administrator in Windows. To run as administrator:

• Change security setting to low UAC, if you don’t want run through the command line. Launch Caliber 11.0.2 Hot Fix.msp.
• Open DOS window as administrator and run: msiexec /p <file path>Caliber 11.0.2 Hot Fix.msp as a command, where <file path> is the directory where the .msp is located.
• Run as a silent install command line ( run as administrator): msiexec /p <file path>Caliber 11.0.2 Hot Fix.msp / qn as a command, where <file path> is the directory where the .msp is located.

If you are running as non Adminstrator during installation, the installation will complete, but the service will fail to start. You must manually start the SQM Monitor service before you can use Caliber Server.

Uninstall Caliber Author 11.0.2

To uninstall Caliber Author 11.0.2:

1. Open the Control Panel.
2. Click Programs and Features.
3. Click View Installed Updates. All installed updates appear in the programs list.
4. Select Caliber 11.0.2 Hot Fix from the list and click Uninstall.

Components Included in Hot Fix 1

The following Caliber components are included in Hot Fix 1. All upgrades require that Caliber 11.0 be installed prior to running the upgrade process.

• Caliber Author
• Caliber Data Server
• Caliber Eclipse Plugin
• Caliber Team Foundation Server Integration
• Caliber Visual Studio 2005 Integration
• Caliber Visual Studio 2008 Integration
• Caliber Visual Studio Visual Studio Team System 2008 Integration
• Caliber Visual Studio Team System 2010 Integration
• Caliber SDK
• Caliber Web Client
• Caliber Visualize
• Caliber Review

Install all components as you would any upgrade except for Caliber Eclipse plugin. Caliber Eclipse must be uninstalled, then install the Hot Fix.

Installing the Caliber Eclipse Plugin Installer

Before installing the plugin, remove the prior version of the Eclipse plugin:

1. Navigate to Control Panel> Settings> Add or Remove Programs.
2. Find an existing entry for Borland Caliber 11.0 for Eclipse.
3. Remove the plugin.

To install the new plugin:

1. From the Product updates page, navigate to the Borland Caliber 11.0 Hot Fix 1 for Eclipse folder.
2. Double click on setup.exe to install the plugin. The plugin installs in the Eclipse installation directory. For example, C:\eclipse if eclipse is installed on the C: drive.
3. Click Next, accepting the defaults until the Destination Folder dialog box appears.

Caliber Server

• See the Installation Guide for details.
• SDK Users: If your existing SDK application must connect to a server not yet upgraded to this release, do not recompile your application with the SDK included in this release. In general, when writing SDK applications, use the same version of the SDK as the version of the oldest server you need the application to connect to. You must recompile your .NET/COM SDK applications to make use of the new SDK functionality (create and assign security profiles, get/set user LDAP DN) provided in this release, and the recompiled application will be compatible with this release of the server.
• Previous version database backups must be restored in the previous version of Caliber, then migrated to Caliber 11.0.

Top

Installing or Uninstalling Caliber Visual Studio Integration on Windows 7

If installing or uninstalling Caliber Visual Studio Integration from Visual Studio 2005, Visual Studio 2008, and Team Foundation Systems 2008 on a Windows 7 machine, you must lower your UAC settings. If the settings are not lowered, during uninstall you will receive the RGDBSetKeyValueEX, Failed error message.

Caliber for Microsoft Visual Studio Team System

Your Visual Studio Team System administrator must install Caliber for Team Foundation Server once on the machine hosting Team Foundation Server, prior to installing the Caliber for Visual Studio Team System. The Caliber for Microsoft Visual Studio Team System component must be installed by each Visual Studio Team System end user (architect, developer, tester) to access Caliber requirements from within Visual Studio and establish traceability between requirements and Visual Studio Team System work items and tests from Visual Studio.

Top

Caliber SDK installation

• Before upgrading to the latest release of Caliber, you must upgrade any previously installed versions of the Caliber SDK to the equivalent Caliber release. To upgrade the Caliber SDK, perform the following steps:
  1. Remove the Caliber SDK registry key for the current SDK installation.
     • 2008 Caliber SDK: HKEY_CLASSES_ROOT\Installer\Products\15AE90BD6EBEFE146B5096C8E3CB7DFF
     • 2006 Caliber SDK: HKEY_CLASSES_ROOT\Installer\Products\30CB00006002D1F4880685EAC4401026
  2. Delete the Caliber SDK installation files, which appear in the following locations:
     • C:\Program Files\Borland\Caliber SDK 2008
     • C:\Program Files\Borland\Caliber SDK 2006
  3. Install the desired Caliber SDK release.
• When you are installing with an admin account, the Caliber SDK installation shows the error "The system administrator has set policies to prevent this installation" error both from the Caliber SDK installer and from the Caliber Server Install Caliber SDK option.
  
• When installing the Caliber SDK with the main installer (server and client), the Caliber SDK installer (.msi) is launched by the running the installer. This feature is called a nested installation or concurrent installation and has been deprecated.

Caliber SDK Stand Alone Uninstall

On Windows 7 machines:

1. Prior to uninstalling Caliber SDK, you must rename the 1150 folder located in C:\Program Files\Common Files\InstallShield\Driver\1150 as a backup measure.
2. Launch the SDK setup.exe from the installation media. Do not use Add/Remove in the Control Panel.
3. Select remove from InstallShield Maintenance Wizard to uninstall the SDK.

Visualize Upgrade and Default Ports

Note that the Visualize default ports are different from CaliberRDM default ports as follows:

• shutdown: 11001
• http: 11002
• ajp: 11003
• ssl: 11081               

Configuring Caliber Review

Changing Caliber Review Server

To connect to a different data server:

1. Stop the Caliber Review Server.
2. Edit webviewer.properties located in the <install directory>/lib.
3. Change the address and port number.
4. Save the changes.
5. Restart the Caliber Review Server.

Enabling SSL for Caliber Review

By default, SSL is disabled.

To enable SSL:

1. Stop the Caliber Review Server.
2. Edit server.xml located in <install directory>/conf.
3. Uncomment the following section:

<Connector port="11082" minSpareThreads="5" maxSpareThreads="75" protocol="org.apache.coyote.http11.Http11Protocol" enableLookups="true" disableUploadTimeout="true" acceptCount="100" maxThreads="200" scheme="https" secure="true" SSLEnabled="true" keystoreFile="bin/CaliberReview.keystore" keystorePass="Caliber11" clientAuth="false" sslProtocol="TLS"/>

4. Save the changes.
5. Restart the Caliber Review Server.

Top

Resolved Issues in Caliber 11.0.2 Release:

This patch (build number: 11.0.2.174 for Caliber Author and Data Server, 11.0.2.143 for Caliber Visualize, and 11.0.2.81 for Caliber Review) includes fixes for the following issues.

Resolved Issues in Caliber 11.0.1 Release:

This patch (build number: 11.0.1.155 for Caliber Author and Data Server, 11.0.1.113 for Caliber Visualize, and 11.0.1.67 for Caliber Review) includes fixes for the following issues.

Other Resolved Issues and Enhancements

The following resolved issues and enhancements are not related to an RPI, but have been implemented in this Hot Fix:

Author:

• Added new feature to paste unformatted text during edit
• Miscellaneous edit formatting updates
• Localized user interface updates for French, German and Japanese
• Enable support for Custom Tools integration in ribbon bar
• Enable the deletion of Visualize integrated projects from Administrator
• Corrected issue with Document View in the Caliber Eclipse plugin
• Corrected issue with adding new terms to glossary from Author editor

Visualize:

Fixed discussion defect regarding formatting parent discussions

Review:

• Added support for viewing different baselines
• Adjustments to UDA view formatting
• Enabled iPad / Android scrolling
• Performance improvements

Caliber Known Issues

Localized Documentation

The new features for Caliber 11.0 are not localized for this release. Our international (German, French and Japanese) customers are requested to refer to the English documents for the Caliber 11.0 release (http://supportline.microfocus.com/productdoc.aspx).

The Caliber SDK Programmers Guide is not included in the release media but is available for download from the Borland Documentation Web site mentioned above.

Option in Word influences Document Factory 1 and 2

When creating a .doc report Document Factory 1 and 2, an error occurs and the report does not open. If creating an xml report, the file opens but displays <<description>> in each requirement description.
Workaround: In Microsoft Word, choose Options > Advanced, and select Typing replaces selected text.

Other Known Issues

• Caliber 2008 SP1 components are not supported on the Caliber 11.0 Data Server.
• When upgrading, Caliber creates two backup copies of your existing database after restart, tripling the amount of disk space used. Your database is renamed and the default database is installed. You must restore your old database from the copy into the default database. After you restore,Borland recommends removing both backup databases.
• If the Caliber Server is installed on a VM image, rebooting the VM image may not start the "SQM Monitor" service properly.
  Workaround: Restart the service manually in the Services control panel or via "dbmgr -start" in the command line.
• In Caliber LDAP QuickStart Manager, new Caliber Data Server connections are not saved when the connection properties are created by a non-admin user. Also, new queries are not saved and no error message is displayed, when the query is created by a non-admin user

Note: If the user was an Admin user then the query would be saved, however there is no warning or error message to advise non-admin users that they don't have the correct permissions.

Note: The LDAPQuickStart.pdf guide states under the heading 'Having Appropriate Access Rights' that If you do not have the appropriate access rights on the Caliber Data Server and StarTeam Servers that you want to access, you cannot import users with LDAP QuickStart Manager. For Caliber Data Servers, the user must be a Framework Administrator. For StarTeam Servers, the user must have the server-level access right named Administer User Accounts. By default all members of the Administrators group have this and many other rights. Refer to the documentation for each product for a list of Administrator rights.

• The release software download shows “Unknown Publisher” instead of "is signed by Borland." Refer to http://support.microsoft.com/kb/922225/en-us#appliesto for more information.
• MPX users: When you upgrade your server, MPX events are disabled by default. If you used MPX events with your server and you are planning to continue using MPX events, you should select the Enable MPX Events (requires StarTeam Message Broker) option in the MPX Configuration dialog box. MPX is required for Caliber Visualize.
• Evaluation users only: If you re-install a trial version of Caliber Data Server on a Windows XP machine (not an officially supported platform), your installation may fail.
  Workaround: stop the SQM Monitor and SQM Database Windows Services before re-installing.
• During the upgrade the Caliber Server Settings in the Control Panel applet are lost. We recommend you save these settings prior to upgrade and restore them afterwards.
• When attempting to install the Caliber server from a remote location, "Error 1706: no valid source could be found".
  Workaround: run the installer locally from the server machine.

• Borland License Server users: The per-user license assignment (Named, Concurrent) needs to be manually restored after an upgrade.
• Borland License Server users: If your Caliber server is configured to use BLS licenses only, you must change the Admin user license type to BLS to be able to log on to the Caliber server using the Caliber Author as Admin. In this case, connections of the Admin user to the Caliber server using the Caliber Author are counted by the BLS server against the available licenses, and the type of the license acquired (named or concurrent) depends on the type of the particular BLS license assigned to the Admin user.

Top

Caliber Author

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 Caliber Author is launched for the first time, it tries to create dictionary files in “Program files” by default, and may fail if user does not have write access to Program Files.

Documentation

• On Windows XP SP2, selecting Help > Help Content may generate an error. Refer to http://support.microsoft.com/kb/843017/.

  Workaround:
  1. Open Internet Explorer.
  2. Select Tools >Internet Options.
  3. Select the Advanced tab.
  4. Scroll down to the Security options.
  5. Select the option to Allow active content to run in files on My Computer.

• The documentation lacks information about how to trace to files. To do so, select the Files tab in the Traceability Modification window, then browse to the file to trace to/from. Click the Trace From or Trace To button to create the trace, then click the Save Changes button.

Online documentation:

• The "Importing Requirements from Microsoft Word" topic states that you can import requirement names with delimiters or keywords. It should read as "You can only import requirement descriptions with delimiters and keywords."
• The Datamart topic launched from the Configuration wizard has an incorrect path for launching the Configurator. It should read as Borland Caliber > Administration > Datamart.

Caliber Author

• Caliber administrators must restart the machine after restoring a database as there may be a performance degradation if Caliber is used immediately after a database restore.
• Caliber Import utility crashes when it tries to import some German data. The problem is due to some special characters appearing in the export data. When exporting the data, the Export tool will have to convert the special characters in data into special form. This helps the Import tool to handle all them correctly. For more information, see 'Export of Special characters' under references in the online help.
• When exporting data using Export Utility, opening and editing export files in MS Excel will cause error when importing the modified file back to Caliber.
  Workaround: Use Notepad to open and edit the export files.
• In Caliber import utility, you cannot import requirements to the project without initializing the project.
  Workaround: Initialize the newly created project by opening it in Caliber Author and associating Requirement Type to it.
  
• There may be inconsistent behavior when inserting objects. JPEG objects are displayed by their filename while BMP files are shown as images. This is consistent with OLE behavior in MS Word.
• Traces added by a previous user are visible, even after logging out, to the next user.
• The trace filter for Requirement Grid doesn't work for remote traces (in the case of trace to SCTM artifact). When you select these filters, the Requirements with remote traces will not get displayed.
• On Japanese Vista operating system, some dialogs appear too big and some labels appear too small. This is due to the change in the default dialog font from MS UI Gothic to Meiryo font.
  Workaround: Change the Window Design from the Windows Vista Basic to the Windows Standard. The dialog size will be changed to the normal size.
• Importing an exported project into a new project gets many consecutive "Object does not exist" messages and the import is not successful. A second run of the import will then succeed.
• When you create users via the Caliber SDK, by default, the "User Can Manage Glossary Terms" permission is enabled for the user created. There is no SDK option to deselect this permission. However, if this permission needs to be disabled, you can disable it in the security tab of the Caliber Administrator.
• Caliber SDK doesn't support surrogate pair characters.
• If you do not have the corresponding OLE object software installed, the Edit object command does not open the OLE object software and shows no warning.
• Export to MS Access does not include StarTeam traces.
  Workaround: Use Datamart extractor to MS Access.
• HP Quality Center traces are not exported to MS Access from File > Export to Access. Workaround: login to Quality Center before initiating the export to Access.
• Traces to deleted requirements are displayed as "Retrieving ..." in the requirement Traceability tab.
• Traceability matrix rows and columns cannot display non-requirement objects without displaying some requirements.
  Workaround: use a "ID equals <requirement ID> "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.
• Creating some baselines may take longer than Caliber 2005 (due to versioning of traces).
• Traceability cannot be included when pasting requirements after a copy.
  Workaround: Use paste special.

Document Factory

• If the formatting in Microsoft Word 2007 is turned on, an additional small,bullet-like square may be visible at the beginning of any bulleted list items. This is a formatting mark and can be turned off. To turn off the formatting mark:

1. Open the Paragraph dialog box and click the Line and Page Breaks tab.
2. Uncheck Keep lines together option. The square no longer appears.

• If DocFactory2 templates are not well formed in Word, the resulting DocFactory2 report and its numbered headings will not be created properly. Read this article for a better understanding on creating numbered headings or outline numbering:

  http://www.shaunakelly.com/word/numbering/outlinenumbering.html

• DocFactory reports for Microsoft Word 2003 and above versions can be either in .XML or .DOC formats. For portability, size and general usage with images, you may use the .DOC extension. For extendibility with MS Office technology, performance, flexibility, scalability, custom post processing without using MS Word and when processing large amount of data and producing large result, it is recommended to use .XML.
• If you are generating document factory with requirement trace to SCTM linking service, the external trace does not appear in the document.
• When running old DocFactory (with MS office 2000), "Multiple" radio button has to be selected instead of "Once" for the keywords to be replaced properly for all the records.
• In new DocFactory, (for MS word 2003 Pro and 2007), invalid query error message appears during document generation when $filter command (containing old DocFactory syntax) is used in the template:
  Workaround: Create and save a new filter on the server, and modify the $filter tag with new filter criteria.
• New DocFactory (for MS word version 2003 Pro and 2007), does not support filtering in SQL format.
  Workaround: Create and save a new filter on the server, and modify the $filter tag with new filter criteria.
• The Document Factory option in the requirement grid is not available when the grid displays a single requirement.
  Workaround: Display grid with multiple requirements and manually select the requirement.
• Specifying the current baseline is done with $BASELINE{Current Baseline} instead of $BASELINE{Current}.

Borland Search

• Tools > Borland Search does not open a Web browser if a browser is not already open.
  Workaround: open a browser before invoking this menu option.

Estimate Professional

• Closing the project browser with the close button generates an error.
  Workaround: select the menu option to close the project browser.
• The EstimatePro online help (Import Project Data topic) erroneously claim MS Project 97 support.

StarTeam integration

• When a new Requirement Trace is made, StarTeam integration gets disconnected and the Requirement Trace properties are not displayed.
  WorkAround: You must 'Refresh' after making Requirement Traces in order to display the New Requirement Trace Properties.
• When opening several views in different tabs on the StarTeam tab in the Traceability Modification window, you may see java.lang.Out.Of.Memory...error messages.
  Workaround: add an options=-Xmx256m or options=-Xmx512m line to the StarTeamSDK10.ini file which is located in C:\Program Files\Borland\StarTeamSDK10.1\Lib by default.
• 'Out of Memory' error may be displayed when attempting to view the StarTeam trace history.

HP Quality Center integration

• Caliber 10.1 has default value for configuration file after upgrade in HP QC.
• If you use a non-English Caliber Author with an English version of Quality Center, characters other than English will not display correctly in Quality Center.
  Workaround: install a corresponding Mercury Quality Center language pack.
• Custom fields created in Mercury Quality Center are displayed in the Publisher to Quality Center wizard, even though these custom fields are not modified when publishing requirements.

SilkCentral Test Manager integration

• When restore and taking backups, the integration (enabled or disabled) is remembered. However, when enabled, the URL is not remembered. User has to supply the URL again for SCTM just like in Mercury Quality Center to make it work.

• Caliber 10.1 will not support SCTM 8.6 for synchronization.
• On the Traceability tab, the project/ID field 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 tab displays an error.
  Workaround: connect to SilkCentral first.

SCM integration

• A trace to a file in Rational ClearCase does not show in the Traceability tab.
  Workaround: refresh the Traceability tab after creating the trace.

Top

Caliber for Eclipse

• The requirement grid is slow when viewing large number of requirements.
  Workaround: use the document view instead.
• The Compare Baselines report is difficult to read using the default width.
  Workaround: use the Windows client to compare baselines.
• Option to trace to Borland StarTeam, Borland Together, Borland Silk or Mercury Quality Center do not allow users to create traces.
  Workaround: contact support to install the necessary addins.
• When MPX is enabled and the requirement tree is refreshed by MPX events, the current cursor position is lost.
  Workaround: turn off MPX events in the login dialog box.
• Navigating to non-requirement software artifacts (such as Borland StarTeam elements) from a requirement may generate an error.
  Workaround: use the Windows client to view these traces.
• After a refresh, the requirement navigator shows requirements as locked even though the requirements are not locked and can be edited.
• In both Eclipse 3.2 and Eclipse 3.3, when you view the traceability tab of a requirement that has SCTM trace attached to it in SCTM, the SCTM trace is not displayed. However, when you view the same requirement in Caliber, the SCTM trace will be displayed.

Top

Caliber for Microsoft Visual Studio 2008/ Visual Studio Team Foundation 2008

• In Caliber explorer, after adding a project, the pull-down menu for the project displays Log in to Caliber Project instead of Logout Caliber Project.
  Workaround: Select Log in to Caliber project after adding a project.
• After removing a project, if you use toolbar button to add a project, the Logon/Add project dialog is not closed even after the operation succeeds. You must click the Cancel button, to close the dialog and to display the project. This does not occur if you click on <<Click Here to Add a New Caliber Projects>> to add a project.
• Using the Caliber Explorer, you are unable to add multiple projects from the same Caliber Server.
  WorkAround: Log off before logging in again to the same Caliber Server.
• When you select a trace on the Traceability Modification dialog and select the 'trace to' or 'trace from' button in the toolbar (in the same direction) and save, it does not remove the trace as in the Caliber Author.
  Workaround: Manually remove the trace using the Traceability tab.
• When you disable "Always on top" option in the Traceability Modification dialog, you are unable to interact with its parent Visual Studio. Close the Traceability Modification dialog before continuing work with the VSTS integration. This happens only in VSTS integration and not in VS integration.
• In Visual Studio 2008 integration, when you click the 'Refresh' button of Caliber Explorer Toolbar, empty message dialog is shown and 'Refresh' command doesn't work.
  Workaround: To close the empty dialog box, click the 'left' button on the dialog box. To refresh your Caliber project, click 'Refresh' button after any requirements are opened or restart the Visual Studio.
• In VSTS 2008 integration, changing the direction of two traces and saving them from the Traceability Modification dialog box results in displaying only one trace in the Traceability tab and infinite hour glass prompt.
  Workaround: Closing the requirement and re-opening it again will show the correct display.
• In Visual Studio 2008 integration, Visual Studio hangs up when removing Caliber project. When multiple baselines for same Caliber project are added to Caliber Explorer, Visual Studio sometimes hangs up when you remove a project. This issue occurs only when requirements are opened in Editor pane.
  Workaround: Close all requirements before removing project.
• The following features of VS/VSTS2008 integration doesn't work correctly on Vista:
  • Requirement Grid: In the Print Preview, there is nothing to preview.
  • Add multiple projects to Caliber Explorer (VS2008 will crash).
  • Store Caliber connection information (users have to add Caliber project every time).
  • Images in Description are always missing.
  • VSTS Tests tab in Traceability Modification (There is an Error while opening the test list)
  This error occurs because VS/VSTS integration needs administrative privileges to use these features.
  Workaround: When you run Visual Studio, select "Run As Administrator" from the context menu.
• Need to copy the Visibroker.Net files into the corresponding directory of the actual Visual Studio installation.
  If the user has installed the Visual Studio into another drive, then VSTS integration cannot connect to the Caliber Server even though The VSTS Integration installer is hard coded to install the Visibroker.Net dll files into C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies.
  Workaround If VS is installed to a drive other than C, then copy the Visibroker.NET files into the corresponding directory of the actual Visual Studio installation after the integration.
• In French version, VSTS 2008 crashes when trying to add TFS server using 'Traceability modification'>'VSTS Test tab'
  For English and Japanese version, VSTS hangs when trying to add TFS server using 'Traceability modification'>'VSTS Test tab'
• In Visual Studio Team foundation 2008 and 2005, while uninstalling Caliber for Team Foundation Server (TFS Integration), uninstaller fails to unregister Caliber entry.
  Workaround:Remove the Caliber entries manually from the Microsoft Visual Studio Team Foundation Server. The procedure is given below.
  • To remove the Caliber entries manually from the Microsoft Visual Studio Team Foundation Server 2005 (TFS2005):
    1. Run the TFSReg command with /D switch before running uninstallation.
       (You can find TFSReg command under \Tools folder).
       TFSReg /D \Registration.xml TfsIntegration

       For example: TFSReg /D "C:\Program Files\Borland\Caliber For Team Foundation Server\Registration.xml" (local) TfsIntegration

       Note: If you have uninstalled TFS Integration, but you can't find the Registration.xml file, please contact to Borland Support or reinstall TFS Integration.

    2. Uninstall TFS Integration.
  • To remove the Caliber entries manually from Microsoft Visual Studio Team Foundation Server 2008 (TFS2008):
    1. Run the TFSReg command with /EXPORT switch (You can find TFSReg command under \Tools folder). TFSReg /EXPORT TfsIntegration

       For example: TFSReg /EXPORT c:\temp\Registration.xml (local) TfsIntegration

    2. Open the exported file.
    3. Search "Caliber" Type element.
    4. Remove the element including "Caliber" Type element and save the file.
    5. Run TFSReg command with /OVERWRITE switch. TFSReg /OVERWRITE TfsIntegration

       For example: TFSReg /OVERWRITE c:\temp\Registration.xml (local) TfsIntegration

  Top

  Caliber for Microsoft Visual Studio 2005

  • In Caliber explorer, after adding a project, the pull-down menu for the project displays Log in to Caliber Project instead of Logout Caliber Project.
    Workaround: Select Log in to Caliber project after adding a project.
  • After removing a project, if you use toolbar button to add a project, the Logon/Add project dialog is not closed even after the operation succeeds. You must click the Cancel button, to close the dialog and to display the project. This does not occur if you click on <<Click Here to Add a New Caliber Projects>> to add a project.
  • In VSTS 2008 and 2005 integration, changing the direction of two traces and saving them from the Traceability Modification dialog box results in displaying only one trace in the Traceability tab and infinite hour glass prompt.

    Workaround: Closing the requirement and re-opening it again will show the correct display.

  • Option to trace to Borland StarTeam, Borland Together, Borland Silk or HP Quality Center does not allow users to create traces.
    Workaround: contact support to install the necessary addins.
  • The integration cannot connect to Caliber servers with enabled SSL.

    Workaround:

    1. Open the folder where the VSTS client is installed, for example: C:\Program Files\Borland\Caliber Client For Visual Studio Team System
    2. Right-click on Caliber SSL.crt.
    3. Select "Install Certificate."
    4. Select Next
    5. Select Next
    6. Select Finish

  • Traceability to external software artifacts is not available.
  • In Visual Studio 2005 integration, when you click the 'Refresh' button of Caliber Explorer Toolbar, empty message dialog is shown and 'Refresh' command doesn't work.

    Workaround: To close the empty dialog box, click the 'left' button on the dialog box. To refresh your Caliber project, click 'Refresh' button after any requirements are opened or restart the Visual Studio.

  • In Visual Studio 2005 integration, Visual Studio hangs up when removing Caliber project. When multiple baselines for same Caliber project are added to Caliber Explorer, Visual Studio sometimes hangs up when you remove a project. This issue occurs only when requirements are opened in Editor pane.

    Workaround: Close all requirements before removing project.

  Top

  Caliber for Microsoft Visual Studio Team System

  • When you view the traceability tab of a requirement that has Visual Studio trace attached to it from Visual Studio, the Visual Studio trace will not be displayed. However, when you view the traceability tab of the same requirement in Caliber, the trace is visible.
  • After uninstalling Caliber for Microsoft Visual Studio, Borland Caliber is still displayed amongst installed products on Visual studio splash screen.
  • The Owner field of some requirements is not displayed on the Details tab.
  • The integration cannot connect to Caliber servers with enabled SSL.

    Workaround:

    1. Open the folder where the VSTS client is installed, for example: C:\Program Files\Borland\Caliber Client For Visual Studio Team System
    2. Right-click on Caliber SSL.crt.
    3. Select "Install Certificate."
    4. Select Next
    5. Select Next
    6. Select 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 may occur. Click OK. The trace is created correctly.

  Top

  Caliber for Web

  • The Caliber 10.1 Web Viewer is unable to connect to the Caliber 11.0 Data Server. You must use the Caliber 11.0 Web Viewer in order to connect to the data server.
  • When a new Requirement Trace is made, StarTeam integration gets disconnected and the Requirement Trace properties are not displayed.
    WorkAround: You must 'Refresh' after making Requirement Traces in order to display the New Requirement Trace Properties.
  • During the installation of the Caliber Web components, having a blank space in the installation directory causes the Apache Server not to run. Even Manual run made to the service won't start the Apache Server.
  • When viewing discussions, selecting/clicking the white space of a subject causes the tree list display to show weird displays.
    Workaround: Click on the subject's text itself or the nodes/icons of the subject.
  • Web client 10.1 does not display existing traces to SCTM 2007 artifacts. If a trace is created to a SCTM 2007 artifact using the Caliber Author, this trace would not be visible under the Web client. The web client is only able to display traces to SCTM 2008 artifacts.
  • Upgrading Caliber Web keeps the previous version installed.
  • On Windows XP SP2 and Windows 2003, selecting Help > Help Content may generate an error. Refer to http://support.microsoft.com/kb/843017/

    Workaround:
    1. Open Internet Explorer.
    2. Select Tools >Internet Options.
    3. Select the Advanced tab.
    4. Scroll down to the Security options.
    5. Select the option to Allow active content to run in files on My Computer.

  • Non-alphanumeric characters in requirement descriptions may not display.
  • .WMF file inserted in requirement descriptions may not display correctly.
  • The hyperlinks in requirement descriptions are displayed, but are not active.
  • The Description field of a trace to a Mercury Quality Center object displays unreadable HTML code if the original Quality Center 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.
    Workaround: 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 requirement grid filter functionality works only in the windows client. The Web client uses the former requirement grid filter functionality for filtering.

  Top

  Caliber Visualize Known Issues

  • Caliber allows administrators to define permissions to limit access and actions. The message “You are not authorized to modify traces for this visualization object" indicates that the logged in user does not have permissions defined to allow the trace modification action. A Caliber Administrator can grant this permission.

  To grant this access in the Caliber Administrator tool:

  1. In the Caliber Administration tool, click File>Admin>Security Profiles to open the Security Profiles Editor.
  2. Select the appropriate profile and click Edit.
  3. In the Modify section for both Scenarios and Simulations Requirement Types, change Requirement Trace from Owned to Any.
  4. Click OK.
  • When using Caliber Visualize on Internet Explorer 7 or later on Windows Vista or later, you may continuously receive an error message stating, "unable to connect to the Caliber Visualize server. Please refresh your browser window." Windows Vista and later with Internet Explorer or later runs in Protected Mode. In order to use Caliber Visualize, you must turn off Protected Mode. Protected Mode can be configured in Internet Explorer's Internet Options dialog. To configure Protected Mode, click the Security tab, select a Web content zone, and then change the Enable Protected Mode check box. By default, Protected Mode is enabled for the Internet, Intranet, and Restricted Sites zones. To verify that Internet Explorer is running in Protected mode, look for the words "Protected Mode: On" next to the Web content zone displayed in Internet Explorer's status bar.
  • When synchronizing requirements from SilkCentral Test Manager, an error occurs indicating a project import failure. This problem is due to a missing Change History database table required by the integration. To work around this issue, you must create a project in Caliber Visualize before initiating the synchronization. When creating a project in Caliber Visualize, the required Change History database table is also created.
  • After installing a full access license, you must restart the Caliber Visualize server. From the Control Panel, navigate to Administrative Tools > Component Services, and then restart the Caliber Visualize Server service.
  • When attempting to create a report when a report of the same name is already opened, an Internet Explorer error message appears.
    Workaroud: you must close the first instance of the report and recreate the report.
  • A confirmation message indicating the successful import of a project or upload of a file may not appear when running Caliber Visualize on a Firefox browser. This issue does not result in the failure of the project import. To work around this issue, you must close the browser, and then restart the browser to verify the project or file uploaded properly.
  • When you assign an owner to a requirement, it is possible to select a user name that is not assigned to a project in Caliber. If a user selects an owner name that is not a member of the project, the following error message appears: The selected owner is not a member of this project.
    Workaroud: assign the owner to the project from Caliber or select a different owner from the list.
  • In some cases, only the user who created a project can edit the project. Other users cannot edit the project.
    
  Top
  

• Limitations

• Caliber Data Server

  • Database administrative tasks cannot be performed by users other than the specific user who created the database.
    Workaround: when creating the database, use a generic user ID (like "crmdb") not tied to a specific user.
  • The following Caliber 10.1 administration tools only work with the 10.1 server: Caliber Administrator, Datamart, RM Import, RM Export, LDAP Quick Start Manager.

  Top

  Documentation

  • The Caliber documentation is not localized for this release. Documentation is only available in English.
  • For more information about the Caliber Visualize, refer to the Caliber Visualize help.

  Top

  Caliber Author

  • HP Quality Center Version 10.0 is supported for non-versioning projects. NOTE: We do not yet support MQC 10.0 for Versioning Enabled Projects using Caliber Mercury Publisher and Caliber Test Wizard tools.
  • The $Filter command in a template is ignored when the new DocFactory is launched from Caliber Author.
    The $filter command is ignored when the new document factory is launched from Requirement Grid when no requirement is highlighted and when 'No' button is used, and also, when 'Yes' button is used and when requirements are selected. The filter on the template is ignored as well. Instead, it prints the highlighted requirements.
  • While extracting using Datamart to SQL Server 2000, the extraction fails if the data goes beyond row size of 8060 bytes. This is due to SQL Server 2000 limitations.
    However, if the row sizes are below 8060 bytes, Datamart extraction will be successful for SQL Server 2000.
  • When you synchronize requirements from SCTM, images added in description of requirement in SCTM are not displayed in Caliber Author, Visualize, and Review after synchronization. Only the URL of the image gets displayed in the description pane. To view the image, you must paste the image URL in the web browser.
  • Import from Word may not import tables correctly.
  • To install Caliber, users must have write access to the /Program Files/Borland/Caliber directory.
  • Export to MS Access: Information exported from the requirement grid into Excel will be truncated at 255 characters per column.
  • Large requirement descriptions may not display in the grid.
  • Pasting text from MS Word to requirement descriptions may result in lost format.
    Workaround: save the document as "Web Page, Filtered" first, then copy and paste the text in Caliber.
  • The traceability diagram is not available from baselines.
  • Information about Rational ClearCase files traced to requirements cannot be seen in the traceability diagram.
  • Matrix and Grid Filters are private to users, cannot be shared with other users.
  • Grid and matrix filters are saved on server, instead of “.rgv” file on user’s computer. Clicking the save button will only save the column layout in “.rgv” file.
  • Old Document Factory (default for MS Word 2000 and below) cannot use Grid and Matrix filters (saved on server). If users have any filters (.rgv files) from Caliber 2006, they can still be used in old Document Factory. Also, string based filtering mechanism can be used with old Document Factory.
  • Caliber 2006 filters saved as .rgv files cannot be used in new Document Factory (default for MS word 2003 Pro and above).

  Top

  Caliber for Eclipse

  • Displaying a traceability matrix for a large set of requirements may take a while.
  • Viewing traces may generate errors.
    Workaround: view traceability in the Windows client.
  • You must use the default MPX port in the Caliber Server (control panel) for requirements to be automatically updated.
  • Traceability information should be viewed with the Current baseline opened.

  Top

  Caliber for Microsoft Visual Studio 2005

  • Document references set as key references are not displayed.
    Workaround: store requirement descriptions in Caliber.
  • Creating traces to Borland StarTeam, Borland Together, Borland Silk or Mercury Quality Center is not available.
  • Traceability information should be viewed with the Current baseline opened.

  Top

  Caliber for Microsoft Visual Studio Team System

  • Work items created in Caliber are not visible in Team Explorer until the user refreshes Team Explorer.
  • Users must have a non-empty Caliber authentication password.
  • Creating traces to Borland StarTeam, Borland Together, Borland Silk or Mercury Quality Center is not available.
  • Traceability information should be viewed with the Current baseline opened.

  Top

  Caliber for Web

  • Long requirement descriptions may take a while to display.
  • Traceability views may show errors.
    Workaround: view traceability in the Windows client.
  • Traceability information should be viewed with the Current baseline opened.

  Top

  Getting Help

  For technical support, contact the Borland Support Center at http://support.borland.com/.Before contacting support, you may want to consult the Borland Support Center Borland Answers at http://support.borland.com/kb.php

  Top

  Copyright © 2013 Micro Focus. All rights reserved. Portions Copyright (c) 1998-2009 Borland Software Corporation (a Micro Focus company). All other marks are the property of their respective owners.