Oracle Hyperion DRM Basics | Node types

Now we are getting into what makes Oracle Hyperion Database Relationship Management (DRM) so flexible: node types. As we explained in an earlier blog, nodes in a hierarchy can be assigned a node type. Node types allow you to filter properties and validations that will be available for the node. Node types will also allow you to assign a different icon to your nodes.

There are three steps that you need to follow to assign node types. First you create the node types you need; second you create a property to assign the node type to a node, and thirdly, you associate this node type property to the relevant hierarchies.

1. Create a node type

Log in to Oracle Hyperion DRM then navigate to Administer > New >  Node Type. Oracle Hyperion DRM will open a tab similar to the following:

 

You must give the node type a name and a description. You can also assign a glyph to the node type. The glyph is an icon that will be shown against the nodes. In this example, I will not be associating any glyph to the node type, but to do so, all you have to do is load the icon by creating a new glyph then select it in the node type definition.

 
 

 

Once the node type has a name and a description you can associate properties and validations using the lower part of the screen. Only the properties that are associated to the node type will be visible against a node with that node type. Similarly, only validations associated to the node type will be executed against nodes with that node type. Once you have associated the properties and validations, you can save the node type.

2. Create the property to associate node types to nodes.

In the following example, we are just going to create a simple defined local string property with a list. Let’s say we only have two node types, “Account node type” and “Other”, we create and configure this list property with only two valid values “Account node type” and “Other”. This way, we are sure that users will only select a valid node type.

 

Note: The property must always store the exact name of the node type. If the property stores a value that does not correspond to any existing node type, Oracle Hyperion DRM will assign the default node type to the node, so all properties and validations will be assigned to the node.

Since we have just created this property and we want it to be visible against the node type we created, we have to go back to our node type definition and associate it to the node type.

 

3. Associate property to a hierarchy

Navigate to the version and right click on the hierarchy then select properties.

 

In the system property labelled “Hierarchy Node Type”, select the property you have just created then save.

 

 

 

 

 

 

 

 

 

 

Now nodes in the hierarchy will assume the node type you select in this property.

Hopefully this will have helped you understand how to work with node types but do contact us if you want any further clarification. In our next technical blog we will review exports.

This entry was posted in Technical and tagged , , , , . Bookmark the permalink.

Comments are closed.