Relationship Overview
In BMC Helix Portfolio Management, a Relationship links one record (a root entity) to another entity, so you can capture how portfolios, ideas, incidents, work orders, or other entities from third parties are connected. Relationships enable you to express real-world associations, such as the Idea - IDEA001 belongs to the Portfolio - PRTF005, the Demand - DMND004 impacts the Project PRJT001, and so on.
These relationships, in BMX Helix Portfolio Management, can be synced automatically for any system generated relationships. For example Portfolio - PRTF001 is the grandparent of Idea - IDEA008. Alternatively, relationships can be created manually between entities internal to Portfolio Management and entities that are internal or external to Portfolio Management. For example, a Portfolio can be related to an internal entity such as idea or sprint and can also be related to an incident or another entity from a third party application.
A single record can have many records related to it through different relationship types.
Relationship Type and Relationship Type Connections
Each Relationship is governed by a Relationship Type, which says what the connection means (for example, impacts, groups, belongs) and how two entity types are allowed to connect. Relationship Types, in turn, contain one or more connections (Node A ↔ Node B) that specify which entity types can be connected.
For example, the relationship type impacts connects the entity types Requirement and Project Task. Similarly, the Grandparent relationship type connects Portfolio to the idea entity type.
How to configure a Relationship Type?
Only the application admins have the authority to configure a relationship type.
For more information, see Configuring Relationship Types.
Related topics