A DRM hierarchy is a special type of containers that contains nodes in a hierarchical manner.
A hierarchy is created under a DRM version.
A node can be created under the context of a hierarchy by adding the node to the hierarchy.
A node can be shared across hierarchies. In this case, the existing can be selected to add to a new hierarchy. You can control whether nodes can be shared by setting the rule at the hierarchy level.
A DRM hierarchy has common seen properties:
- Hierarchy ID
- Hierarchy Name
- Hierarchy Description
- Hierarchy Owner
- Hierarchy URL: A generated URL to allow the user to access this hierarchy
- Top Node
- Top Node ID
When a hierarchy is being created, the specific node types can be enabled for the hierarchy by using the Hierarchy Node Type property. For example, if this is a legal entity hierarchy, you can create a node type called “legal entity node type” and the nodes created under this hierarchy will be legal entities and the properties associated with the legal entity node types can be used when creating the nodes.
A hierarchy can have nodes of different node types and the same node can be of different node types in different hierarchies.
There are other Hierarchy Properties that define how the nodes are displayed within the hierarchy, such as:
- Default Display Properties – the node property will be shown for displaying the nodes within the hierarchy.
- Standard Hierarchy Sort
- User Display Properties
- User Hierarchy Sort
The name of a hierarchy cannot be changed after you save it.