Node Type (DRM)
Node Type in DRM is similar to the database table definition in the relational database.
It groups nodes with the similar characteristics.
A node can be created under more than one node type under different hierarchy. I do not know why people would like to do that. One example I can think of is that an organization is a department as well a legal entity. When the node is added in the department hierarchy, you add the department specific properties to that node. When the same node is shared and is added to the legal entity hierarchy, legal entity related properties can be added.
It can define which user-defined properties are shown or hidden for nodes based on the node type the node is created under.
Nodes created under the same node type have the same set of properties.
An example of a node type can be “Cost Center”. A property can “Cost Center Manager”.
The separation of the property definition from the node type definition makes the property definition shareable across different node types.
Typically relational database designers do not have a straight forward way to identify the properties shared across database tables.
You can also enforce validation by node types. For example, the nodes created for cost center hierarchy need to have cost center manager. The cost center manager property should only be required for cost center node type.
Custom Icon (Glyph)
You can have visual indicator on the nodes by assigning a different icon for different node types.
Node Type is an optional construct. You only need to define node types for controlling and enforcing business rules.
To enable node type to be used in grouping nodes, you need to create a custom property and use a custom property to point to the node type.