Library > Articles >

Workarounds and Limitations: Known issues in IBM Engineering Requirements Management DOORS Next 7.0

The following known problems are related to this release.

Workarounds

The following problems in this release have workarounds:

Limitations

The following problems in this release do not currently have workarounds:

Workarounds

Views might timeout when using Link validity in global configuration


First occurrence
7.0

Problem
When you enable link validity in the component properties, views that display link columns can timeout when working in the context of a global configuration. This issue is more likely to happen when there are a large number of component contributions to the global configuration.

Workaround
You must disable link validity for the component or remove the link columns in any views that timeout. You can also refresh the view to resolve the timeout issue.
Complete these steps to disable link validity:
  1. Click Manage Component Properties from the Administration menu.
  2. Select the Link Validity tab.
  3. Clear the Show link validity check box and click Save.
Related information
Work Item 133184

Back to top

Complex link-related views might timeout when using Db2


First occurrence
7.0

Problem
Views that display link columns can timeout on Db2 databases due to a long initial execution time of the underlying relational database query. This behavior is observed when working in the context of a global configuration.

A large Db2 statement heap causes the Db2 optimizer to take a long time to compute an optimal query execution plan for these types of queries or views.

Workaround
Complete one of the following workarounds to reduce the statement heap size:
  • View the current statement heap size by executing the db2 get db cfg for <db alias> command.
  • Change the statement heap size to the recommended value by executing the db2 update db cfg for <db alias> using STMTHEAP 8192 AUTOMATIC command.
<db alias> is the RM database name specified in the teamserver.properties entry for com.ibm.team.repository.db.jdbc.location.

Related information
Work Item 133757
Db2 documentation: stmtheap – Statement heap size configuration parameter

Back to top

Missing embedded video in the translated versions of a DOORS Next 7.0 topic


First occurrence
7.0

Problem
Embedded video is not displayed in the translated versions of the following topic for DOORS Next 7.0 documentation on IBM Knowledge Center:
Engineering Requirements Management DOORS Next overview

Workaround
To view the video, change the language by selecting English from the list at the lower right of the KC page.

Related information
Work Item 496011

Back to top

Download button is disabled when downloading a ReqIF file from a baseline


First occurrence
7.0

Problem
If you create and export a ReqIF file from a definition in a baseline, the export function appears to successful but the Download button is disabled and the ReqIF file cannot be downloaded. In version 7.0, the ReqIF metadata is a part of the baseline and cannot be amended.

Workaround
To resolve this issue, download the existing ReqIF file that is created before the baseline is created. Create a ReqIF file from the definitions that you want to be available in the baseline immediately before you create the baseline. In a configuration management enabled project, you can create a stream from the baseline, and then create the new ReqIF file from the definition in that stream.

Complete these steps:
  1. Open the Stream Editor by selecting the Baseline link in the Configuration menu.
  2. Click Create Stream to create a stream from the baseline.
  3. Navigate to the stream and select the ReqIF Component Properties tab.
  4. Click Export. The ReqIF file is available for download when you select the Download button.
Related information
Work Item 135212

Back to top

Link to a module binding in another project created in global configuration does not show up in local configuration


First occurrence
7.0

Problem
If you create a link from one CM-enabled project or component to an artifact in another CM-enabled project or component in a global configuration context and switch to a local configuration, the link still appears as broken. This is an expected behavior.
However, when you create a link to module binding between projects or components and then switch to a local configuration, the link does not show up at all.

Workaround
To view the link, use one of the following options:

Option 1
Switch back to the corresponding global configuration and the link reappears.
Complete these steps:
  1. In the configuration menu, click Switch. The Select the Configuration Context window appears.
  2. Select Global Configuration.
  3. Select the appropriate global configuration and click OK.
Option 2
Search the link on the links sidebar.
Complete these steps:
  1. Open the artifact, which is the source of the link.
  2. Expand the links sidebar.
  3. Examine existing links.
Related information

Work Item 132724

Back to top

Cross-server links in different domains cannot be created by dragging and dropping in Microsoft Internet Explorer 11


First occurrence
6.0.6

Problem
Creating links across servers in different domains by dragging and dropping does not work in Microsoft Internet Explorer 11.

Workaround
Use the Create Link dialog box instead, or use a different browser.

Related information
Work Item 122211

Back to top

Cross-server link target titles are not shown on the Changed Resources tab and in the Audit History view


First occurrence
6.0.6

Problem
When you view cross-server links on the Changed Resources tab or in the Audit History view, the titles of the targets are not shown.

Workaround
To see the title, navigate to the target of the link.

Related information
Work Item 122042

Back to top

Diagram shapes are not highlighted for incoming cross-server links


First occurrence
6.0.6

Problem
When you click links in the Links section of a diagram, the related linked shape is highlighted. This function does not work for incoming cross-server links.

Workaround
To link to diagram shapes, use outgoing cross-server links.

Related information
Work Item 122187

Back to top

Cross-server linking cannot identify link type URIs on other servers


First occurrence
6.0.6

Problem
When you create a cross-server link, any local link types that can be used for cross-server linking are available. Currently, the client cannot identify which link type URIs are available on other servers, which means that you can create a link that does not have a matching URI on the other server and cannot be seen on that server until you create the matching URI.

Workaround
Ensure that all link types with URIs have a matching URI for all cross-server components.

Related information
Work Item 122041

Back to top

You can't import requirements if their embedded resources are on a different server

First occurrence
6.0.6

Problem
For security reasons, you can't export requirements if they have embedded resources from a different server. You can export only the embedded resources that are on the local system, such as sketches, storyboards, or diagrams.
 
Workaround
To export requirements with embedded resources, create the embedded elements on the local system before you export them.
When you import requirements with embedded resources that are on a different server, the embedded elements resolve only if the user is logged in to the server that contains the embedded resources.

Related information
Work Item 130034

Back to top

Graphical artifact converter application is discontinued and causes error CRRRW8011E


First occurrence
6.0.6

Problem
The Rational DOORS Next Generation (now known as Engineering Requirements Management DOORS Next) graphical artifact converter is discontinued in the 6.0.6 release. The converter application generates images to display graphical artifacts that were created with the deprecated graphical artifact editor browser add-on.

When you attempt to view these graphical artifacts, including the graphical artifacts in the JKE Banking sample template package, this error is displayed:
ID CRRRW8011E The converter application could not be reached.

The rm.log file also contains this message: The converter is disabled. Please contact support to enable it.

Workaround
If you require the graphical artifact converter application, contact IBM Software Support for steps to enable it.

Related information
Rational DOORS Next Generation 6.0.4 – Graphical Artifacts Migration Utility
Rational DOORS Next Generation Support Community

Back to top

An error is displayed when you view graphical artifacts on WebSphere Application Server


First occurrence
6.0.5

Problem
If you use WebSphere Application Server and attempt to view graphical artifacts by using the Rational DOORS Next Generation (now known as Engineering Requirements Management DOORS Next) graphical artifact converter application, the following error message might be displayed:

CRRRW8010E The content that you requested could not be generated. The converter application encountered an error that prevented the graphical content from being created or retrieved. This is usually caused by a configuration error for the converter application. It may have missing dependencies or was not started correctly. Ask your administrator to verify the converter application was correctly installed and configured.

If you view the converter diagnostics page at https://<converter_server_name>:<converter_server_port>/converter/htmlgen and any tests do not pass, this error is likely a result of a common configuration error. However, if all the tests on the diagnostics page pass, the following workaround might resolve the issue.

Workaround
On WebSphere Application Server, add the InvalidateOnUnauthorizedSessionRequestException session management custom property:
  1. Navigate to Servers > Server Types > WebSphere application servers.
  2. Click the name of the server that contains the converter application and, in the Container Settings section, click Session management.
  3. In the Additional Properties section, click Custom properties.
  4. Click New and enter the following information:
    Name: InvalidateOnUnauthorizedSessionRequestException
    Value: true
  5. Click Apply and save directly to the master configuration.
Related information
Work Item 123130
Work Item 117607
Requirements Management (RM) Converter application configuration and troubleshooting guide

Back to top

Filtering large numbers of artifacts across CLM products might be slow or time out


First occurrence
6.0.5

Problem
If you filter data that involves other CLM products and that includes a large number of artifacts, the query might be slow or time out. This issue is more likely to happen when a large number of artifacts is filtered to a very small result set, such as fewer than 25 rows.

Workaround
If the filter times out, first increase the grid view Rows Per Page setting:

1. From the grid's Configure Page Settings drop-down menu, select the first item: Show 25 Rows Per Page.
2. Change this value to 200 rows.

If you still experience timeouts, increase the query timeout setting:

1. Open /rm/admin and select Advanced Properties in the left sidebar.
2. Locate the query.client.timeout setting and increase it to 2 minutes.

Related information
Work Item 114596 

Back to top

Delivering a large number of change sets might take a long time


First occurrence
6.0.4

Problem
When you deliver a very large number of change sets (typically over 100,000), the client can take a long time to marshal the selected change sets. This delay occurs after the first step in the wizard, when you select the change sets to deliver.

Workaround
Deliver the change sets between streams in smaller sets.

Related information
Work Item 113080

Back to top

Japanese or simplified Chinese characters are displayed incorrectly in PDF documents


First occurrence
6.0.3

Problem
If you view a PDF document in Rational DOORS Next Generation (now know as Engineering Requirements Management DOORS Next), the browser incorrectly displays Japanese or simplified Chinese characters as blank squares. This issue occurs with some versions of Mozilla Firefox and Microsoft Internet Explorer, and might occur with other browsers.

Workaround
  • Ensure that Adobe Acrobat Reader is installed and that the appropriate browser plug-in is configured (such as the Adobe PDF Plug-in for Firefox, or ActiveX for Internet Explorer).
  • Use the 32-bit edition of Firefox; the 64-bit edition does not support the Adobe PDF Plug-in.
Related information
Work Item 107842

Back to top

Copying and pasting cells from Microsoft Excel does not retain cell borders


First occurrence
6.0.2

Problem
When you copy bordered cells from Microsoft Excel, the borders are lost when you paste the cells into the rich-text editor.

Workaround
Complete these steps:
  1. Open the context menu for the pasted Excel data.
  2. Click Table Properties and set the Border Size attribute to 1.
Related information
Work Item 122015

Back to top

Comments widget on a personal dashboard displays an incorrect label for the Configuration setting


First occurrence
6.0.1

Problem
If a personal dashboard is migrated from version 6.0 or an earlier release to version 6.0.1 or later, and it contains a Comments widget for a project that is enabled for configuration management, the label for the Configuration setting is displayed as $viewlet.prefs.configuration instead of Configuration.

Workaround
Delete the Comments widget from the personal dashboard and then add it again.

Related information
Work Item 100741

Back to top

Page Up and Page Down keys do not work properly when you edit an artifact in Mozilla Firefox

First occurrence

6.0.1

Problem

In Mozilla Firefox, when you inline edit artifact content in a module, the Page Up and Page Down keys do not work.  When you edit artifact content in the full text editor, Page Up will page to the top of the document and Page Down will page to the bottom of the document.

Workaround

Use these techniques to move the cursor:

  • Use the Up Arrow and Down Arrow keys to move up or down.

  • While in-line editing, press Ctrl+Home and Ctrl+End to move to the beginning or end of the text.

Related information

Work Item 120350

Back to top

During the CSV import process, artifacts that were partially removed cannot be reinserted into a module


First occurrence
6.0.1

Problem
When you import CSV files, you cannot reinsert an artifact into a module if the artifact was partially removed; that is, the base artifact reference still exists in the project. The import process is only intended for creating new entries or for updating attributes for an artifact that is already part of the module.

Workaround
To reinsert an artifact into a module, use the artifact grid in the web client.

Related information
Work Item 118894

Back to top

Errors are displayed during TRS rebase operations if timeouts occur


First occurrence
6.0.1

Problem
If you perform a Tracked Resource Set (TRS) 1.0 or TRS 2.0 rebase operation on a large Rational DOORS Next Generation (now known as Engineering Requirements Management DOORS Next) repository, you might receive an error stating that the rebase operation could not be completed successfully. The error does not always mean that the rebase operation failed. In some cases, the error is caused by a timeout.

Workaround
To examine the actual status of a rebase operation, go to the TRS management page, scroll to the Tracked Resource Sets Status section, and click Status Refresh to update the status of the operation.

Related information
Work Item 101420
Work Item 100622
Work Item 111679

Back to top

Error message is displayed when delivering large change sets


First occurrence
6.0.1

Problem
When you deliver a module containing large number of artifacts (approximately 20000) to a parent stream, the web browser is unable to handle the module structure and a generic error message is displayed.

Workaround

Use the Express delivery option to deliver the change sets.


Related information
Work Item 131113

Back to top

Links between artifacts in Rational DOORS 9 and Rational DOORS Next Generation do not work as expected when configuration management is enabled


First occurrence
6.0

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
Work Item 97418
Considerations for enabling configuration management

Back to top

Large change set deliveries on Db2 databases might fail with an SQL error


First occurrence
6.0

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:
  1. Stop the RM server.
  2. Increase the database LOGPRIMARY setting to 40.
  3. Increase the database LOGSECONDARY setting to 40.
  4. Restart the DB2 server.
  5. Start the RM server.
Related information
Work Item 343765 
Work Item 94922

Back to top

In some browsers, images cannot be pasted from the clipboard into an artifact


First occurrence
6.0

Problem
In Rational DOORS Next Generation (now known as Engineering Requirements Management DOORS Next), 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, Google Chrome and Chromium Edge. 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. Pasting images in Chromium Edge is supported for Rational DOORS Next Generation 7.0.1 and later.
Microsoft Internet Explorer is not supported in Rational DOORS Next Generation 7.0.1 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
Work Item 91314
Work Item 99618
Work Item 69411
Work Item 84016

Back to top

The Alt+e keyboard shortcut does not insert the euro sign in the Module editor


First occurrence
6.0

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
Work Item 95144

Back to top

During an upgrade, the CRJAZ0554I timeout error might occur


First occurrence
6.0

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
Work Item 404381
Repository tools command to rebuild database indexes

Back to top

Importing large or complex word documents might take a long time


First occurrence
4.0.5

Problem
When you import large or complex Word documents, the import process might take a long time. The resulting folder or module might load slowly and be difficult to navigate. This happens because of the size and complexity that is involved in handling the Word documents. DOORS Next processes just a single Word import operation at a time to prevent concurrent imports from compromising server stability by consuming too much memory or processing time. If an import request takes a long time, other import operations get blocked. This is a limitation based on the design of the product. This is applicable for both import wizards: Import requirements from within a text document and Import a text document and convert to a rich text artifact.

Importing a Word document into a folder or module as multiple artifacts by using the Import requirements from within a text document wizard might take longer and consume more resources. Also, importing a Word document as a single rich text artifact might also be affected due to large and complex documents. For example, if the document is large and complex, the result of the import might be difficult to view and edit in the rich text editor.

Workaround
To reduce the import time, use one of the following options:

Option 1
Split the Word document that produces more than 10,000 artifacts into multiple documents before saving the results. The resulting module or folder should not contain more than 10,000 artifacts. Otherwise, the import might take more time, and the pages might load more slowly when browsing the module or folder. Each non-empty paragraph creates at least one artifact. If you use delimiters and keywords, the paragraphs might create more artifacts. In that case, you can split the document more. OLE objects, shapes, and other graphical content can also have an impact on the import time. You can split the documents that contain such content to reduce the import time. Before saving the results, preview the results to confirm that the number of artifacts that will be created is not too large.

Option 2
If your document has a large number of section breaks, the import time might take longer. It is advised to split the document into further chunks before the import. Alternately, you can also enable an admin property to merge all the document sections in one section. When the documents are merged, the headers and footers of only the first section are used and remaining headers and footers are lost. To merge the content in the document into the first section, complete these steps:
  1. Navigate to Advanced Properties under the Configuration section.
  2. Search the WordImport.MergeSections property.
  3. Set the property value as true and click Save.
  4. If a Word document with a large number of section breaks is being processed, you might need to restart the server.
Note: This option affects all word import operations.

Related information
Rational DOORS Next Generation: Organizing requirements for best performance
7.0 performance: IBM Enterprise Requirements Management DOORS Next
Work Item 134130

Back to top

Limitations

Link validity decorations are not displayed in an artifact grid for references links


First occurrence
7.0

Problem
Link validity decorations are not displayed in an artifact grid of a baseline for references links. This happens as there is no global configuration in which to fetch artifacts at the other end of the link.

Related information
Work Item 128579

Back to top

Requirements with public tags show additional audit history entries


First occurrence
7.0

Problem
The requirements audit history shows addition and removal of public tags. After you upgrade to version 7.0, additional audit history entries with label 'saved with no changes' are also present.

Related information
Work Item 133337

Back to top

Publish API with history option is not supported for modules


First occurrence
7.0

Problem
The Publish API supports an option for retrieving the audit history of an artifact. This option is not working for modules.

For usage of this feature, see the following example:
https://hostname.com:9443/rdm/publish/resources?resourceURI=https://hostname.com:9443/rdm/resources/MD_HKLOcB0SEeqPz4pWvbDtbw&history=true

If you attempt to use this feature, you might receive incorrect and incomplete history data for that module. This issue occurs because the feature is not implemented for the 7.0 release.

Related information
Work Item 133618

Back to top

The main TRS validation does not process selections content


First occurrence
7.0

Problem
TRS validation cannot process selections content currently. The selection validation and repair are not integrated with the TRS validation and repair feature, which are shown in the admin UI. This means that the main TRS validation feature does not check and repair the configuration mappings information.

Related information
Work Item 143198

Back to top

OSLC query for requirement collection does not include views


First occurrence
7.0

Problem
When you run an OSLC query for requirement collections, the query result does not include any views that are present in the collections.
For example, if you run a query string containing oslc.where=rdf:type="<http://open-services.net/ns/rm#RequirementCollection>", no views are shown in the result.

Related information
Work Item 129633

Back to top

Server timeout error occurs when performing the quick search operation on projects or components

 
First occurrence
7.0

Problem
If you configure the RM server by using the Derby database and perform a quick search operation on all project areas for non-configuration enabled project or all components for configuration enabled project areas, server timeout error occurs. The following error message is displayed:
SyntaxError: Unexpected end of JSON input

Related information
Work Item 133519

Back to top

Cross-project linking between module bindings in non-configuration enabled project baselines are not visible


First occurrence
7.0

Problem
In a non-configuration enabled project baseline, the artifacts at the other end of cross-project links are not visible. This happens as there is no global configuration context in which to find the artifacts.

Related information
Work Item 128472
Work Item 128611

Back to top

System-generated change sets are not included as module dependencies in migrated data


First occurrence
7.0

Problem
In version 7.0, all prior changes to a module will be included as dependencies when delivering a change set with edits to that module. However, system-generated change sets that have been migrated from previous releases will not be included as dependencies, if those change sets contain only structural modifications.


Related information
Work item 131094

Back to top

Data purge functionality is not supported in version 7.0


First occurrence
7.0

Problem
In version 7.0, the existing data purge functionality is no longer supported. The data.purge.enabled property is still available under the Advanced Property section but the property value will have no effect on the delete operation. You cannot view the Delete From Repository tab in the Project Properties of the application.
The data purge functionality is intended to be reintroduced in a later release.

Related information
Rational DOORS Next Generation 6.0.2: Delete from Repository feature

Back to top

Link validity summary is not visible for baselines for DM or RM links


First occurrence
7.0

Problem
When you use link validity in non-configuration enabled project and in DOORS Next baseline, work items or resources that are stored in other applications are not visible to the DOORS Next baseline.

Related information
Work Item 128567

Back to top

For Configuration Management enabled project areas, install ELM 7.0 iFix001 before upgrading to the next version


First occurrence
7.0

Problem
If you enable Configuration Management in a project area and run the upgrade script, the upgrade process might leave some data in an incorrect state leading to unexpected changes in the requirements. Install ELM 7.0 iFix001 on version 7.0 in the RM database before running the rm_upgrade script.

Related information
Work Item 130288

Back to top

Importing ReqIF files creates fewer history entries


First occurrence
7.0

Problem
When you import Requirements Interchange Format (ReqIF) files, fewer history entries are created. Adding resources and assigning those resources to a folder during ReqIF import will not create new history records, when those resources are added through module processing. The reason for this behavior is that module creation is now recorded as a single operation that takes care of resource creation and adding artifacts to a folder in bulk.

Workaround
To view the artifact count, use one of the following options:
  • Examine the ReqIF import report.
  • If you are using configuration management and importing artifacts in to a change set or child stream, use the delivery compare window to view the created artifacts count.
Related information
Work Item 133242

Back to top

Audit history related to deleted comments is missing or incorrect after upgrading to the version 7.0


First occurrence
7.0

Problem
If an artifact has comments, which were deleted in version 6.x, some entries in the audit history might be missing after you upgrade the repository to the version 7.0. The audit history shows that the comment was deleted, but it might not show a comment change before the delete.

Related information
Work Item 133992

Back to top

Link validity returning to a previous state maintains validity assertions for RM but not for other applications


First occurrence
7.0

Problem
In a global configuration enabled project, if you enable link validity between artifacts in two RM projects and assert the validity, any change between the artifacts changes the validity state to suspect. If you undo the change, link validity assertions of previous state are maintained. This is because the state of an artifact in DOORS Next is based on its content.

If you use global configuration and enable link validity between an artifact in RM and a test case in QM and change the title of the test case, link validity state changes. If you undo the changes, the test case reverts to a previous state and the validity assertions are not maintained as the validity here is based on the etag, which changes with each edit regardless of the content.

Related information
Work Item 128592

Back to top

Team Area members that have a role with baseline creation permission does not have 'Create Baseline' option enabled

 
First occurrence
7.0
 
Problem
A member of a Team Area that has a role with the permissions to 'Manage Baselines' enabled, and is not a member of the Project Area that does not have the 'Create Baseline' option available. To avoid any confusion, CM related permissions related to stream, baseline, and change set should not be inherited into team area permissions.
 
Related information

Back to top

Known issues in translated versions of ELM 7.0 documentation


First occurrence
7.0

Problem
  1. The table of contents for ELM 7.0 documentation on IBM Knowledge Center might display long navigation titles in place of short titles for content in languages other than English.
  2. The pre-release header is visible on the translated pages of ELM documentation on IBM KC.

Related information
Work item 496011

Back to top

Incoming cross-server links are not created for imported files


First occurrence
6.0.6

Problem
When you import a file, any incoming cross-server links are not created.

Related information
Work Item 122406

Back to top

Cross-server links cannot be created between basic artifacts and modules or collections


First occurrence
6.0.6

Problem
You cannot create a cross-server link from an artifact that is not a module or collection to a module or collection. A cross-server link to a module or collection must be from another module or collection.

Related information
Work Item 121956

Back to top

Content that is saved as a file cannot be exported to and imported from CSV and Microsoft Excel files


First occurrence
6.0.6

Problem
If you try to export content that is saved as a file, such as a PDF file, to a CSV or Microsoft Excel file, the exported file contains an empty row that specifies the artifact is there, but has no content because that format is not supported. Because the content is not exported correctly, it cannot be imported from the CSV or Microsoft Excel file either.

Related information
Work Item 121295

Back to top

No message is displayed when you try to create incoming cross-server links that already exist


First occurrence
6.0.6

Problem
If you try to create an incoming cross-server link that already exists, the action fails but no explanation is provided.

Related information
Work Item 122204

Back to top

Configuration Administrator role is displayed instead of Configuration Lead role in configuration management enabled project areas


First occurrence
6.0.6

Problem
After you upgrade DOORS Next and try to add members in configuration management enabled project areas, the Configuration Administrator role is displayed instead of the Configuration Lead role. This is likely to happen because of the upgrade process.

Related information
Work item 120836

Back to top

Browser zoom in/out support


First occurrence
6.0.6

Problem
You can set the zoom level of the browser by using the zoom in and zoom out feature. Adjusting the zoom level out will generally work, but in some instances the page's layout might not be maintained properly. Adjusting the zoom level in is supported to 200%.

Related information

Work Item 129853

Back to top

In distributed topologies, authentication times out if single sign-on is not used


First occurrence
6.0.6

Problem:
If you complete any of the following actions in distributed topologies where single sign-on is not used, the link discovery process cannot fetch OSLC links from the associated project areas:
  • Export process where views contain OSLC links
  • View Artifact or Module Grid views that contain OSLC links
  • Generate reports that contain OSLC links
This happens because authentication is lost in the associated OSLC project areas after some time (approximately after 2 hours) and affects all DOORS Next versions. A warning message appears in the Links side bar section and notifies you to authenticate in specific project areas.

Workaround
You must revalidate the session by refreshing the page in every associated project. For example, if you cannot view a link between Rhapsody Model Manager (RMM) and DOORS Next, you must log in to both project areas. To avoid this issue, use some form of single sign-on mechanism for the associated project areas.

Related Information:
Work Item 132148
Work Item 494265
Single sign-on authentication in ELM
Configuring authentication session timeout

Back to top

Java 8 SR5 Fix Pack 5 through Fix Pack 10 is not supported as the runtime for CE/CLM applications on a Windows platform


First occurrence
6.0.5

Problem
Continuous Engineering (CE) and Collaborative Lifecycle Management (CLM) applications on a Windows platform that run on Java 8 SR5 Fix Pack 5 through Fix Pack 10 encounter null pointer exceptions and might not be usable. Use Java 8 SR5 Fix Pack 11 (8.0.5.11) or later as the runtime.

Related information
Work Item 455371
Work Item 452307
APAR IJ04429

Back to top

Embedded images, artifacts, and content is not visible if it is imported into a project or component where it does not exist


First occurrence
6.0.5

Problem
If you try to import embedded artifacts, images, and content that is not part of the configuration for the project or component where the import process is being executed, those items are not visible in the current configuration, and the following message is displayed: The resource for this embedded image no longer exists or is not visible in the given configuration.

Related information
Work Item 121294

Back to top

Artifacts with only review comments are not included when you sort the Comments column


First occurrence
6.0.4

Problem
This behavior occurs only in projects that are not enabled for configuration management. When you sort the Comments column to display artifacts with comments, artifacts that have only review comments are not sorted in the correct order. Only comments other than review comments are sorted as expected.

Related information
Work Item 112750

Back to top

The Review Comments column is not displayed in printed module reports


First occurrence
6.0.4

Problem
If you create a report for a module in a table format and the report includes the Review Comments column, that column is not displayed when you print the module report. The column is excluded because the printed version does not show the correct information.

Related Information
Work item 112553
Work item 112691

Back to top

Exporting modules into CSV or Microsoft Excel files only exports module artifacts


First occurrence
6.0.4

Problem
When you export modules from a module view or from only a module structure, the export process does not include base artifact information. In the context of a module, the export options are intended only for module artifacts or bindings.

To export artifact information into a CSV or Microsoft Excel file, you must export directly from a folder where the target is located.

Related information
Work Item 116896

Back to top

The PDF viewer is still usable when the “Upload file” dialog box is active in Microsoft Internet Explorer


First occurrence
6.0.3

Problem
In all supported versions of Microsoft Internet Explorer 10 and 11, if you upload a new version of a PDF artifact, the “Upload file” dialog box opens, but you can continue to perform actions in the PDF viewer, such as scrolling, selecting text, or changing the zoom value.

Related information
Work Item 105021

Back to top

Symbols or special characters are not displayed in reports


First occurrence
6.0.2

Problem
When you create reports for rich text artifacts that include symbols or special characters, the symbols or special characters might not be displayed in the report if the reporting font does not support them.

Related information
Work Item 101931

Back to top

Microsoft Visio VDX and VSDX file formats have limited or no support for uploaded file previews


First occurrence
6.0.1

Problem
The Microsoft Visio file formats that are XML-based, such as VDX and VSDX, lack support for uploaded file previews. For example, the VDX format has no support for file previews. A possible workaround is to convert the file to a different, older Visio format such as VSD. VSDX files have limited support for file previews; they cannot be rendered as thumbnail images. This means that a preview is not available when embedding the file as an artifact, when performing rich hover, when viewing it in a module, or from reports on that artifact. The only support for VSDX files is for viewing the artifact in full-screen mode or directly opening the artifact in Microsoft Internet Explorer with the Visio plug-in installed.

Note: Starting with the version 7.0.1, support for Microsoft Internet Explorer is removed. As a result, the Microsoft Visio file formats that are XML-based, such as VDX and VSDX, lack support for uploaded file previews. For example, the VSDX format has no support for file previews. A possible workaround is to convert the file to an older Visio file format such as VSD. The Microsoft Visio Compatibility Pack provides a command-line tool that can be used for conversion.

Related information
Work Item 97340
Work Item 98831
Work Item 136372
Save a Visio file in the older .vsd format
Microsoft Visio Compatibility Pack

Back to top

Quick Search results do not correctly include artifacts that have a format of Diagram


First occurrence
6.0

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
Work Item 90550

Back to top

Module baselines were replaced with project baselines


First occurrence
6.0

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
Work Item 97312
Work Item 97420

Back to top

Anchor point connections cannot be changed by using keyboard shortcuts on a Turkish Q keyboard


First occurrence
6.0

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
Work Item 96740

Back to top

A module template's duplication policy is shared across its templates


First occurrence
5.0

Problem
If you create multiple templates on the same module with a different duplication policy, the duplication policy of all of the module’s templates will be changed to the duplication policy of the last template that you created or modified for that module. This is because the duplication policy is stored as a property of the module and not the module template.

Related information
Work Item 71064     

Back to top

The number of tags for a project is no longer visible


First occurrence
4.0.4

Problem
In version 4.0.3 and earlier, you can enable a feature that shows the number of tags for a project. To enable the feature, you set this property: com.ibm.rdm.fronting.server.RDMTagCountEnabled=true. When the feature is enabled, you can see how many times a tag is used by hovering over the tag. You can also sort tags by number of uses. As of version 4.0.4, the feature is no longer available.

Related information
Work Item 75304
Work Item 84919

Back to top

Text searches do not support queries that include certain characters


First occurrence
4.0.2

Problem
When you search for text by using a quick search, full-text search, or term lookup operation, the search results might be inconsistent if the query includes one of the following characters:
( ) { } [ ] « » / : ; * ? ! _ – ” < > | & . , ‘ “

This limitation is caused by the way that the Jazz Team Server search facility handles special characters.

Related information
Work Item 60581
Work Item 65502
Work Item 41905

Back to top

Changes in an artifact type in DOORS Next are not reflected in Reporting REST API


First occurrence
RRC 3.0.1

Problem
If you change an artifact type such as, create or modify an artifact type in DOORS Next, the changes are not immediately reflected in the reporting REST API. The changes are reflected only after an instance of that type is created or modified after the type was changed.

If you delete an artifact type, which means there are no instances of the artifact type in DOORS Next, that change is also not reflected in the REST API.

Related Information
Work Item 127238

Back to top

© Copyright IBM Corporation 2022

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Feedback
Was this information helpful? Yes No 0 people rated this as helpful.