When adding a new node to the UDM, you can now specify the node id by selecting it from the dropdown list. By default it is "1". If you want to add a sibling to this node, the default node id is taken as 101. When a new node is added, the node id allocated is in multiples of 100.

This makes the node ids more change- tolerant. This also ensures that the generated HTML tags can withstand change in the UDM.

Say, a sibling is added to the root node. It has node id =1. The child nodes to this sibling have node ids 3, 4, 5 & 6. Another sibling is added to the root node. The node id is 7 and the sibling has child nodes with ids 8, 9, 10 & 11. Suppose a new child is added to the first sibling, the child acquires the id 7. This causes the node ids of the remaining siblings and their child nodes to get changed, thus offsetting the entire database resulting in further complications.

This has now been made more simple by spreading the node ids of the siblings in multiples of hundred. In the improved version, the first sibling has node id 1. The child nodes to this sibling will have ids, say, 2,3,4 & 5. The second sibling has node Id 101. Its child node will have node ids 102, 103, 104, 105 and so on. If a new child node is added to the first sibling, the child node acquires the id 6. Hence it doesn't affect the node ids for the rest of the tables in the database.

The large interval between the node ids of the two siblings ensures that there is enough room to accommodate additional data without offsetting the existing data.

The available node ids are displayed in a dropdown in the very first step of node addition so that you can make a more informed choice of the node ids.