Workarounds: Rich Client problems in Rational DOORS Next Generation 4.0.2

Douglas Raith, Alex Elrick
Last Updated: March 15, 2013
Build Basis: Rational DOORS Next Generation 4.0.2

Problem summary

OSLC links cannot be created in the rich client after servers are migrated from version 3

Problem

If two projects on a version 3 Requirements Management (RM) server have an OSLC provider relationship and the database is migrated to version 4, you cannot create OSLC links between those projects by using the rich client.

Workaround

Create the links by using the web client. To view an artifact in the web client, open the Artifact properties window for that artifact and click View in web client.

Related information

The following link points to related information:

• Defect 70776: DNG Client: Can’t create OSLC link to RQM or RTC after either has been upgraded in n-1 scenario

Problem summary

OSLC links cannot be created in the rich client when the client and server use different locales

Problem

If the language locale setting for the rich client is different than that setting for Jazz Team Server, you cannot create OSLC links from requirement artifacts in the rich client.

Workaround

Either use the same language locale for the rich client and the server, or create the links by using the web client. To view an artifact in the web client, open the Artifact properties window for that artifact and click View in web client.

Related information

The following link points to related information:

• Defect 70894: [DNG only] Can’t create OSLC links in rich client on different language locale than server

Workaround summary

When you move artifacts or sections in a module, the rich client does not save the move

Problem

If you drag an artifact or section to a new location in a module but do not place the artifact or section under a new parent, when you save the module, the move is not saved.

Workaround

Move the artifact or section to a temporary location under a different parent and save the module. Then, move the artifact or section to its intended location and save the module again.

Related information

The following link points to related information:

• 71682: Rich client module – Location of moved sections under same parent are not maintained after module close and reopen

If you add the Implemented By column in the rich client, the column is not shown in the web client

If you add the Implemented By link type to a module view in the rich client, save the view, and then open the view in the web client, the Implemented By link column is not shown in the web client.

Workaround

Create the view that contains the Implemented By link type by using the web client.

Related information

The following link points to related information:

• Defect 70085: SSEA: Implemented By column added in DNG rich client is not visible in web client