Jazz Library Workarounds: Rich Client problems in DOORS Next Generation 4.0.1
Author name

Workarounds: Rich Client problems in DOORS Next Generation 4.0.1

Follow this link for Rational Requirements Composer 4.0.1 or DOORS Next 4.0.1 Web Client and Server workaround articles

The table of contents lists the known problems, workarounds, and limitations related to the Rich Client functionality in the DOORS Next Generation 4.0.1 release.

Workarounds

Use the links below to learn more about the issues and workarounds in this release:

Limitations

Use the links below to learn more about the limitations (an issue, without a workaround) in this release:


Problem Summary

In the rich client, users can modify links to other CLM applications even if they do not have the required permissions

Problem

Before users can modify links to other applications of the Rational solution for Collaborative Lifecycle Management (CLM), the users must have the “Modify CLM Link” project configuration permission. However, in the rich client, users can modify links to other applications even if they do not have that permission.

Workaround

To restrict who can modify the links, use the web client because it enforces the “Modify CLM Link” permission.

Return to the top of the page

Problem Summary

In the rich client, traceability attributes are lost when you edit the associated view

Problem

In a module view with columns that show the traceability attributes from linked-to artifacts, if you edit that view in the rich client, the columns will no longer display the traceability attributes. If you save the view, the change becomes permanent. This problem occurs because when the view is edited, the part of the view definition that specifies which traceability attributes to show is lost.

Workaround

Repair the view definition in the web client:

  • 1. Open the web client.
  • 2. Open a module that is associated with the view definition.
  • 3. Open the view definition.
  • 4. Add the traceability attributes that are missing.
  • 5. Save the view.

Related Information

The following links point to related information:

Return to the top of the page


Limitation Summary

In DOORS 9.5, some of the links created between the DOORS artifacts and the Requirements Management (RM) artifacts are not shown in the traceability reports.

Problem

After the DOORS 9.5 and the Requirements Management ETLs run a few times, some links created between the DOORS artifacts and the Requirements Management (RM) artifacts are removed from the data warehouse and therefore they are not available in the traceability report.

Related Information

The following links point to related information:

Return to the top of the page


Mon, 26 Nov 2012