Workarounds: Web client and server problems in Rational Requirements Composer and Rational DOORS Next Generation 4.0.6 and 4.0.7
The following known problems are related to the web client and server in the Requirements Management application 4.0.6 and 4.0.7 releases.
Workarounds
The following problems in this release have workarounds:
- Links cannot be created to Rational ClearQuest
- Some non-English fonts cannot be saved or rendered in graphical artifacts
- Rational RequisitePro baselines cannot be imported
- Licenses are not released when you log out
- When you run the setup wizard on Internet Explorer 10, the Finalize Application page for the RM application is blank
- When you delete cells from a table, other content is also removed
- Artifacts in a module might be incorrectly shown after you cancel the edit of a new artifact row
- The graphical editor add-on installer opens when the add-on is installed and disabled
- On Solaris and Linux systems, the Express setup wizard fails when finalizing the RM application
- Link columns might not display links if the link type has a URI defined
- After the RM server is started or during an online upgrade, server problems occur
- PDF documents cannot be viewed in modules on Google Chrome
- Links in reports that are generated in Microsoft Word format do not work
- Unicode characters are removed from downloaded files on Internet Explorer 8 and releases of Safari 5.1
- Timed-out queries might return a generic server error when you use the web server plug-in for WebSphere Application Server
- The Requirements View dashboard widget does not correctly paginate when a lifecycle status filter is applied
- In PDF reports, non-English and ideographic characters are not printed
- When printing reports, the page size for PDF documents cannot be changed
- When you upgrade to 4.0.3, you can save disk space by deleting the converter cache
- During the import of a CSV file that includes a FEAT requirement, a validation error occurs
- Automatic synchronization of artifact content and content in Name field
- Custom Word templates are not updated in an upgrade
- After a document is imported into a module, images that are in headings are not shown in artifacts
- During an import, the wizard might not detect images or text.
- After you save selected text as a new artifact, when the new artifact is linked to or inserted, an error occurs
- The thumbnails of screen flow artifacts are not always rendered in reports
- HTTP requests are not automatically redirected to HTTPS
- When the import wizard extracts requirements from a document, an error occurs
- A CRRRW8010E error occurs when you try to view a graphical artifact
- After a successful upgrade, the upgrade console incorrectly indicates that the upgrade failed
- If the server crashes or is improperly shut down, the server indexes can become corrupted
- Graphical artifacts that are embedded into text artifacts are not displayed in the requirements specification report for Rational Reporting for Document Generation
- Graphical artifacts might be clipped when printed from a browser
- Graphical artifacts cannot be printed by using the browser print function
- In rich text documents, space cannot be added between consecutive tables
- Text is displayed in multiple languages
- On Linux systems, the Rational Requirements Composer server does not start in console-only mode
- The Cut, Copy, and Paste editor menu options are disabled
- How to configure PDF output for Rational Reporting for Document Generation
- Long artifact names cause the artifacts to be displayed with their URL
- Importing a ReqPro Project that was integrated with Rational Requirements Composer requires a manual refresh prior to seeing changes
- When an artifact attribute is deleted from an artifact type, artifact exports fail
- The Rational Requirements Composer on-line migration requires a 4.0 RRC Analyst license, and the Jazz Team Server 4.0 read-only mode now supports installing and assigning licenses
- Adding or removing multiple IBM Rational ClearQuest record links from IBM Rational Requirements Composer or IBM Rational Quality Manager artifacts might not update all selected ClearQuest records
- In the Float data type, users cannot enter values of more than three digits after the decimal point
- The creation of the Money that Matters lifecycle sample might fail with a socket timeout
- Error importing large CSV files into Derby
- In environments that use Rational Requirements Composer V3.0.1.3 and earlier and Jazz Team Server V4.0, issues with snapshots occur
- Internet Explorer automatically generates mailTo hyperlinks that might fail the RM XHTML server validation process
- In the rich text editor, the font size of the bullet or number portion of a list cannot be changed
- In rich text documents, space cannot be added between consecutive tables
Limitations
The following problems in this release do not have current workarounds:
- The report wizard includes irrelevant parameter fields
- Report generation fails when too many artifacts are added to a report
- The Coverage of Requirements by Test Cases Trend report cannot filter the results by requirement type
- Memory consumption increases under load when you use a non-default log level for the Rational DOORS Next Generation server
- The number of a tags for a project is no longer visible
- Reports do not support Unicode Extension-B characters
- Clustered environments only: An HTTP 403 error is displayed when you try to open a module that was created by importing a document with many artifacts
- The import wizard and summary do not correctly display file names that contain non-ASCII characters, such as Japanese and Chinese characters
- Text searches do not support queries that include certain characters
- When you view artifacts in modules, some toolbar icons are no longer shown
- Re-authenticating from the Requirements Management application to IBM Rational System Architect fails
- Modules that are loaded into the data warehouse can contain a maximum of 100 artifacts.
- The Module Find operation does not account for language sensitivity when searching text
- Collections can no longer contain other collections
- Large ReqIF files or Rational DOORS migration files cannot be imported into Rational DOORS Next Generation
Workaround summary
Problem
When you try to create a link to a record in Rational ClearQuest, this message is displayed: CRRRW7250W Cannot link to a development plan.
Workaround
Contact IBM Software Support for a test fix.Related information
Workaround summary
Problem
Due to restrictions on the rendering library that is used to create graphical artifacts, some fonts cannot be used within those artifacts. You can identify a non-compatible font by trying to use it on text in a graphical artifact. If the font is not applied to the selected text, that font cannot be used by the graphical artifact rendering library.
Workaround
Specify an alternative font to use. The font must be installed on both the client computer that you use to edit the graphical artifact and on the server that contains the RM converter web application.Related information
Workaround summary
Problem
When you import Rational RequisitePro baseline .zip files into Rational DOORS Next Generation, the following issues might occur:
Issue 1
If you import a Rational RequisitePro baseline .zip file and Rational DOORS Next Generation does not support the compression method, the following error is displayed:
The Exception occurred while extracting invalid compression method Rational RequisitePro project baseline file cannot be uploaded.
The baseline .zip file is uploaded, but problems occur when you extract the compressed files. The following compression methods are known to cause this issue:
- Deflate64
- bzip2
- LZMA
- PPMd
Issue 2
If you import a Rational RequisitePro baseline .zip file with file names that contain non-ASCII characters, and the file name encoding does not support those characters, the following error is displayed:
The CRRRS9239E Error occurred while extracting the baseline archive. One of the reasons for this error could be that the baseline has the file names with non-ASCII characters and archive was not created with the option to use the UTF-8 encoding for file names. Please use an archive tool that supports creating an archive with the option of using UTF-8 encoding for the file names. Rational RequisitePro project baseline file cannot be uploaded.
Issue 3
If you enable debug logging and import large Rational RequisitePro baselines, you might receive an HTTP entity too large to be buffered in memory error in the RM log file, and the import fails.
Workaround
Complete these steps:1. Ensure that the compression method for the files in the baseline .zip file is DEFLATE. To check the compression method, use a tool such as the zipinfo command line utility.
2. Ensure that the file name encoding in the baseline .zip file is UTF-8.
3. Disable debug logging. Specifically, do not set these values in the log4j.properties file:
log4j.logger.com.ibm.rdm.fronting.server.rrs.migration.reqpro.ReqproMigrationService=DEBUG
log4j.logger.com.ibm.rdm.fronting.server.headers.services.ReqProMigration=DEBUG
log4j.logger.com.ibm.rdm.fronting.server.response.services.ReqProMigration=DEBUG
Related information
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Limitation summary
Problem
When you generate a “Print Module as a Book” or “Print Module as a Table” report, these parameter fields are shown in the report wizard:
- Report Parameter
- Parameters moduleURI
- Parameters projectURI
- Parameters serverURL
- Parameters viewCacheId
Those parameter fields should not be shown in the report wizard. You can ignore them.
Related information
Limitation summary
Problem
When you generate a report, if you add more than 250 artifacts to the report, the report generation process might fail. This problem is caused by an internal tool limitation.
Related information
Limitation summary
Limitation summary
Limitation summary
Limitation summary
Limitation summary
Limitation summary
Limitation summary
Limitation summary
Limitation summary
Limitation summary
Limitation summary
Limitation summary
Limitation summary
© Copyright IBM Corporation 2014, 2017
Yes