Rational RequisitePro Release Notes
Version 2001.03.00

Getting Started

Compatibility Issues

New and Changed Features

Guidelines and Restrictions on Using RequisitePro

Known Issues

Upgrading the RequisitePro and ClearQuest Integration

Contacting Technical Support

This document provides information about the 2001.03.00 release of Rational RequisitePro. The release number is listed in the About RequisitePro dialog box (Help > About RequisitePro).

For information regarding RequisiteWeb, including system requirements and known issues, refer to the Rational RequisiteWeb Installation and Configuration document (ReqWebSetup.html).

Before installing RequisitePro, be sure to read the following sections: Hardware/Software Information and Getting Started.

Refer to the following information for system and software requirements. This section provides basic information on the platforms supported and the hardware and software requirements for running RequisitePro. Refer to Compatibility Issues for more information.

Operating Systems:

• Microsoft Windows 2000 Professional Service Pack 1, or
• Microsoft Windows 98 Second Edition, or
• Microsoft Windows NT 4.0 Workstation Service Pack 6a, or
• Microsoft Windows Millennium Edition, or
• Microsoft Windows 95 OEM Service Release 2.

Recommendations for Microsoft Office:

• With Windows 95 and Windows NT 4.0 Workstation, use Office 97 Service Release 2 or Office 2000.
• With Windows 98 Second Edition, Windows Millennium Edition, and Windows 2000 Professional Service Pack 1, use Office 2000.

Processor:

• 200 MHz or greater;
• 300 MHz or higher is recommended.

Memory:

• 64 MB or greater;
• 128 MB is recommended.

Note: For using UCM to baseline RequisitePro projects, 256 MB is recommended for RequisitePro project administrators.

Disk Space: 100 MB.

Monitor:

• 800 X 600 X 256-color video resolution, or greater;
• High Color or True Color recommended.

Mouse/pointing device: Microsoft Mouse or compatible pointing device.

Word Processor:

• Microsoft Word 97 Service Release 2, or
• Microsoft Word 2000 Service Release 1.

Note: See recommendations for Microsoft Office above.

XML Parser: Microsoft Internet Explorer 4.0 Service Pack 1 or later.

Requirement Metrics Reporting:

• Microsoft Excel 97 Service Release 2, or
• Microsoft Excel 2000 Service Release 1.

LAN Support: Microsoft networks. (Novell networks are not supported.)

Automated License Key Requests: Internet connection required for automated license requests.

Oracle Client: Versions 7.3.4, 8.0.5, 8.1.5, 8.1.6.

• Microsoft SQL Server: versions 7.0 or 2000.
• Oracle Server: versions 7.3.4, 8.1.5, 8.1.6. (In Oracle version 8.0.5, the ability to create a table based on a query that uses an "Order By" clause was not available. RequisitePro requires this clause.)

Note: If you are using a version 7.3.4 server, we recommend that you use a version 7.3.4 client.
• Memory: 128 MB minimum. For projects with approximately 50,000 requirements, 256 MB is recommended.

Note: Memory requirements will vary depending on the number of concurrent users, the amount of data being requested, and the size of the database.
RequisitePro does not require the installation of the Oracle Java Runtime components. Installing these takes approximately 50 MB of RAM.
• Disk Space: 96 MB.

For more information on using Oracle or SQL Server, refer to Compatibility Issues.

For full installation instructions, refer to the manual Installing Rational RequisitePro (also available in an electronic version on the Rational Solutions for Windows Online Documentation CD).

All users must use the same release of RequisitePro in order to access shared projects. We recommend all users uninstall previous versions of RequisitePro before installing this version.

Minimal Installation

The Minimal Install functionality of Rational products is not supported in this release. You must choose the Typical or Custom/Full options to install your Rational product(s). The references to the minimal install option in Rational installation manuals are no longer applicable.

If you open an Oracle-based or SQL Server-based project that has been upgraded to RequisitePro version 2001.03.00 from version 2000.02.10 or a prior release, an error message indicating an Access database was not found appears. The project is still based in Oracle or SQL Server, but you should upgrade RequisitePro on your system to version 2001.03.00. (15459)

If you previously used the Rational Synchronizer with RequisitePro, you will need to manually change the "SynchLinks" attribute to "SynchronizerSynchLinks" for each requirement attribute in order for previously generated links to be recognized. (15637) (RATL00037926)

For detailed steps on upgrading RequisitePro projects for use with the ClearQuest integration, refer to Upgrading the RequisitePro and ClearQuest Integration .

If you are upgrading from RequisitePro 4.5 and have not uninstalled 4.5 and removed the RequisitePro 4.5 installation folders, you should remove the reqpro.gid and letsgo.gid files from the \Rational\RequisitePro 4.5\help directory if they are still present. (11427)

Microsoft Access 2000 is the default database format for RequisitePro version 2000.02.10 and version 2001.03.00. If you have a project that was created in a earlier release of RequisitePro, the project database is in Microsoft Access 97 format. If you want to view a RequisitePro project from a previous release in Microsoft Access 2000, you will need to upgrade the project database to Microsoft Access 2000.

Rational has provided a utility to convert Microsoft Access-based RequisitePro projects from Access 97 format to Access 2000 format. The utility "RqAcc2KConv.exe" (located in the RequisitePro/bin/ directory) can be invoked by either dragging and dropping the RequisitePro project file (.rqs) onto the executable, or running the utility from the command line and specifying the entire path to the RequisitePro project file (.rqs) file. As part of the conversion process, the utility will create a backup copy of your database with the .tac extension instead of the .mdb extension. The backup copy can be removed once you are satisfied that the conversion was successful. The utility will also repair and compact the database.

RequisitePro setup creates a Start menu program group for RequisitePro with the following items: Let's Go RequisitePro, Online Help, Rational License Key Administrator, Rational RequisitePro, Rational Software Installed Product Information, Release Notes, Technical Support, and Rational Administrator. To start RequisitePro, select the Rational RequisitePro menu item.

Let's Go RequisitePro when RequisitePro is first launched. Use the Let's Go RequisitePro online help to access getting started online help as well as these release notes, project administration tips, white papers, the Rational Unified Process, and Web resources. Let's Go RequisitePro can also be launched from the RequisitePro Help menu.

In addition to online help, refer to the manual Using Rational RequisitePro (also available in an electronic version on the Rational Solutions for Windows Online Documentation CD).

RequisitePro is compatible with:

• Rational ClearCase and ClearCase LT, version 2001.03.00
• Rational TestManager, version 2001.03.00
• Rational Rose, version 2001.03.00
• Rational SoDA for Word, version 2001.03.00
• Rational ClearQuest, version 2001.03.00
• Rational Unified Process, version 2001.03.00
• Microsoft Project 98 and 2000

Note: Oracle and SQL Server versions are listed in the Hardware/Software requirements.

If you experience problems running RequisitePro on Micron systems, contact Rational Technical Support for a technical note relating to the issue. For additional information contact Micron PC Technical Support at: http://support.micronpc.com/contact/support/.

• By default, when Oracle databases are created on UNIX systems, the Oracle character set installed is incompatible with Microsoft Word's extended characters. This incompatibility prevents proper storage of special characters in RequisitePro requirement text and causes requirements to be marked as "modified" in documents. The required character set is WE8ISO8859P1. For more information, contact Rational Technical Support.
• If you are having difficulty installing the 8.1.5 client, uninstall and install a previous version of the client (such as 8.0.5 or 7.3.4), then reinstall the 8.1.5 client. Refer to Microsoft Knowledge Base article Q239719. (6050)

• When configuring SQL Server, do not mark the check box "Change the language of SQL Server system messages to..." The use of this check box prevents users from opening the RequisitePro project after its initial creation. (10411)
• If you have SQL Server 2000 installed and are running the Database Upgrade Wizard, you may receive an error informing you that you lack permissions to perform an action. This occurs because SQL Server 2000 allows only server administrators to drop and add system messages (specifically to execute the sp_dropmessage and sp_addmessage stored procedures). To complete the upgrade, your DBA will need to assign the RequisitePro user (e.g. reqpro) to the ServerAdmin role. Once the DBA has completed this task, run the Database Upgrade Wizard again and you should not receive the error. Remove the user from the ServerAdmin role once the upgrade has been completed. (14296)

• The graphical heading banners and icons in Let's Go RequisitePro may be distorted when displayed on PCs with the 256 Colors display setting. For clearer graphics, set your display properties to High Color (16 bit) or the True Color (24 or 32 bit) settings. (11573)
• For best results when opening PDF files from Let's Go, make sure you are using Acrobat Reader version 4.0. This version of Acrobat Reader is shipped with RequisitePro. (11837)

You must use the SMTP mail protocol when configuring the Rational E-Mail Reader for RequisitePro discussions. MAPI is not supported. (14370)

RequisitePro now allows administrators to create baselines of their RequisitePro project using ClearCase UCM. You can create a baseline for the project and create new RequisitePro projects from existing baselines. This feature is supported for RequisitePro projects that are stored in Microsoft Access, SQL Server and Oracle databases.

Requirement names provide the ability to assign a short descriptive name to any requirement. In views and other places where a requirement's tag is used as its identifier, RequisitePro can display the name as well. This allows all RequisitePro users to refer to requirements more naturally in conversations and more easily locate them in the views.

It is now faster and easier to create new RequisitePro projects using project templates. A project template can be created from any existing RequisitePro project. You have the option to include the project data in the template. New projects can be quickly created based on templates. RequisitePro ships with three predefined templates to help you get up and running faster.

The new URL Link attribute type allows RequisitePro users to store a URL and navigate to a site from an Attribute Matrix or a Requirement Properties dialog box.

RequisitePro has been enhanced for teams that work across time zones. RequisitePro documents now use GMT time stamps to eliminate inconsistencies.

RequisitePro is supported on the following international operating systems: French, German, Japanese, Italian, Swedish, Simplified Chinese, Traditional Chinese, Dutch, Hebrew, and Korean.

Users are able to enter text and data using their native language and corresponding character set on the following operating systems: French, German, Japanese, Italian, Swedish and Simplified Chinese. Regional date, time, and number conventions, as specified by the user's selection of regional settings on the Windows control panel, are also supported for both input and output.

Users with Hebrew, Korean, Traditional Chinese and Dutch operating systems must enter all input data (such as path names) using U.S. English.

For all international systems listed above, screens, menus, controls, wizards, reports and user documentation are in U.S. English.

Note that internationalization assumes homogeneous language environments; for example, a French operating system using French versions of SQL Server and Microsoft Word.

Microsoft Word Issues

Avoid creating requirements inside text boxes. RequisitePro cannot access them properly.

Avoid creating requirements that span more than one cell in a table.

RequisitePro doesn't support Word customized macros. (10108)

When saving RequisitePro documents, Microsoft Word records the revision number for all revisions as "2." This revision number is available on the Statistics tab of the document Properties dialog box, which is accessed from the File menu using the Properties command. This revision number does not affect the document revision information in RequisitePro, which is available on the Revision tab of the Document dialog box. This dialog box is accessed from the RequisitePro Document menu using the Properties command. (1826) (1109)

If you are importing a Word document that uses a template other than Word's normal.dot template or an existing RequisitePro outline, you should set up that template as a RequisitePro outline prior to importing the document. RequisitePro will overwrite any unrecognized formatting, such as Word styles, with the normal.dot formatting.

If you have customized the formatting within the Word document, you should save the document as a Word template and copy it to the RequisitePro outlines directory. Refer to the Microsoft Word documentation for help in creating Word templates. Refer to the RequisitePro online help topic "Creating outlines" for help in managing RequisitePro outlines.

RequisitePro will not create a requirement if the block of text and/or images highlighted contain hidden text at the beginning or end of the selection. This occurs because RequisitePro uses hidden text at the beginning of a requirement to assign a requirement tag number and at the end of a requirement to store formatting information about the requirement.

Do not type information within the hidden part of a requirement, as the information is formatted as hidden. If the requirement is deleted, the information you typed is deleted as well.

• After saving RequisitePro documents, a maximized Word window changes to the previous size. To avoid his change in the Word window size, use the cursor and drag the Word window to the appropriate size instead of using the Maximize button. (15647)
• RequisitePro contains a Refresh Requirements command on the Document menu that allows you to reset the style and color of all requirement text in a document in case you inadvertently change it. However, if you change the color of any requirement text using Word 2000, the color cannot be reset using the Refresh Requirements command. To refresh requirement text color, close the requirements document and reopen it, and then select the Refresh Requirements command. (5359)
• If you are using Word 2000 and choose to clear the Trust all installed add-ins and templates check box on the Tools > Macro > Security dialog box, you must click Enable at the Microsoft Word message box each time you open the RequisitePro Word Workplace. (11361)

If you include the following in the text of a requirement located in a document, you will not be able to edit the requirement text outside the document (even when the extended editing feature is enabled):

• OLE objects (both embedded and linked)
• Fields (e.g., author, title, subject)
• Pictures (both inline and floating)
• Tables
• Annotations (comments, footnotes, bookmarks, hyperlinks)
• Subdocuments
• Lists containing more than a single item (including bulleted and numbered headings or other styles, both sequential and outline)

• If you experience problems with the RequisitePro menus when using offline documents, clean all temp files and delete normal.dot.
• In Word 2000, you may need to adjust your macro security levels to use the Requirements > Create and Delete menu commands in offline authoring. Word 2000 defaults to the highest level for macro security. This setting prevents the enabling of the RequisitePro offline authoring macros. Reset the macro security in Word 2000 to medium on the Security dialog box, which is available by clicking Tools > Macro > Security.

ClearCase UCM/Baseline Issues

The time required for checking in a project is proportional to the number of requirement types, documents, and saved views in the project. For example, checking in 200 elements can take 45 minutes; 400 elements may take 75 minutes. The impact of many saved views and extremely large documents is particularly significant. (14374)

Project Templates

If you do not have write access to the local machine directory of the registry, you cannot see the RequisitePro project templates in the Create RequisitePro Project dialog box. You can copy the templates from the RequisitePro\templates\ directory into any directory and then specify that directory in the Project Template field in the Tools > Options dialog box. (15746)

RequisitePro does not support a digit-grouping symbol of any kind (i.e., a thousand separator, such as the comma in 2,350). You cannot enter attributes with this symbol. RequisitePro does not display numbers with this symbol. (6858)

• If you are using an Access database and you have slow performance with the Retain Hierarchy option in the views display or queries, upgrade the RequisitePro project to use Oracle or SQL Server. (15569)
• If a saved view includes a query with a user-defined date field parameter, the date is stored with the saved view in the date format that is set in your Control Panel/Regional Settings/Short Date Style. If you attempt to open a saved view on a PC that uses a different date format (such as dd/mm/yyyy), a run-time error occurs. The same error occurs if the saved view is part of a project that you are using as a template for creating a new project on a PC that uses another date format. (8328)
• In RequisitePro projects that use a Microsoft Access database, you may experience a 5-to-10-second delay between entry of data and display of the modified data. This is due to defects in Microsoft MDAC components, which RequisitePro uses in querying data in Access databases. For example, if you create or modify a requirement, and then run a query for all requirements of that type, the new or modified requirement may not be displayed until after a delay. (2189)

• The Parent Change filter cannot always detect when a requirement is changed from a root requirement to a child requirement, and vice versa. (8472)
• Close Requirement Metrics before you close the RequisitePro project. (7302)
• If your Requirement Metrics report has multiple queries and contains a traceability change query, the results of other queries may not be correct (11894)

The following is a list of known issues that are expected to be fixed in a future release of RequisitePro.

The color and style set through the RequisitePro Extensibility Interface are off by one index number. To set the color and style correctly from the extensibility interface, use enum - 1. (11746)

• When the project is converted from Oracle or SQL Server to another database type using the Database Type Conversion Wizard, the source project is not deleted. Run the rqdelete_project stored procedure to remove that project. (14274)
• If you have not opened a RequisitePro sample project (Learning Project, Learning_Business, or QuarterByte Savings Bank Example Project) and try to convert it to another database type, you will receive an error message. If you want to experiment with converting the database type for a sample project, make sure you have opened the project at least once before you start the conversion. (14242)

If you are using participation e-mail, discussion replies are not added to the RequisitePro project if the project is opened exclusively when the reply is created. (12146)

If a dialog box or wizard in RequisitePro appears to stop responding, a hidden error message may be displayed behind the dialog box. Drag the box to another part of your screen to see if a hidden error message is displayed. Respond to the error message and continue. (11979)

• When creating RequisitePro schemas or databases on international operating systems, use the default names and passwords: RequisitePro, reqpro, reqpro. Non-English characters are not supported for the schema name and passwords for SQL-Server- and Oracle-based projects. (14940)
• The Rational E-Mail Reader doesn't accept project names that use double-byte characters. Therefore, participation e-mail cannot be enabled for those projects. (11773)
• In some languages, Excel and other products use a separator other than a comma when saving data as comma-separated value (CSV) files. If your language uses semicolons, do the following: to import a CSV file created from Excel to RequisitePro, change the semicolon separators to commas for the requirements to import correctly. (11775)
• When running queries, if the decimal separator and thousand's separator are different from the default of the language, Visual Basic conversion routines fail. (11423)
• On Japanese systems, if you are importing requirements from a Microsoft Word document based on a style, the import may fail. (11792)
• Japanese characters do not appear properly in a Microsoft Word document after an export of requirements from an Attribute Matrix. To correct the problem, open the Word document, select all text and select a new font. (13808)
• If you are using RequisitePro on a Japanese operating system and you attempt to create a RequisitePro document or export requirements while Microsoft Word is open, you receive an error message. To avoid this, close all instances of Word before creating a document in RequisitePro. (15432) (15566)
• On Korean and simplified Chinese systems, requirements in existing projects may be concatenated after cut, paste, and Rebuild Tags operations. This applies to all existing projects, including the Learning Project. (15540)

• When creating a new project from a baseline, the revision number in RequisitePro is not reset to 1.0000. This applies to project, document and requirement revision numbers. (14931)
• A project created from a baseline does not maintain the cross-project traceability links, discussions information, and associations with Rational ClearQuest and Rational Rose from the original baselined project. (13476)
• When opening a RequisitePro document in a project that was created from a baseline, you are notified the document was modified outside of RequisitePro. You can accept this message and then save the document. (14604)

RequisitePro cannot accept database fields (such as requirement text, requirement attributes) with more than 4000 characters between carriage returns. If you are using RequisitePro with ClearCase or ClearCase UCM and one of the fields exceeds this limit, the integrations will fail. (14285)

• If your project was upgraded from a version of RequisitePro prior to version 2000.02.10, you need to enable the extended editing feature if you want to modify the text of requirements from a Rose use case using Integrated Use Case Management. Enable extended editing on the Documents tab of the Project Properties dialog box.
• You must have Rose open before using RequisitePro's Associate to Use Case command. (15618)
• If you access the Rose Use Case Specification dialog box from RequisitePro (using the Go to Rose command) and change the use case name, clicking either the Apply or OK button in the dialog box will cause Rose to stop responding. To avoid this, access the dialog box from Rose when you want to change the use case name. (10755)
• In order to use the Associate to Use Case command in RequisitePro, Rational Rose must be running. (15646)

• If you are upgrading an existing "Studio" schema from ClearQuest version 2.0 to ClearQuest version 2000.02.10, an additional Requirement tab appears on the EnhancementRequest and Defect record forms in ClearQuest. This tab can be removed through ClearQuest Designer. (The tab that should be removed only has a "Requirement" field. The tab that should remain contains both a "Requirement" field and a "Tag" field.) (11912)
• On Windows 95 systems, when you launch the ASCQISetup.bat, two MS-DOS windows open. One may result in a Windows Kernel32.dll error. Click OK and launch the ASCQISetup.bat file again. (10866)
• If you are using non-English, special characters, when you launch the ASCQISetup.bat file, the special characters are not sent correctly. Instead, launch each command directly from MS-DOS. Copy each command (excluding REM commands) from the ASCQISetup.bat, paste it into the MS-DOS Prompt window and run each command. On Windows 9X systems, you must use environment variables for commands longer than 127 characters. (11625)
• After you have changed associations in ClearQuest, or deleted requirements, manually refresh any open views in RequisitePro (click the Refresh button) to make sure updated information appears in the Associate Enhancement Requests dialog box. (10862)
• When creating a new requirement from ClearQuest, do not click the ellipsis button in Create Requirement dialog box. The applications may stop responding. Once the requirement has been created, you can use the ellipsis button. (11070)
• When you are setting a ClearQuest query in the Query field of the Associate Enhancement Requests dialog box, you must choose a query that contains a ClearQuest ID in order for the integration with RequisitePro to work correctly. (10853)
• From within ClearQuest, if you remove an association to a requirement, then change the RA Project reference and add another requirement for the new project in the same session, errors will result. Instead, delete the requirement and commit the changes before changing the project reference and adding a new requirement. (10897)

Please see the ClearQuest release notes for information regarding additional integrations beyond ClearQuest and RequisitePro. In order to upgrade the RequisitePro/ClearQuest integration, you must complete the following steps in order. For specific information about each step, read the sections that follow.

1. Back up all data.
2. Apply the Repository 1.0 package to your ClearQuest database.
3. As necessary, perform the steps listed in the "Repository 1.0 package" section below.
4. Apply the following packages:
   • RequisitePro 1.4
   • RequisitePro Supplement 1.1 upgrade
   • TeamTest 2.0 (Note: You do not need to enable the record types for this package.)
5. Check in your schema and upgrade your ClearQuest database to the latest schema version.
6. Upgrade your Rational Repository via the Rational Administrator. (Consult the Configuring Rational Suite manual for more information.)
7. Delete all existing "RequirementMap" records from ClearQuest. (These records are created again when you run ASCQISetup.bat file.)
8. Edit and run the ASCQISetup.bat file located in the \Program Files\Rational\common\ directory.

If your ClearQuest database is based on any of the following schemas, you must apply new ClearQuest packages:

• DefectTracking Schema
• AnalystStudio Schema
• DevelopmentStudio Schema
• TestStudio Schema
• Unified Change Management
• EnterpriseStudio Schema

Apply the following new ClearQuest packages:

• Repository 1.0 Package
• RequisitePro 1.4 Package
• RequisitePro Supplement 1.1 Upgrade Package
• TeamTest 2.0 Package

There are a few general rules for package application because the ClearQuest Designer allows only one package application at a time for a particular schema:

• Run the package wizard.
• Apply the relevant package.
• Make any necessary modifications to your schema to support the new package.
• Check in the schema.

To support the conversion of Rational Repositories to Rational Suite Projects, a new version of the Repository package is required. A few changes in this package require work by the ClearQuest administrator in ClearQuest Designer to complete the upgrade.

As part of the application of the Repository 1.0 package, you will notice that many instances of the RepoProject field associated with some record types (such as Defect and Enhancement Request) are renamed to RAProject. Unfortunately, the automatic upgrade process cannot fully rename every instance of this field/record type. It will generally be simpler to apply these changes immediately after the application of the Repository 1.0 package. Specifically, the ClearQuest administrator will need to check and manually rename any instance of:

• Form controls that had referenced RepoProject: If you have used any of the out of the box "Studio" schemas such as AnalystStudio, DevelopmentStudio, TestStudio, or EnterpriseStudio, this step will be required. In addition, this step is very likely if you have included the RepoProject field on any ClearQuest forms that you might have created in your own custom schema, particularly as a result of applying an earlier revision of the Repository package. As part of the upgrade process, the underlying field name is changed to RAProject, but the field that the control points to is removed since it is no longer known by that name. You must select properties for that control and pick the RAProject field. If this is not done, the field will always appear read-only from the client and the designer schema validation process will report that there is no field associated with that control.
• Record Type families that had included RepoProject: This will be necessary only if you have created record type families that happened to include the RepoProject stateless record type. You will need to modify the members list of the Record Type family. Remove the reference to the RepoProject stateless record type and replace it with RAProject.

RequisitePro 1.4 and RequisitePro Supplement 1.1 Upgrade Packages

To support the latest version of the RequisitePro integration, application of two packages is required. They are the RequisitePro 1.4 package and the RequisitePro Supplement 1.1 Upgrade packages. It is important to apply the RequisitePro Supplement 1.1 Upgrade package and not the base package or the integration will not function properly. If you accidentally apply a version of a package that you wish to remove, you will be required to remove the entire schema version that includes that package.

There are two cautions when applying these packages. First, they expect the record types for "Defect" and "EnhancementRequest" to be named exactly as listed here. If you have renamed either of these record types, you will be unable to apply the RequisitePro packages. Second, the packages expect the submit forms for the Defect and Enhancement Request record types to be named "Defect_Base_Submit" and "EnhancementRequest_Submit" respectively. If you receive an error message while applying the package indicating that the "form name" form could not be found for the record type "record type", you should temporarily rename the form to what the package is looking for before applying the package and then rename the form back to your desired name after the package application.

After applying the RequisitePro 1.4 and RequisitePro Supplement 1.1 Upgrade packages, you should follow the instructions in the "Configuring Rational Suite" manual to complete the upgrade of the RequisitePro datastore and to re-initialize the integration between ClearQuest and RequisitePro.

TeamTest 2.0 package

The TeamTest 2.0 package is now an even more integral part of the Rational Administrator Project functionality. It will be required for you to apply the TeamTest 2.0 package even if you had not previously had this package applied. Many of the integrations of the Rational Administrator are contained within this package. You will want to apply this package to each of the record types that you wish to enable for the integration.

Telephone: 1-800-433-5444 or 408-863-5000 (outside the U.S. and Canada)
Fax: 408-863-4300
E-mail: support@rational.com
Web site: http://www.rational.com

Visit our Web site for more information about us!