Workarounds: Web client and server problems in Rational Requirements Composer 4.0.3 and Rational DOORS Next Generation 4.0.3
The following known problems are related to the web client and server in the Requirements Management application 4.0.3 release.
Follow this link to see the Rational DOORS Next Generation 4.0.3 rich client workaround article.
Workarounds
The following problems in this release have workarounds:
- The Requirements View dashboard widget does not correctly paginate when a lifecycle status filter is applied
- Migration of module history can cause the server to be unresponsive
- In PDF reports, non-English and ideographic characters are not printed
- In Internet Explorer, artifacts that include custom tables are not correctly printed in reports
- When printing reports, the page size for PDF documents cannot be changed
- The rich hover over a requirement artifact might display an internal server error
- 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
- Links in error messages point to a “page not found” in the information center
- When you try to create an artifact after you add an artifact to a module, a warning message is shown
- 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
- Attributes are duplicated after you import modules from Rational DOORS by using ReqIF.
- 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
- The Save button on the Administration page remains enabled before and after the user makes and saves changes in the form
- 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. 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:
- 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
- To indicate a suspect state, link columns on the Artifacts page show only the incoming suspect icon.
- 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 a saved view that contains a lifecycle status filter is displayed on a dashboard in the Requirements View widget, you cannot paginate through the results. If you try to move to the next page, this error message is displayed: CRRRW7558E The server indicates that it does not permit the operation. The message that follows might include additional information about why the operation is not permitted.
Workaround
To work around this issue, complete one of these steps:
- In the Requirements View widget, change the page size settings so that you can see a maximum of the first 50 results.
- Open the Artifacts page and run the saved view. On the Artifacts page, you can correctly paginate through the results.
- On the dashboard, add the Requirements Tracing widget and set the widget to use a similar lifecycle status filter.
Related information
Workaround summary
Problem
When you upgrade to version 4.0.3 from version 3.0.1 or later, the history resource format is migrated to a new, more compact format as users update artifacts in version 4.0.3. If users update many artifacts in a short period, excessive load is placed on the server. This issue occurs especially with modules that contain many artifacts.
The excessive load can cause the server to become unresponsive. This problem is more likely to occur just after the server has been upgraded to version 4.0.3, during an initial period of heavy use.
To determine whether the server is experiencing excessive load due to history migration:
- Log in to the Requirements Management (RM) server as a JazzAdmin user at https://rmhost:port/rm/counts.
- In the AsyncTasks section, find the MigrateOldChangeLogsToFeed row.
- View the Active column and verify whether it shows 10 or fewer active migration tasks. If the column consistently shows more than 10 active change log migration tasks, the migration might adversely affect query performance.
- To assess query performance, on Jazz Team Server, check the jts.log file for canceled queries. Canceled queries are indicated by this message: CRJZS5544W.
- If the jts.log file indicates canceled queries and the number of change log migration tasks is high, follow the workaround steps.
Workaround
Complete these steps:
- Contact IBM Software Support and request the RM change log migration tool.
- Restart the Requirements Management (RM) server and Jazz Team Server to ensure that the change log migration and any long-running queries are stopped.
- Run the change log migration tool on your RM server by following the instructions included with the tool.
- Before you start using the RM server again, wait for the tool to finish running. Depending on the amount of history resources, it might take several hours for the tool to finish. If you use the RM server while running the tool, the server might become unresponsive and the tool might fail.
Related information
Workaround summary
Problem
The performance PDF file does not support non-English and ideographic characters. If those characters are included, information is not displayed in reports.
Workaround
When you print a report, use sophisticated format or Microsoft Word format. Those formats support non-English and ideographic characters, with the exception of Unicode Extension-B.
Related information
Workaround summary
Problem
In Internet Explorer 9, when you print a report of an artifact that includes a custom table, the table is not properly displayed in the report.
Workaround
Open and save the artifact in another supported browser, such as Firefox. After you save the artifact, you can print the table by using any browser, including Internet Explorer.
Complete these steps:
- Open the artifact in any supported browser except for Internet Explorer.
- Click Edit.
- Save the artifact without making changes.
- Print the report.
Related information
Workaround summary
Problem
When you print a report to a PDF document, the page size cannot be changed. Even if you try to change the size by editing the com.ibm.rdm.fronting.server.publish.PaperSize property, the size cannot be changed.
Workaround
Print to Microsoft Word format, as that format supports changes to the page size.
Related information
Workaround summary
Problem
When you hover over a requirement artifact, the rich hover might display this error message: ERROR 500: Internal Server Error. java.lang.NullPointerException.
Workaround
Complete these steps:
- Open the artifact.
- In the sidebar, expand the Links section. If you are prompted to log in to an associated project, log in.
Related information
Workaround summary
Problem
The 4.0.3 version of the converter cannot read old cache files. Although new cache files will be created as needed, the old files are not deleted. To save disk space, you can delete the converter cache.
Workaround
Complete these steps:
- Find the location of the cache directory:
- If you are using Apache Tomcat, the default location is JazzInstallDir/server/rrcweb/cache.
- If you are using IBM WebSphere® Application Server, the default location is ProfileRoot/rrcweb/cache, where ProfileRoot is the root directory of the WebSphere profile that contains the converter application.
Tip: You can also find the location by going to the converter diagnostic page. With the application server running, go to http://host:port/converter/htmlgen; for example, http://exampleserver:9443/converter/htmlgen. On the page that opens, note the location of the cache directory.
- Stop the application server.
- Navigate to the cache directory, and then delete all of the files from the directory.
- Restart the application server.
Related information
Workaround summary
Problem
If you import a CSV file that includes requirements of the FEAT type, a validation error might occur. This error occurs only on projects that were created by using the Traditional Requirements template.
Workaround
Complete these steps:
- From the Admin menu, click Manage Project Properties.
- On the Artifact Attributes tab, select the Business Priority artifact attribute.
- Make a change and then save it. For example, you might add a description and save it.
- Import a FEAT requirement as you normally would.
Related information
Workaround summary
Problem
When you create or edit an artifact, you can type a name for the artifact in addition to the main text content of an artifact. The content that you type in the Name field acts as a title, which identifies the purpose of the artifact.
If the Name field is empty, it is automatically populated from a shortened version of the artifact’s text content. If the content of the artifact is later modified, the content in the Name field is synchronized and updated accordingly. However, if the content in a Name field is explicitly set, the automatic synchronization no longer occurs. One situation in which this might happen is if you add an existing artifact into your module and that artifact already has a Name field explicitly set.
Workaround
If the synchronization does not seem to be occurring for a particular artifact, another user might have explicitly set the content of the Name field. To get the synchronization to work again, delete the content in the Name field.
Related information
Workaround summary
Problem
In version 4.0.3, if you get an error or warning message that contains a linked ID, such as CRRRW7321W, when you click the linked ID, the information center opens and displays a “page not found” message. This problem occurs because the messages were recently moved from the product information center to their own information center on Jazz.net.
Workaround
If you get an error or warning message that has an ID, go to the messages information center, and then search for the message ID.
Related information
Workaround summary
Problem
After you add an existing artifact to a module, if you try to create an artifact whose type is not the type that is currently set in the blue Create button, a warning message about concurrent access is shown.
Workaround
When the warning message is shown, click Yes. Then, you can create an artifact. The warning message is not shown again unless you try to add an existing artifact.
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
Limitation summary
Problem
Unicode Extension-B characters cannot be printed in reports in the Requirements Management (RM) application. Artifacts can contain Unicode Extension-B characters, but those characters are not included in printed reports.
Related information
Limitation summary
Problem
In a clustered environment, if you try to open a module that was created by importing a document with many artifacts, an HTTP 403 error is displayed. Also, in the module artifact folder, not all of the imported artifacts are displayed.
If you experience this problem, contact IBM Software Support.
Related information
Limitation summary
Limitation summary
Limitation summary
Limitation summary
Limitation summary
Limitation summary
Limitation summary
Limitation summary
Limitation summary
© Copyright IBM Corporation 2013, 2016
Yes