Micro Focus Dimensions RM (formerly known as Serena Dimensions RM) offers a unified solution that simplifies the complex process of documenting, analyzing, tracing, and prioritizing requirements, and ensuring that necessary information is communicated to stakeholders.
To keep your team connected during complex projects, you need to integrate Dimensions RM with a broad range of external development tools. Planview Hub makes it happen by allowing information to flow seamlessly among teams throughout the development process.
Hub provides flexibility in what level of information is required, synchronized and exposed in the other endpoint, and allows all parties use the tool of their choice. This helps reduce friction between teams and eliminate additional manual work.
For Example:
This section describes the basic steps needed to prepare your Dimensions RM instance for use with Hub. Note that additional fields for synchronization or configuration of queries may be required depending on the requirements of your integration.
We recommend that you create a new user within your external tool, to be used only for your Hub integration. This is the user information you will enter when setting up your repository connection within Planview Hub. By creating a new user, you will ensure that the correct permissions are granted, and allow for traceability of the modifications that are made by the synchronization.
In general, your user account should have sufficient permissions to create, read, and update artifacts in your repository. However, depending on the use case, your user may need different permissions. For example, if you are only interested in flowing data out of your repository, your user may not need to have full CRUD access, as the 'create' and 'update' permissions may not be needed.
Your user should have a secure password or token. Please be aware that Hub will not allow you to save a repository connection utilizing a weak password/token, such as 'tasktop.'
Before creating a connection to the Dimensions RM repository, a user with the necessary permissions must be created if one does not exist already. The permissions can be given either to a specific user or to a group of users. Follow the steps below to create a user and a group with the necessary permissions for use with the connector:
For the Dimensions RM connector to function properly, the user used for authentication must be assigned to the desired project and must have the following permissions on this project:
Standard Authentication
Required Fields:
Optional Fields:
Learn more about how to set up your repository in Planview Hub here.
Planview Hub: 18.4.0.20180802 and later
For person reconciliation, the following fields are available:
Fields Used for Hub’s Default Person Reconciliation Algorithm |
Field Names for Person Reconciliation Extensions (Note that these are case sensitive) |
Label in Dimensions RM |
---|---|---|
ID |
person-id |
Username |
Username |
person-username |
Username |
|
person-email |
|
N/A |
person-display-name |
Display Name |
N/A |
person-first-name |
First Name |
N/A |
person-last-name |
Last Name |
Learn more about how to configure person reconciliation in Planview Hub here.
In general, a full scan is not required to synchronize updates from this repository. However, it is possible that some read-only fields may require a full scan. Please consult with customer care for additional details.
You can learn more about special features in Planview Hub here.
Feature |
Custom Type Supported? |
Applicable Hub Versions |
Applicable Repository Versions |
---|---|---|---|
Time Worked (Worklogs) Impersonation |
|
|
|
Comments Impersonation Public/Private |
|
|
|
Attachments Impersonation |
|
|
|
N/A - State Transitions (Dimensions RM does not use state transitions. Status can flow out of or into Dimensions RM as a single-select.) |
N/A |
Planview Hub: All |
Any supported repository version: |
Learn about the difference between containers and work items in Planview Hub here.
Supported Artifact Type |
Applicable Hub Versions |
Applicable Repository Versions |
Unique URL? |
---|---|---|---|
Component Requirement |
Planview Hub: All |
Any supported repository version: |
Yes |
Marketing Requirement |
Planview Hub: All |
Any supported repository version: |
Yes |
Product Requirement |
Planview Hub: All |
Any supported repository version: |
Yes |
Defect |
Planview Hub: All |
Any supported repository version: |
Yes |
Test |
Planview Hub: All |
Any supported repository version: |
Yes |
Arbitrary (any custom class) |
Planview Hub: All |
Any supported repository version: |
Yes |
Learn more about containment in Planview Hub here.
Containers that can synchronize between repositories |
Applicable Hub Versions |
Applicable Repository Versions |
Unique URL? |
---|---|---|---|
N/A |
|
|
|
Containers used to define the boundary of a collection |
|
|
|
Projects |
Planview Hub: All |
Any supported repository version: |
N/A |
Containers used for artifact routing |
|
|
|
Projects, Folders, Child Folders |
Planview Hub: All |
Any supported repository version: |
N/A |
Note: If one field of a given type is supported, others that are also that type in theory should also work. However, sometimes there are instances in which this is not the case due to the repository. So, while we can claim support for fields at the type level, there is a chance that some specific fields of a given type will not synchronize properly.
Standard Field Type |
Does Hub support custom fields of this type? |
How is field type referenced in the repository? |
Sample Repository Fields Supported |
Particular Repository Fields NOT Supported |
---|---|---|---|---|
String |
|
Alphanumeric |
Owner Source Object Paragraph Title Paragraph ID Revision Title |
|
Single Select |
|
List |
Verification Status Current Status Workflow State |
|
Multi Select |
|
List |
|
|
Boolean |
N/A |
|
Active Inactive |
|
Date |
|
Date |
Time Created |
|
Date Time |
|
Date Time |
Time Modified Status Modified Lock Timestamp |
|
Duration |
|
|
|
|
Double |
|
Numeric |
Version ID Suspect Class ID |
|
Long |
|
|
|
|
Person |
|
User |
|
|
Persons |
|
|
|
|
Relationship(s) Learn how to configure relationships in Planview Hub here. |
|
|
Defects to Requirements Defects Identified by Tests |
|
Rich Text |
|
Text |
Text |
|
Web Links |
|
|
|
|
Container Links |
|
|
Category |
|
Other |
|
|
|
|
Category |
Limitation |
Applicable Hub Versions |
Applicable Repository Versions |
---|---|---|---|
Third Party Functional Limitation |
Collisions Limited mid-air collision support. Dimensions RM does not detect mid-air collisions. Hub will retrieve the artifact before posting changes, but there's still a window in which an overwrite may occur. |
Planview Hub: All |
Any supported repository version: |
Third Party Functional Limitation |
Explicit Integer Type Explicit integer type is not supported. Dimension RM does not support explicit integer values, but instead supports a generic "Numeric" type which Hub then maps to double. The workaround is to use doubles and cast them to integers using Groovy. |
Planview Hub: All |
Any supported repository version: |
Third Party Functional Limitation |
Explicit Person Type Explicit Person type is not supported. Dimension RM has fields that represent Persons (e.g. "Modified By"), but they aren't distinguished from other types of fields and they aren't validated as Person types. |
Planview Hub: All |
12.1, 12.2 |
Third Party API Limitation |
Internal Link Fields Internal link fields only appear for primary artifact type. Dimensions RM Links have a Primary artifact that links to a Secondary artifact. In Hub, link fields will only appear on artifacts where the artifact type is the primary type of the link field. For instance, a link field from Product Requirements to Component Requirements would only appear on Product Requirements. If the direction is a problem, a workaround could be to create a custom link type where the direction is reversed. |
Planview Hub: All |
Any supported repository version: |
Third Party API Limitation |
Required Fields Required fields may not appear as required in Hub. Dimensions RM SOAP API does not show whether a field is required or not when we call QueryAttributes to retrieve the schema. There is a Mandatory attribute, but that is displayed as false even for required fields (but it is true for the Summary field) |
Planview Hub: All |
Any supported repository version: |