Limitations and recommendations

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

  • If Dimensions RM has more than one URL (HTTP and HTTPS), OpenText Dimensions CM requests are displayed only if the RM Browser windows are using the exact URL that is registered with OpenText Dimensions CM. OpenText Dimensions CM accepts requests only from the registered URL. If the association between OpenText Dimensions CM and Dimensions RM is set up using HTTPS, then using Dimensions RM from HTTP does not allow to return OpenText Dimensions CM information (requests) to Dimensions RM.

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

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

  • For consistent synchronization, after a Dimensions RM project is associated to an OpenText Dimensions CM product, we recommend that you never remove this association.

  • For consistent synchronization, after a Dimensions RM baseline or collection is associated to OpenText Dimensions CM project/stream, we recommend that you never remove this association.

  • Never delete an OpenText Dimensions CM project/stream until after all Dimensions RM baselines or collections are unassociated from the OpenText Dimensions CM project/stream. If this strategy is not followed, the Dimensions RM GUI is incapable of removing the association, and a consultant is required to repair both the OpenText 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 OpenText Dimensions CM objects.

  • The OpenText Dimensions CM–Dimensions RM OpenText Application Quality Management integration only works with OpenText Dimensions CM requests. External requests are not supported.

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

  • When a 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 request regardless of the request's state/phase.

  • Dimensions RM baselines are fixed. You cannot replace or update requirements in an Dimensions RM baseline. We recommend that you relate Dimensions RM baselines only to OpenText Dimensions CM projects/streams.

  • If you unrelate a Dimensions RM baseline or collection from an OpenText Dimensions CM project/stream, the relationships between OpenText 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 RM integration prerequisites.

Back to top

Next steps: