When Enterprise Data Management Cloud (or EDM/EDMCS) was released a year back, Data Relationship Management (DRM) finally moved to the cloud. The EPM family is getting stronger, and after a good amount of patches installed to EDMCS, it’s time to discuss some high-level EDMCS functionalities. It is extremely valuable to understand how and when to use EDM. In this post, we will be focusing on Node Type Converters.
First and foremost, similar to other EPM cloud applications, EDMCS is a Software-as-a-Service (SaaS) product and has a similar cloud application interface. EDMCS provides a single platform to flexibly manage enterprise data while maintaining data integrity and enterprise application alignment. The following is the EDMCS home page interface.
Figure 1 – The EDMCS Home Page Interface
What is a Node Type?
To properly use Node Type Converter, having a good understanding of a node type is necessary. A node type is a collection of nodes that share a common business purpose; this idea is similar in DRM. We are able to use node types to define nodes’ properties and to define rules that convert a node type to another node type. In EDMCS, every node is assigned a node type. A node is uniquely identified by the combination of node name and node type.
Figure 2 – Illustrates Node Types
Node Type Converter
Generally speaking, we use node types to define nodes’ properties. Node Type Converter is heavily used for EDMCS Subscriptions. Subscription is used to make changes in one viewpoint and has those changes applied to target viewpoints for multiple applications that require the same changes. We may discuss the EDMCS subscriptions in future posts. Let’s focus on the Node Type Converters first.
The common question we have is under which situation do we need to consider node type converters. For example, when you have a source and target viewpoints that do not share a common node type, then you would consider creating a node type converter for subscriptions to work. Node type converters are needed to compare, locate, align, and drag and drop nodes of different node types across two viewpoints in side by side layouts. So the foundation is there to readily implement subscriptions.
To create/add a Node Type Converter, go to the node type card and then inspect one of the node types. One example is the Cost Center. Log into the EPM enterprise environment, and then select Rules.
Figure 3 – Inspecting the Cost Center Node Type Converter
Figure 4 – Getting a further look at the Cost Center Node Type Converter
The Node Types are grouped and sorted by application. For example, the figure below shows the target node type is not included in the Department list.
Figure 5 – Showing the Cost Center Node Type Converter is not included in the Department list
It’s important to make sure all the node type converters are mapped to all required properties. When we create a converter, properties are auto-mapped where possible, but we can make changes to the properties that auto-populated. If the target property is read-only, the row shows the source property is not editable.
Figure 6 – Demonstrates Mapping all Node Type Converters to Required Properties
Then we can repeat the process for each Target Node Type. Remember to make sure you have node converters that you need!
I hope you have a better understanding of adding a node type converter after reading this. We may talk more on the uses cases of node type converter in future posts. Please feel free to email us here if you are interested in learning more or have any questions.