Application Specific Validation for Equivalent Nodes in Related Viewpoints
- An application specific validation is available to verify whether certain nodes in a viewpoint also exist in one or more other related viewpoints.
- The Equivalent Nodes With Filter validation is disabled by default but can be enabled for any dimension where the same nodes must be in multiple viewpoints for data integrity reasons.
- The Related Viewpoints and Equivalent Nodes Filter parameters need to be configured for viewpoints where the validation will be enforced.
Business Benefit: This validation ensures completeness of nodes across multiple related viewpoints in a dimension for reconciliation purposes.
Calculated Name for Nodes Added By Copy or Model after Action
- Names can be calculated for new nodes that are added to a viewpoint using a Copy or Model After action.
- The calculated name can be based on properties and relationships which are copied or some other information about the node.
- Node names can be calculated when performing a Copy or Model After operation interactively, during a request file load, or using a subscription.
Business Benefit: Node names can be calculated for new nodes which are copied or modeled after existing nodes in a viewpoint.
Management Hierarchy Approvals
- Approval policies can be configured with the Management Hierarchy approval method to invite approvers based on a hierarchy of users defined in a Users type application.
- Users who are ancestors of the request owner in the management hierarchy are individually invited to approve their requests in a sequential manner.
- The approval policy can be set up with a fixed or variable number of approvals before the policy is fulfilled.
Business Benefit: Requests submitted by different users can have different approvers based on an organizational hierarchy that is maintained in Enterprise Data Management or loaded from a source system.
