Limitations and recommendations

Before you begin setting up the Dimensions CM–RM associations, review these limitations and recommendations:

  • If Dimensions RM has more than one URL (HTTP and HTTPS), Dimensions CM requests will only be displayed if the RM Browser windows are using the exact URL that is registered with Dimensions CM. Dimensions CM will only accept requests from the registered URL. If the association between Dimensions CM and Dimensions RM is set up via HTTPS, then using Dimensions RM from HTTP - Dimensions CM information (requests) will not be returned to Dimensions RM.

  • The username and password of the user involved in ALM integration (for example, dmsys) must be the same for both Dimensions CM and Dimensions RM. The username and password are case-sensitive.

  • Dimensions RM does not support connections/associations to more than one Dimensions CM server.

  • For consistent synchronization, once a Dimensions RM project to Dimensions CM product association is established it is recommended that it never be removed.

  • For consistent synchronization, once a Dimensions RM baseline or collection to Dimensions CM project or stream association is established it is recommended that it never be unassociated.

  • Never delete a Dimensions CM project/stream until after all Dimensions RM baselines or collections are unassociated from the Dimensions CM project/stream. If this strategy is not followed, the Dimensions RM GUI will be incapable of removing the association and a consultant will be required to repair both the Dimensions CM and Dimensions RM databases.

  • To maintain process integrity, you must never delete a Dimensions RM baseline or collection that has any requirements related to Dimensions CM objects.

  • The Dimensions CM–Dimensions RM ALM integration only works with Dimensions CM requests. External requests are not supported.

  • The relationship between Dimensions CM requests and Dimensions RM requirements does not get replicated if using Dimensions Replicator.

  • When a Dimensions CM request is related to a Dimensions RM requirement it is related to "the latest version of the requirement in the associated baseline or collection" until that request is actioned to a FROZEN/FINAL/OFF NORMAL state/phase. When that occurs, the request is pinned to the current latest version of the requirement. When you action the request back again it then "floats" with the latest version again.

  • You can unrelate a Dimensions RM requirement from a Dimensions CM request regardless of the state/phase of the request.

  • Dimensions RM baselines are fixed—you cannot replace or update requirements in an Dimensions RM baseline. It is recommended that you only relate Dimensions RM baselines to Dimensions CM projects/streams.

  • If you unrelate a Dimensions RM baseline or collection from a Dimensions CM project/stream the relationships between Dimensions CM requests and Dimensions RM requirements remain and can still be seen.

Before continuing, ensure that you have fulfilled all the prerequisites. For details, see Dimensions CM–RM integration prerequisites.

Back to top

Next steps: