Rational RequisitePro 7.0.1.2 (Version 7.0.1 Fix Pack 2)

Download Description

This Fix Pack 7.0.1.2 for Rational RequisitePro includes all interim fixes and fix packs subsequent to version 7.0.1. This fix pack is a full product install of Rational RequisitePro. Fix packs and other maintenance releases are available at IBM Rational Support on the Web (http://www.ibm.com/software/rational/support/upgrades/).

Fixes in this fix pack

This list reflects customer-reported Authorized Problem Analysis Reports (APARs) that have been fixed since 7.0.1.1. The internal RATLC defect tracking number is also included. For earlier fixes, see the 7.0.1.1 or 7.0.1 release notes.

PK51208 (RATLC01210072) - When creating a project from a baseline, if the original project was based in an IBM DB2 database, external traceability information was lost in the new project. The baseline capability has been modified to preserve the external traceability.

PK57544 (RATLC01044172) - An error occurred when running a batch refresh for the RequisitePro integration with Rational ClearQuest: "Invalid Use Of NULL". The problem was occurring due to an
unexpected value of NULL in the RequisitePro RqUserDefinedFields table. The batch refresh code has been fixed to ignore the NULL value and treat it as a blank.

PK57727 (RATLC01044426) - When adding CQ Requirement attributes to Rational RequisitePro projects using the RequisitePro Extensibility Interface (RPX), the attributes were not retained in the project database. This problem has been fixed.

PK58195 (RATLC01045201) - When viewing attributes of a requirement that has multi-select attribute types, the attribute value settings were not displayed in RequisiteWeb. The values were visible in the Rational RequisitePro client for Windows. The attribute value display has been modified to correctly present these attribute values in RequisiteWeb.

PK58900 (RATLC01352888) - An error occurred when creating an Oracle-based project from a Rational RequisitePro baseline if the original project, which was used to create the baseline, included user-defined text attributes with null (blank) values. The function for creating projects from baselines has been modified to prevent this error.

PK59497 (RATLC01220677) - When comparing baselines of large projects, the Rational RequisitePro Baseline Manager tool sometimes encountered memory errors. The Baseline Manager tool has been modified to support comparisons of larger baselines.

PK60942 (RATLC01052016) - Microsoft Word Documents in a RequisitePro project were set to read-only permissions when using Rational ClearCase UCM to baseline requirement assets. The UCM implementation has been modified to preserve the current document permissions when creating a baseline.

PK62632 (RATLC01055733) - Error when taking document offline\bringing a document online in a shared location. This error occurs when taking a document offline to remote drive using Word2007.

PK62971 (RATLC01356312) - When running the Metrics tool, the Metrics report is returning the wrong number of requirements for "Attribute Value Change". The error only seems to occur when the there is an attribute that contains the name of another attribute.

PK64758 (RATLC01358828) - Metrics Tool is giving wrong results. It will not support requirement revision time now and it's designed for dates only. If text is changed on a day when attribute values is also changed, the Metrics Tool will report text changed for both attribute values.

PK65793 (RATLC01063283) - Data corruption occurred when requirements were moved from the project database to a document. Requirements were renumbered when moved from their original folders, sometimes replacing other requirements.

PK65933 (RATLC01063572) - The Traceability Tree View Export operation was generating random characters in requirements exported to MS Word. For example, Requirement TC404 would appear as "hTC404".

PK66552 (RATLC01065158) - There was a problem when remote documents were brought on-line using Word 2007. This problem occurred when the original RequisitePro document or project was stored remotely. An error message indicated that the file was already in use.

RATLC01039242 - In the integration with Rational Software Architect, opening the Requirements perspective and switching between perspectives was very slow. The performance has been improved.

RATLC01061357 - After upgrading to 7.0.1.1 IFIX03, multiple errors where encountered when requirements with trace-to relationships were created.

RATLC01205513 - When working in a Rational RequisitePro document, if users created requirements with long descriptions that included double-byte characters, an error occurred: Runtime error ‘1’ Subscript out of range. The requirement creation function has been modified to correct this problem.

RATLC01229317 - The Attribute Matrix view did not show requirements when filtering on package using DB2.

RATLC01356312 (PK62971) - Metrics Reports Displays wrong number of Requirement for "Attribute Value Change".

RATLC01358828 (01358828) - Metrics Tool is giving wrong results.

To review details, search for the Authorized Problem Analysis Report (APAR) number (ICxxxx or PKxxxx) at the IBM Rational RequisitePro Support Web site (http://www.ibm.com/software/awdtools/reqpro/support/). Paste the APAR number in the "Enter search terms" field.