Rational RequisitePro 7.0.0.2 (version 7.0. Fix Pack 2)

Download Description

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/).

---

Defects fixed in this fix pack (roll-up of defects fixed in iFix01 thru iFix09):

This Fix Pack 7.0.0.2 for Rational RequisitePro includes all interim fixes and new, previously unreleased fixes subsequent to version 7.0.0.1.

IC46463 (RATLC01150969) - Column widths in Traceability Matrix views are now properly preserved when a project is saved and re-opened.

IC47023 (RATLC01095977) - After deleting a parent requirement (but not its child) in an offline document, users were not able to assign a new parent to the child requirement when bringing document online.

IC47330 (RATLC01098693) - Unusual punctuation, such as multiple periods within a sentence prevented the New Requirements wizard from accurately creating requirements as full sentences. The fix improves the accuracy of the wizard; however, it does not guarantee the capture of full sentences in all cases, due to the dependence on the Microsoft Word API for sentence identification. For best results, eliminate extra periods within sentences and other unusual punctuation before importing the document.

IC47741 (RATLC00762030) - Oracle optimization methods had differing impacts on performance in RequisiteWeb and RequisitePro. Fixes in 7.0.0.0 iFix005 and 7.0.0.1 have improved RequisiteWeb performance in Oracle.

IC51355 (RATLC01006568) - An error occurred in RequisiteWeb when displaying RequisitePro documents that contained empty and non-RequisitePro bookmarks. The conversion to HTML failed. The display function has been modified to ignore these bookmarks. If problems persist, avoid empty and non-RequisitePro bookmarks in documents. To resolve the problem if it persists, save the Word document to HTML outside of RequisitePro, and then convert the HTML back to Word format before attempting to display the document in RequisiteWeb.

-------------------------------------------------------------------------------
IC52388 (RATLC01018643) - When using the ASCQISetup.bat batch file for configuring the Rational RequisitePro integration with Rational ClearQuest (as an alternative to using the Integration Wizard), if the password for the user database is set, it was not clear how to include the password in the batch file. To specify the CQ Connection, you need to provide three more optional arguments after the required arguments for the "ascqisetup -c" command. These optional arguments are:
CQConnectionName
CQ_Password
RP_username
Example:
ascqisetup -c admin SAMPL EnhancementRequest Requirements_List EnhancementRequests_List RAProject Modify "" "" 1 test2 c:\temp\test2\test2\test2.rqs FEAT EnhancementRequest 2 Connection1 secret_password admin

In the example, "Connection1" is the CQ Connection name, "secret_password" is the Rational ClearQuest user password and "admin" is the Rational RequisitePro user name for the project.
----------------------------------------------------------------------------------

PK20615 (RATLC00144452) - If a document-based requirement's text ended with a double-byte character with a hexadecimal value of 0x5c in the trailing byte, the final character was truncated or converted to a 0 when changes were made to the requirement hierarchy. This was caused by a partial match of the double-byte character and the value of the requirement delimiter. The delimiter value for identifying document-based requirements in hierarchical functions has been modified to avoid confusion with the Japanese character. (This fix also resolves PK29496 RATLC01185370.)

PK24017 (RATLC00760015) - After canceling a login to an external project, if the user opened a view that contains traceability to requirements in the external project, a runtime error occurred. The error did not occur if the external project was disconnected manually before opening the view. The disconnect process is now invoked when a user cancels a login to an external project. This resets the requirement collections so that the user can open the traceability view without errors.

PK24337 (RATLC00987137) - When a user cuts requirement text from an external document, which contains Rational RequisitePro bookmarks, and pastes the requirement into a requirements document, the initial revision entry is missing in the requirement history. The missing entry causes Rational SoDA reports to fail when reporting revisions.

PK25030 (RATLC00988164) - The New Requirement wizard encountered problems if more than one key word was used. The problem was fixed by RATLC00738463.

PK28191 (RATLC00992597) - In version 2003.06.15 while attempting to log in to a RequisitePro project from Rational ClearQuest using the integration, if you canceled the login by closing the login window using the red "x" in the upper-right corner, the computer "hangs" and the application consumes CPU resources. This problem was fixed in version 7.0.0.0.

PK29174 (RATLC00492869) - When attempting to save a RequisitePro document that contains new changes, the user is prompted to Review Changes before saving. In the previous release when the user reviewed changes, the Document Changes window was displayed, but the document was not repositioned to review each change as it was saved. The function has been modified to reposition the document to review each change.

PK30561 (RATLC00996376) - Users with read-only permissions were able to enter text in the Text field in the Requirement Properties window, although they were not able to save their changes. The Text field is now disabled if the user does not have permissions to modify it.

PK30594 (RATLC00996463) - When archiving projects in Rational RequisitePro, documents were not included in the archive if the package in which they were located was not expanded in the Requirements Explorer. A new function was added to load all documents (including those in collapsed packages) into memory before creating an archive.

PK30887 (RATLC00997000) - When creating views that included traceability to external projects that are based in Microsoft Access, the view creation failed if the external project had a dot (.) in its name. The function has been modified to handle an external project name with this construction.


PK31934 (RATLC00998973) - When using the Rational RequisitePro Cut and Paste commands in the RequisitePro menu in Microsoft Word twice on the same requirement while Track Changes was enabled, the first four characters were not included in the requirement text. The cut and paste logic has been modified to include all text during this operation.


PK32861 (RATLC00498130) - When using the RequisitePro integration with ClearQuest on a Japanese language system, it is possible for the double-byte input in the RequisitePro text field to exceed the 254-byte limit for descriptions in ClearQuest. Previously, users received an error that interrupted the process. The text is now truncated to accommodate the field size in ClearQuest, and no error occurs.

PK32912 (RATLC01000950) - Programs that were compiled for the RequisitePro 7.0.0.0 API were not compatible with 7.0.0.0 iFixes. This problem was resolved in 7.0.0.1 (Fix Pack 1). Programs compiled against 7.0.0.0 function properly with 7.0.0.1 (Fix Pack 1).

PK33086 (RATLC01001304) - In a Traceability Matrix view in RequisiteWeb, additions and modifications to traceability relationships using the multiple selection feature resulted in an unreasonably long delay. The data handling revisions in this fix improve the performance of these functions with between 25% to over 50% faster responses.

PK33449 (RATLC01001937) - When importing a CSV file that included double-byte characters, non-double-byte characters were encoded as double-byte characters in Rational RequisitePro. This corrupted the hierarchical (parent/child) relationships in the requirements. The import function has been changed to retain hierarchical relationships when the text includes double-byte characters.

PK33585 (RATLC01002147) - In RequisiteWeb, when viewing a Traceability Matrix that did not include any column requirements, the frame did not display all requirements on the page and no scroll bar was available. The display function has been modified to provide a scroll bar.

PK33905 (RATLC01002676) - In some cases, the command File > Project Administration > Renumber Requirements did not renumber the document-based requirements correctly to match the order in which they appear in the document. This problem has been fixed.

PK34555 (RATLC01003905) - The view in a document shifted when creating a requirement from text, requiring users to scroll to locate the new requirement. The function has been modified to retain the document position after a requirement is created.

PK34908 (RATLC01004515) - When exporting an Attribute Matrix view into Microsoft Word, the user was prompted to save the Rqview97.dot file. If the user selected Cancel, an error was displayed. An internal file, which was set to read-only, has been modified, allowing the user to export the view without being prompted to save the Rqview97.doc file.

PK35268 (RATLC00501813) - Opening a RequisitePro document that is stored in a ClearCase VOB resulted in errors. The handling of UNC paths for documents in a ClearCase VOB has been modified to correct the problem.

PK35453 (RATLC00057983) - Users were unable to create a requirement in an offline document if its text was positioned within a non-RequisitePro bookmark. The requirement creation function has been modified to disregard non-RequisitePro bookmarks and therefore allow the creation of the requirement in the offline document.

PK35714 (RATLC01186922) - In some cases, an inactive rather than the current administrative user was selected when creating a RequisitePro baseline, causing an error. Also, when the baseline data included a document that was last modified by a user who was subsequently deleted, an error occurred when a user attempted to create a project from the baseline. These problems have been resolved.

PK36058 (RATLC01006493) - When sorting requirements by document position in a project based in Microsoft Access or Microsoft SQL Server, if the position value exceeded 32767 (number of characters from the start of the document), the value was set to 0 and the sorting was then invalid. This was fixed in 7.0.0.1 iFix01 by using the relative document position (first, second, third requirement, etc.) rather than number of characters. Related fixed defects are IC49332 (RATLC00987513), IC46922 (RATLC00961822), PK36291 (RATLC01007244).

PK36436 (RATLC01092657) - In the 7.0.0.1 (Fix Pack 1) release, the navigation between requirements and records for the integration with ClearQuest was not functioning. The navigation has been fixed.

PK36672 (RATLC01008050) - When multiple users are working in RequisiteWeb and editing the same requirement, if one user saves a change and a second user attempts to save a change, the second user is notified of the other user's change.

PK36708 (RATLC01008112) - The discussions notification feature has been changed so that an e-mail notification is sent to the originator of a discussion or a discussion reply, as well as to all other participants in the discussion. Duplicate: PK36693 (RATLC01137557)

PK37184 (RATLC01187167) - If one RequisiteWeb user changed a document-based requirement in the Requirement Properties page just as a second user was taking the document offline, the first user's changes did not appear in the offline document. When the second user brought the document online, the requirement was overwritten and the first user's changes were lost. The RequisiteWeb offline document function now checks for pending database changes just before locking the document and taking it offline.

PK37309 (RATLC01009133) - Users were able to relocate (drag and drop) requirements and documents in different packages even though the users only had read permissions for those requirement and document types. The drag and drop function has been modified to check for update permissions before the action is complete. This constraint only applies to requirements and documents; views and packages do not have read/update security policies. Duplicate defects: PK36336 (RATLC01007327), PK37307 (RATLC01336895).

PK37322 (RATLC00507641) - When creating a requirement, if a user entered values for more than one attribute of the User Name type, a validation error occurred and the requirement could not be created. You can enter multiple user name values while creating a requirement.

PK37409 (RATLC01009274) - When importing requirements from Microsoft Word documents and identifying requirements by Word styles, not all characters, lines, and paragraphs were imported.

PK37480 (RATLC00507835) - On a Japanese installation of RequisiteWeb, when filtering an Attribute Matrix view on the Contact attribute with a "Not=" operator set equal to blank or "<NO ENTRY>", the view displayed all requirements regardless of the Contact attribute value. The filter function has been modified to resolve this problem.

PK37486 (RATLC01009392) - Japanese characters were corrupted when exporting a view to a CSV file. The export operation now exports Japanese characters properly. The fix applies to all attributes that contain text values.

PK37587 (RATLC00507982) - In RequisiteWeb, a user who attempted to change a traceability relationship in a Traceability Matrix view was not notified if the relationship was deleted by another user after the first user opened the view. A message is now displayed informing the user that the traceability has been modified. The view is then refreshed to display the current data.

PK37966 (RATLC01187293) - In the RequisitePro Metrics tool, the Requirement Creation (by date) filter was returning too many results. The filter has been modified to display the correct results.

PK38880 (RATLC01011615) - On the Japanese version of version 7.0.0.1 (Fix Pack 1), when installing to a release area, directories for the Composite, Traditional, and Use-Case project templates were not installed. The components are installed in this iFix.

PK39068 (RATLC01187414) - The batch refresh for the integration of RequisitePro and ClearQuest failed for projects based in an Oracle database. A query that is used in the batch refresh has been modified to support the data type requirements of Oracle databases.

PK39074 (RATLC01011976) - When using keywords in the New Requirements wizard to create requirements while importing a document or from a range of text in an existing document, if the text ended with a Word cross-reference followed by several carriage returns, the carriage returns were included in the requirement text as null characters and an error was displayed "Runtime error: Invalid procedure call or argument...". The New Requirements wizard has been modified to truncate trailing null characters and the requirement is created successfully.

PK39874 (RATLC01013360) - It was possible in some cases to introduce data corruption when saving a RequisitePro document with the Word Track Changes feature enabled. This fix introduces a new optional security setting that prevents users from saving documents in RequisitePro with the Track Changes feature enabled. To set this option, edit the <project_name>.rqs file, which is located in the project directory. Add the following line to the file:
isTrackChangesAllowed=0
If a user attempts to save a RequisitePro document in this project when this property is set to 0, the save operation fails and a message is displayed: "Unable to save document with Track Changes enabled."

PK40101 (RATLC01013731) - Users with read-only permissions for requirement attributes were able to modify the attribute values using the CSV source option in the Import wizard. This problem only occurred when manually matching imported attributes and existing attributes in the Import wizard. This fix now prevents users with read-only permissions from manually matching attributes in the Import wizard.

PK40339 (RATLC01196542) - When ReqPro integrates with ClearCase in UCM mode, an error is displayed when open the ReqPro project and document

PK40888 (RATLC01015067) - If a document was moved to a different directory in the file system using Windows Explorer, users that do not have Delete permissions were able to delete the document while attempting to open it in Rational RequisitePro.

PK40941 (RATLC01015139) - When exporting an Attribute Matrix view into Microsoft Word, at the end of the export process, Word opened, but the document containing the exported view did not open. The export process has been modified so that the exported document opens upon completion of the process.

PK42856 (RATLC01018592) - When managing views that had requirements sorted in ascending order by document position, the document position were not always displayed correctly.

PK43110 (RATLC01019160) - When changing the width of row requirements in a RequisiteWeb Traceability Matrix view, the frames become unaligned so that the traces in the matrix cells do not align with the column requirements. The issue is only reproducible on some versions of Internet Explorer. A new validator function has been added to synchronize the frameset every 0.1 seconds.

PK43598 (RATLC01200999) - When Rational RequisitePro was installed in a Japanese-language release area, the project templates were not created.

PK43658 (RATLC01020311) - When using the Rational RequisitePro feature that prevents users from saving Microsoft Word documents with Track Changes enabled, problems occurred when offline documents were saved with Track Changes enabled and then brought online. The problem is fixed so that when Track Changes prevention is set and a document is brought online with Track Changes enabled, a new error message is displayed: "Unable to bring document online with Track Changes enabled." The operation is successfully canceled.

PK43721 (RATLC01020428) - When entering values in fields in a new requirement in RequisiteWeb, if users entered incorrect values they were redirected to the Project Properties page and lost all input for new requirement. The requirement creation function has been modified so that the new requirement data is now cached. If an error occurs, the data is repopulated in the new requirement.

PK43810 (RATLC01020579) - After creating a project from a baseline, requirement text does not appear as expected when selecting the "Go to the selected requirement" button on the toolbar.

PK44185 (RATLC01021361) - When using the GetRequirement method in the API (RequisitePro Extensibility Interface), the user was unable to retrieve the document location name with the requirement. New functionality has been added to return the document name with the requirement.

PK44410 (RATLC01021793) - When modifying Trace To or Trace From "Requirements of type" or the "Located in" settings from the Traceability page of the requirement properties window, Rational RequisitePro sometimes encountered a runtime error "OS error 16r0" and the application closes. The issue has been resolved.

PK44736 (RATLC01022389) - When editing a user profile in RequisiteWeb, read-only fields were not disabled. An error was displayed if a user with read-only permissions attempted to save changes to a profile. Read-only fields have now been disabled for user profiles in RequisiteWeb.

PK45791 (RATLC01203633) - When a user printed a Project Summary Report, it displayed the CQ Integration attributes as type “Text” rather than the correct type “CQ Integration.” The reporting function has been modified to correctly display the CQ Integration, URL Link, and User Name types.

PK46208 (RATLC01188837) - An error occurred when transporting a project with the same user and schema from DB2 to DB2 even though the DB2 server and database are different. A message appeared stating that the source and destination database is the same. The code has been fixed to check the DB2 alias in addition to the schema to detect if the source and destination DB were the same.

--------------------------------------------------------------------------------
PK47070 (RATLC01023607) - Users were unable to open some exported RequisiteWeb views as CSV files in Microsoft Excel, depending on the default character encoding for the RequisiteWeb server locale. The following encoding is used by default for the indicated locales. All are supported by Microsoft Excel except UTF-8:

Windows-1252 - English, French, Italian, German, Swedish, Dutch
Shift_JIS - Japanese
GB2312-80 - Simplified Chinese
Windows-1255 - Hebrew (see the known problem for this APAR below)
EUC-KR - Korean
UTF-8 - all others

If the RequisiteWeb server locale defaults to UTF-8, RequisiteWeb administrators must specify the character encoding for the exported CSV files so that users can view them them in Excel. Set the following parameter in the config.txt file on the RequisiteWeb server:

CsvExportCharacterEncoding=

The default location of the configuration file is: C:\Program Files\Rational\Common\rwp\EmbeddedExpress\profiles\profile2\ installedApps\DefaultNode\ReqWeb.ear\ReqWeb.war\WEB-INF\classes\config.txt

When specifying this value, use one of the supported character codes that are shown above with their various language locales; for example: CsvExportCharacterEncoding=Windows-1252

When using a locale that defaults to a supported character encoding, you can leave the value for this new parameter blank.
----------------------------------------------------------------------------------

PK47603 (RATLC01205484) - Traceability views in the Rational RequisitePro client for Web (RequisiteWeb) were not returning correct results when tracing to a requirement type and adding a filter on an attribute. All "trace to" results were displayed; there was no filtering for the specified attribute values. The "trace to" query function has been modified to recognize all attribute filter criteria.

PK47980 (RATLC01026839) - After migrating a project from Microsoft SQL Server to Oracle the View > Expand All command resulted in very slow performance. The SQL statements associated with that command have been modified to provide significantly faster performance.

PK48452 (RATLC01011240) - The license checkout code in the RequisitePro Extensibility Interface (RPX) did not consistently manage licenses to ensure that the number of checked out licenses matched the number of active sessions in RequisiteWeb. RequisiteWeb now manages the licenses to ensure that a license is checked out for every active user session and the license is checked in when the user ends the session.

PK48650 (RATLC01189591) - When comparing two baselines in Japanese versions of RequisitePro, the following error occurred: java.lang.reflect.InvocationTargetException. This problem has been resolved.

PK48904 (RATLC01207027) - Users encountered a 404 HTTP error when attempting to open RequisiteWeb if Rational RequisitePro was installed in a location other than the default: C:/Program Files/Rational. An error message containing an explanation is now displayed.

PK49039 (RATLC01252989) - When projects are converted from Microsoft(R) Access(TM) to a Microsoft SQL Server(TM) database and the user attempts to run an Attribute Matrix filter query for an attribute text value that is longer
than 30 characters, the query fails if the text is not in the first 30 characters of the value. While the project accommodates 255 characters in the attribute text, the value is truncated to 30 characters as a result of the database conversion. The database conversion function has been modified to retain the full content of textual attributes.

PK49207 (RATLC01149858) - When performing a baseline comparison using the Baseline Manager, information was missing in both the report and comparison tree when changes were made in more than one node level. The compare function has been modified to perform the comparison on all the packages, including inserted or deleted ones.

PK50048 (RATLC01092416) - When users attempted to view integrated requirements in RequisiteWeb from the Rational ClearQuest Web client, the project login for RequisiteWeb failed. Users can now successfully log in to RequisiteWeb and view the associated requirements from ClearQuest Web.

PK51044 (RATLC01032464) - When using the Baseline Manager to generate a report that compares two package baselines and the root package for the project is not included, the report generation was interrupted and an error occurred. The package compare function has been modified to run successfully even when the root package is not included.

-----------------------------------------------------
PK51400 (RATLC01252959) - An error occurs when working in a project that uses a Microsoft Access database and the user attempts to apply a filter query to an Attribute Matrix or Traceability Matrix view that includes requirements with external traceability relationships. For an Attribute Matrix, the error occurs if the Trace From or Trace To attributes are displayed. The error includes the following text:

Unable to run query: ReqType.Key(17) 17.RelCriteria(-100 in 5.3 AND -103 ="True")
[Microsoft][ODBC Microsoft Acces Driver] Could not find file...

The error was caused by the incorrect handling of the database name and project name in the filter query function. The function has been modified and the error is resolved.
-----------------------------------------------------

PK52216 (RATLC01211198) - When viewing revision history for multiple requirements in RequisiteWeb, incorrect revision history is displayed. This occurs when opening a requirement from a view in a new window and clicking the Revision tab and History button. After viewing a second requirement in the same manner, if you return to the first requirement, the history window displays the content from the second requirement. The revision history display function has been modified to correct this problem.

PK54796 (RATLC01258105) - When logging in to a project using the Rational RequisitePro client for Web (RequisiteWeb), if the user's password contained only numeric content, the user might have been identified with a previous user's profile. The user identification function has been modified to retrieve the correct user profile, regardless of the alphanumeric content of the password.

RATLC01021392, RATLC01022940 - RequisitePro failed with LDAP servers that do not allow anonymous binds.
In previous releases, RequisitePro used an anonymous bind when initializing a connection to an LDAP server. In some cases, this resulted in errors with the Bind DN and Bind DN password if the LDAP server did not allow anonymous binds. The problem did not occur with most Active Directory LDAP servers because, by default, the Active Directory allows anonymous logins; however, the errors did occur with non-Active Directory servers that require an initialization bind to perform any search and bind operations. The anonymous bind function has been removed from RequisitePro and the BindDN and BindDN password is used, if provided.

RATLC01039454 - It was possible to access external Web site content in the RequisiteWeb help, causing a possible security risk known as cross-site request forgery. The help has been modified to check context changes so that if there is an attempt to reference another site or an invalid help file, the user is directed to the main help page in RequisiteWeb.

Fixed indirectly:
IC47218 (RATLC00755062), IC51124 (RATLC00995818), PK06368 (RATLC01086816), PK28191 (RATLC00992597),
PK31704 (RATLC00998542), PK33277 (RATLC00498765), PK36291 (RATLC01007244), PK39609 (RATLC01195459),
PK40059 (RATLC01196088), PK47616 (RATLC01026329), PK48151 (RATLC01206051)