Hierarchy Member Security

• This is implemented for Hierarchy and Filter objects.
• For each information domain, a mapper definition can be set as the default Security mapper. Based on this mapper definition, the usage of hierarchy members are restricted.
• The nodes/members in a Hierarchy/ Filter which are mapped to your user group will be enabled and can be used. Those which are not mapped can be viewed, but you cannot use it since they are in disabled state.
• If a child hierarchy is mapped and the parent is not mapped to your user group, the parent will be displayed as a disabled node.
• You should have separate roles/functions mapped to add a leaf, sibling, or child to your hierarchy.