Nodetype Relationship Configuration – Hierarchical Model

Post date: Jan 11, 2018 7:08:45 AM

The data representation in Hierarchical model has some relation between one node to other. Usually in framework we write model validator to achieve this by checking whether user connecting node as per business structure or not, for example: Customer Data Management, to create new customer user must draw a model where Party Node should be root and Account to be child to it and then Site should be child to Account Node.

Now we can configure relation between nodes using Applications eWorksheet instead of developing independent model validator every time when new application created. The new enhancement in framework validates hierarchical structure when user connects a node to other in Canvas and shows proper messages as configured if it is not a valid relation.

Below screens shows how to configure and how it will work.

Parent-child relationship configuration

Validation message shows when parent-child relationship violates

Validation message shows when Root Nodetype violates

Follow the video to learn How to configure Nodetype Relationships

Follow the video to learn about How does Nodetype Relationship work for Hierarchical Model validation