Workarounds and Limitations: Known issues in IBM Rational DOORS Next Generation 6.0
The following known problems are related to the Rational DOORS Next Generation 6.0 release.
Upgrading from a version 5 release
For details about known issues that relate to upgrading Rational DOORS Next Generation from a version 5 to a version 6 release, including specific defects and fixes, see the IBM Rational DOORS Next Generation 6.x migration defects Flash article from IBM Support.
Workarounds
The following problems in this release have workarounds:
- Data is lost if new artifacts are created in a locked module
- In Rational DOORS Next Generation, if you use Internet Explorer 11 and use an input method editor (IME) to edit artifacts in modules, unexpected results occur
- Large change set deliveries on DB2 databases might fail with an SQL error
- The Alt+e keyboard shortcut does not insert the euro sign in the Module editor
- Anchor point connections cannot be changed by using keyboard shortcuts on a Turkish Q keyboard
- Table cells are pasted incorrectly from Microsoft Word when “Repeat as header row at the top of each page” is selected
- Links can be delivered before the creation of the link type is delivered
- Linking to or from requirements artifacts that were created in a version 3 release causes an HTTP 400 error
- Links between artifacts in Rational DOORS 9 and Rational DOORS Next Generation do not work as expected when configuration management is enabled
- Graphical artifacts cannot be edited in version 6.0 of the Requirements Management application if an earlier graphical editor is installed
- When you upgrade Rational DOORS Next Generation from a version 4 release, the 4.0.1 token, floating, and authorized user licenses are not automatically upgraded
- After upgrading to 6.0, the Requirements Management server is slow or times out
- During an upgrade, the CRJAZ0554I timeout error might occur
- Concurrent changes to an artifact can cause version issues in configurations
- In some browsers, images cannot be pasted from the clipboard into an artifact
- Modules imported into a change set using ReqIF, discarded, and then reimported cannot be delivered
- In a module, pressing Ctrl+Enter quickly in succession results in unsaved artifacts
- Workarounds and limitations for uploaded file previews
- WebSphere Application Server stops responding and logs an out-of-memory error
- Text in the editor might be displayed in a language that is not installed
- Rational RequisitePro baselines cannot be imported
- Link columns might not display links if the link type has a URI defined
Limitations
The following problems in this release do not currently have workarounds:
- A change set can be delivered that removes an artifact from a project without removing it from a module
- Conflicts between modules incorrectly resolve to the source version
- In projects that are not enabled for configuration management, some dialog boxes list all projects instead of ones you can access
- Quick Search results do not correctly include artifacts that have a format of Diagram
- Running the Data Collection Component to collect Rational DOORS Next Generation data might be slower than in previous releases
- Dashboard widgets only display data from the default stream
- If PDF documents are viewed in Microsoft Internet Explorer, the PDF document might hide menus or controls
- Module baselines were replaced with project baselines
- The audit history is not displayed for modules
- Revision history of an artifact doesn’t show baseline icons
- ReqIF import feature does not support importing data into multiple configurations of a project
- Imported Microsoft Word tables might be displayed incorrectly if the original borders are misaligned
- A module cannot have multiple templates
- The number of a tags for a project is no longer visible
- Text searches do not support queries that include certain characters
- Large ReqIF files or Rational DOORS migration files cannot be imported into Rational DOORS Next Generation
Workarounds
Workaround summary
Problem
When you edit a module, you can insert new artifacts into the module, type in the artifacts, and save the artifacts either explicitly or by creating another artifact. If the module is already locked by someone else, the system should prevent you from inserting new artifacts into the locked module. However, in Rational DOORS Next Generation 6.0, the system does not prevent this action. Instead, you can insert, type in, and save new artifacts in a locked module in what appears to be a successful process; however, the artifacts are not saved and the changes are lost if the module is refreshed.
Workaround
Complete either of these workarounds:
- Do not lock modules. This approach prevents the persistent lock that causes concurrent edits to fail silently.
- Do not create artifacts within a module. Instead, create the artifacts separately, outside of a module. Then, add the artifacts into the module by using the Insert Existing Artifact context menu.
Related information
Workaround summary
Problem
In Rational DOORS Next Generation, if you use Internet Explorer 11 and use an input method editor (IME) to edit artifacts in modules, unexpected results occur. For example, unwanted text characters are entered.Workaround
Edit artifacts from the Artifacts page or the artifact editor.
Related information
Workaround summary
Problem
Delivering a change set with over 45,000 items can fill the DB2 database transaction log space, and cause the delivery to fail with an SQL error. The following SQL error codes are logged in the Requirements Management (RM) server rm.log file: Error: SQLCODE=-1476, SQLSTATE=40506, SQLERRMC=-964. The default DB2 transaction log space is sufficient for change sets with 45,000 items, but log space must be increased for larger change sets.
Workaround
Complete these steps to double the size allowance for change sets:
- Stop the RM server.
- Increase the database LOGPRIMARY setting to 40.
- Increase the database LOGSECONDARY setting to 40.
- Restart the DB2 server.
- Start the RM server.
Related information
Workaround summary
Problem
When you edit artifacts in the Module editor, typing the Alt+e keyboard shortcut opens the Add Existing Artifact dialog box instead of inserting the euro sign into the rich text.
Workaround
To insert the euro sign, hold the Alt key and type 0128 on the numeric keypad.
Related information
Workaround summary
Problem
In a diagram, you can change the anchor point connections for a shape by using the keyboard. The following keyboard shortcuts are used for these actions: Ctrl+/ and Ctrl+\. A Turkish Q keyboard does not have the forward slash (/) and backslash (\) keys. Although you can create these characters by using Shift+7 and AltGr+* respectively, these key combinations do not work to change the anchor point connections.
Workaround
On a Turkish Q keyboard, use Ctrl+ö and Ctrl+ç to change anchor point connections in a diagram.
Related information
Workaround summary
Problem
In Microsoft Word, if you copy a table that has the “Repeat as header row at the top of each page” check box selected in the table properties, and then paste the table into an artifact in Rational DOORS Next Generation, the table cells are pasted incorrectly. For example, all table cells are header cells.
Table properties in Microsoft Word:
Workaround
Complete one of the following steps:
- In Microsoft Word, select only the first row of the table and apply the “Repeat as header row at the top of each page” option to that row, instead of to the whole table.
- In Rational DOORS Next Generation, after the table is pasted, edit the cell type in the cell properties to apply the correct type.
Related information
Workaround summary
Problem
If you create a new link type in a change set, you can create a link of that type in a separate change set. The system allows you to deliver only the change set that contains the link, without delivering the change set that creates the link type. If this type of delivery occurs, the configuration does not work properly because you cannot view artifact types and you cannot use the actions on the artifact pencil menu.
Workaround
Ensure that you deliver the change set that creates the link type.
Related information
Workaround summary
Problem
In version 6.0, if you attempt to create a link to or from a requirements artifact that was created in a version 3 release, and the artifact was not modified in a later release, an HTTP 400 error might occur and the link might not be created. This issue can occur for any link type.
Workaround
Complete either of these workarounds:
- Edit the primary text, save the artifact, and create the link again.
- Apply the first interim fix after version 6.0, which contains a resolution to the issue. For details, see the related work item.
Related information
Workaround summary
Problem
When configuration management is enabled in Rational DOORS Next Generation 6.0, links to artifacts in Rational DOORS 9 do not work as expected because Rational DOORS does not support configurations.
Workaround
Instead of linking, use Requirements Interchange Format (ReqIF) to transfer Rational DOORS 9 requirements into specific Rational DOORS Next Generation streams.
Related information
Workaround summary
Problem
If you installed an earlier version of the Requirements Management (RM) graphical editor add-on, you might not be able to edit graphical artifacts in version 6.0 of the RM application.
Workaround
Complete these steps to install the latest add-on in Mozilla Firefox:
- On the browser toolbar, click Tools > Add-ons.
- In the Add-ons manager, remove any extensions with names that start with RMBrowserAddOn.
- Restart the browser. The next time that you attempt to edit a graphical artifact, you are prompted to install the latest version of the add-on.
Complete these steps to install the latest add-on in Microsoft Internet Explorer:
- On the browser toolbar, click Tools > Manage add-ons.
- In the Add-ons manager, remove any extensions with names that start with RMBrowserAddOn.
- Restart the browser. The next time that you attempt to edit a graphical artifact, you are prompted to install the latest version of the add-on.
Related information
- Work Item 97455
- More information about uninstalling and reinstalling: RM browser add-on: Installation and troubleshooting guide
Workaround summary
Problem
When the version 5 licenses are uploaded, the 4.0.1 licenses are not automatically upgraded and the license assignments are not automatically preserved. If you are upgrading from a version 4 release to a version 6 release, you must first upgrade to a version 5 release (5.0.2 is recommended). After you upgrade to the version 5 release, upgrade your version 4 licenses to 5.0 by using the instructions below. Then, when you upgrade from version 5 to 6, import the 6.0 licenses and they will overwrite the 5.0 licenses with no additional steps required for the products specified.
Workaround
Complete these steps once for each type of license that you have: Token, Floating, and Authorized User.
Important: If you are upgrading from 5.0 to a later 5.0 release, this workaround is not necessary because your licenses are already upgraded.
If you have Token licenses, complete these steps:
- After you upgrade your server to 5.0 or later, import the 5.0 Analyst-Token file.
- Import one of the RDNG_v5.0_CONTRIBUTOR-Token-Term-*.jar files. Do not import both files.
Note: If you upgrade any IBM RATIONAL DOORS WEB ACCESS EDITOR or IBM RATIONAL DOORS WEB ACCESS REVIEWER licenses to Analyst, you cannot include those licenses in the number of Contributor licenses. For example, if you have 10 IBM RATIONAL DOORS WEB ACCESS EDITOR licenses and 15 IBM RATIONAL DOORS WEB ACCESS REVIEWER licenses and you then upgrade 8 of those licenses to Analyst, you are entitled to enter 17 licenses for Contributor rather than 25.
After the import of the 5.0 licenses, both the 4.0.1 and 5.0 licenses will be listed in the Client Access Types and Floating License Server areas. - Click Users > Client Access License Management.
- From the list, select one of the Analyst licenses. After you select a license, if a list of users is displayed, you selected the 4.0.1 license. If no users are listed, return to the list and select the other Analyst license.
- After a list of users is shown, click Reassign All to reassign all of the licenses to 5.0. In the Reassign All wizard, only one entry is shown for Analyst. Click it.
- From the list, select the other Analyst-Token license. All of the users that were assigned to the 4.0.1 license should now be listed under the 5.0 license.
- To upgrade the Contributor-Token license, repeat the steps 4-6 for that license.
- Return to the License Key Management page and delete the 4.0.1 Analyst and Contributor licenses.
- If you have Floating or Authorized User versions of the Analyst or Contributor licenses, complete the steps in the sections for those licenses.
If you have Floating licenses, complete these steps:
- After you upgrade your server to 5.0 or later, import the 5.0 Analyst-Floating file.
- Import one of the RDNG_v5.0_CONTRIBUTOR-*.jar files. Do not import both files. For Floating licenses, enter the total number of licenses that you were entitled to between the IBM RATIONAL DOORS WEB ACCESS EDITOR and IBM RATIONAL DOORS WEB ACCESS REVIEWER licenses.
Note: If you upgrade any IBM RATIONAL DOORS WEB ACCESS EDITOR or IBM RATIONAL DOORS WEB ACCESS REVIEWER licenses to Analyst, you cannot include those licenses in the number of Contributor licenses. For example, if you have 10 IBM RATIONAL DOORS WEB ACCESS EDITOR licenses and 15 IBM RATIONAL DOORS WEB ACCESS REVIEWER licenses and you then upgrade 8 of those licenses to Analyst, you are entitled to enter 17 licenses for Contributor rather than 25.
After the import of the 5.0 licenses, both the 4.0.1 and 5.0 licenses will be listed in the Client Access Types and Floating License Server areas. - Click Users > Client Access License Management.
- From the list, select one of the Analyst licenses. After you select a license, if a list of users is displayed, you selected the 4.0.1 license. If no users are listed, return to the list and select the other Analyst license.
- After a list of users is shown, click Reassign All to reassign all of the licenses to 5.0. In the Reassign All wizard, only one entry is shown for Analyst. Click it.
- From the list, select the other Analyst-Floating license. All of the users that were assigned to the 4.0.1 license should now be listed under the 5.0 license.
- To upgrade the Contributor-Floating license, repeat the steps 4-6 for that license.
- Return to the License Key Management page and delete the 4.0.1 Analyst and Contributor licenses.
- If you have Token or Authorized User versions of the Analyst or Contributor licenses, complete the steps in the sections for those licenses.
If you have Authorized User licenses, complete these steps:
- After you upgrade your server to 5.0 or later, import the 5.0 Analyst-Authorized file.
- Import one of the RDNG_v5.0_CONTRIBUTOR-Authorized-*.jar files. Do not import both files. For Authorized User (AU) licenses, enter the total number of licenses that you were entitled to between the IBM RATIONAL DOORS WEB ACCESS EDITOR and IBM RATIONAL DOORS WEB ACCESS REVIEWER licenses.
Note: If you upgrade any IBM RATIONAL DOORS WEB ACCESS EDITOR or IBM RATIONAL DOORS WEB ACCESS REVIEWER licenses to Analyst, you cannot include those licenses in the number of Contributor licenses. For example, if you have 10 IBM RATIONAL DOORS WEB ACCESS EDITOR licenses and 15 IBM RATIONAL DOORS WEB ACCESS REVIEWER licenses and you then upgrade 8 of those licenses to Analyst, you are entitled to enter 17 licenses for Contributor rather than 25.
After the import of the 5.0 licenses, both the 4.0.1 and 5.0 licenses will be listed in the Client Access Types area. - Click Users > Client Access License Management.
- From the list, select one of the Analyst licenses. After you select a license, if a list of users is displayed, you selected the 4.0.1 license. If no users are listed, return to the list and select the other Analyst license.
- After a list of users is shown, click Reassign All to reassign all of the licenses to 5.0. In the Reassign All wizard, only one entry is shown for Analyst. Click it.
- From the list, select the other Analyst-Authorized license. All of the users that were assigned to the 4.0.1 license should now be listed under the 5.0 license.
- To upgrade the Contributor-Authorized license, repeat the steps 4-6 for that license.
- Return to the License Key Management page and delete the 4.0.1 Analyst and Contributor licenses.
- If you have Token or Floating versions of the Analyst or Contributor licenses, complete the steps in the sections for those licenses.
Exception
If you have IBM RATIONAL DOORS WEB ACCESS EDITOR and IBM RATIONAL DOORS WEB ACCESS REVIEWER Term licenses, you must import both licenses because the number of licenses is hard coded in the Term licenses. After both licenses are imported, they will be listed and the total number of licenses between the two licenses will be available.
Related information
Workaround summary
Problem
After the Requirements Management server is upgraded to 6.0, the server might be slow or become unusable because of frequent timeouts.
Workaround
Run the appropriate statistics command to update the database tables.
Related information
- For information about the IBM DB2 database RUNSTATS command, see the IBM DB2 documentation.
- For information about the Oracle database DBMS_STATS command, see the Oracle documentation
- For information about the Microsoft SQL Server database Update Statistics command, see the Microsoft SQL Server documentation
Workaround summary
Problem
During an upgrade, you might receive the following error, which indicates a timeout issue:
CRJAZ0554I Unable to get the necessary lock in 30000 milliseconds.
Workaround
Complete one or both of the following workarounds:
- Increase the timeout value to 60 seconds. In either the Advanced Properties or the teamserver.properties file, set the following property: com.ibm.team.repository.rdb.mediator.pool.wait=60000
- Rebuild the database indexes by running the -rebuildIndices command.
Related information
Workaround summary
Problem
If multiple users update an artifact in a configuration at the same time, inconsistent versions of the artifact might be displayed in the configuration. This problem occurs because multiple versions of the artifact are internally marked as the current version. For example, you might experience the following issues:
- Different views show different versions of an artifact for the same configuration.
- An artifact cannot be found.
To detect whether a configuration has more than one current version of an artifact, run the following query. Note: The following query is for DB2. The schema name might differ for other databases: see the product documentation.
SELECT DISTINCT CONFIGURATION_ITEM_ID FROM VVCMODEL.VERSION WHERE CURRENT_COL = 1 GROUP BY CONFIGURATION_ITEM_ID, CONCEPT HAVING COUNT(CONCEPT) > 1
If the query finds more than one current version, complete the workaround; otherwise, no action is necessary.
Workaround
To repair existing instances, run the following command from the server directory of your application. Note: The following command is for Linux.
./repotools-application.sh -repairMultipleVersionsMarkedAsCurrent [credentialsFile=credentials.properties]
The utility might take a while to scan the entire database. You do not have to restart the server.
Related information
Workaround summary
Problem
In Rational DOORS Next Generation, whether a clipboard image can be pasted into an artifact is limited by how the browser processes the clipboard data.
Currently, pasting clipboard images into artifacts is only supported in Mozilla Firefox and Google Chrome. These browsers process the image data in a way that enables Rational DOORS Next Generation to create an uploaded image artifact for the pasted data. Pasting images in Mozilla Firefox is supported for Rational DOORS Next Generation 4.0.1 and later. Pasting images in Google Chrome is supported for Rational DOORS Next Generation 5.0 and later.
The ability to paste images is also limited by the external application from which the image is being copied. The external application must put the copied image data onto the system clipboard in a way that enables the browser to process the data.
Workaround
To paste a clipboard image into an artifact in Microsoft Internet Explorer and Safari browsers, you must upload the image as an artifact and paste it into the field by using the Insert Image menu option.
Related information
Workaround summary
Problem
If you import a module into a change set by using ReqIF, discard the change set, and then import the same module into another change set in the same project, the delivery wizard reports a problem when you attempt to deliver the change set by using the Standard delivery option. The delivery fails because a problem is found with the module in the change set, although it appears fine in the interface.
Workaround
Select the Express delivery option.
Related information
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Workaround summary
Limitations
Limitation summary
Problem
In a change set, you can remove an artifact from a module and also delete the core artifact from the project. When you deliver that change set, if someone has modified the same module, a conflict is created. You can resolve the conflict by not delivering your change to the module, but you can still deliver your change to remove the artifact from the project. If this situation occurs, the module contains a row that points to a nonexistent artifact, and you cannot delete the row. To avoid this scenario, ensure that you resolve any conflicts with the module before you deliver a change to remove an artifact from the project.
Related information
Limitation summary
Problem
Occasionally, if you encounter a conflict between modules and resolve the conflict by selecting the target version, the choice is incorrectly conveyed to the server and the conflict resolves to the source version instead. If this situation occurs, the original changes are lost and you must make them again.
Related information
Limitation summary
Problem
This issue only affects projects that do not have configuration management capabilities enabled. When you work with projects in Rational DOORS Next Generation, you encounter several selection dialog boxes that list projects. These dialog boxes should list only the projects that you have read access to. However, all the projects on the server that are not enabled for configuration management are displayed. You cannot access all the projects, but you can see them.
Related information
Limitation summary
Problem
If you use the Quick Search feature to search for artifacts that contain a specific string, the search results do not correctly include artifacts that have a format of Diagram. Search strings that are part of the first or last word of a plain text label or search strings that are part of a rich text label are not found.
Related information
Limitation summary
Problem
In Rational DOORS Next Generation 6.0, the Data Collection Component might take longer to run because the extract, transform, and load (ETL) process and the queries that identify artifact links are slower than in previous releases.
Related information
Limitation summary
Problem
In the Requirements Management (RM) application, if you add widgets to a project dashboard or a personal dashboard, you cannot set the widget to display data from a particular stream or baseline. On a project dashboard, some widgets, such as for recent comments and recent artifacts, display information from the current configuration that is displayed on the banner at the top of the window. On a personal dashboard, all widgets display information from the default stream.
Related information
Limitation summary
Problem
If you view PDF documents by using Microsoft Internet Explorer, menus or controls might be hidden behind the PDF document. This behavior is a defect with the PDF ActiveX Viewer in Internet Explorer. More information is available in this Microsoft discussion thread: PDF is showing always on top of all controls.
In most cases, you can navigate away from the page that shows the PDF document. However, if this issue causes severe problems, you can remove the PDF ActiveX Viewer from Internet Explorer. Rational DOORS Next Generation can display PDF documents without the PDF ActiveX Viewer by using the Embedded Documents feature (where supported).
Related information
Limitation summary
Problem
In Rational DOORS Next Generation 6.0, module baselines were replaced with project baselines. If you upgrade to version 6.0 from any version 5 release, existing module baselines are converted to project baselines. The contents are not lost and can be accessed by switching the current configuration to the relevant project baseline. Note that in the version 5 releases, you could copy a module baseline to create a new editable module, which is not possible with project baselines. However, instead of copying from a module baseline, you can now branch from a project baseline.
Related information
Limitation summary
Problem
In Rational DOORS Next Generation 6.0, the audit history for modules is recorded, but is not displayed. If you need to view the audit history for modules, do not upgrade to version 6.0. The reinstatement of a viewable audit history for modules is currently planned for a future release.
Related information
Limitation summary
Problem
Before the 6.0 release, the Revision history feature showed icons across the timeline that represented both the revisions of an artifact and any project baselines that were captured with that artifact. Currently, the baseline icons are not shown. The revision icons remain and enable you to reach any of the revisions of the artifact.
Limitation summary
Problem
The ReqIF import feature does not support importing the same data item into multiple configurations (streams and change sets) of a single project or project component.
This means that a ReqIF package should not be imported into more than one configuration of a project. It also means that different ReqIF packages that contain the same artifact should not be imported into more than one configuration of the same project.
For example, a module should not be imported into the initial stream of a project and also into a child stream of that project. Similarly, a module should not be imported into two separate change sets in the same project.
The ReqIF feature maintains metadata on all data items that it encounters and the metadata is scoped to a single project (or project component): this metadata is not user-visible. Data items that are handled by ReqIF have a unique identity that is known to the feature and maintained by the application. This identity is used during ReqIF import operations to indicate the lifecycle of a data item and to manage appropriate actions for that an item during the import process.
Both ReqIF and the configuration management capabilities manage changes to data, but are intended for different scenarios and work in different ways. The configuration management capabilities are intended for data changes within projects, while ReqIF is intended for exchanging data between projects and between data repositories. The ReqIF specification does not include the concept of configurations, and the interoperation of these features is not recommended.
Related information
Limitation summary
Limitation summary
Limitation summary
Limitation summary
© Copyright IBM Corporation 2015, 2017
Yes