How to Configure Approval Change Tracking (Doc ID 1472281.1)

Last updated on JULY 28, 2016

Applies to:

Hyperion Data Relationship Management - Version 11.1.1.0.00 to 11.1.2.0.00 [Release 11.1]
Information in this document applies to any platform.

Goal

Configuring DRM for Approval Change Management.

Background

DRM can be configured to warn administrators of certain changes, such as changes to specified properties or events like a node's being moved, by resetting a flag. Several flags, each with different conditions, may be defined. The combination of flags and conditions (or 'triggers') is termed an Approval Group.

When an action requiring approval is made by an end-user, the approver will be alerted by the flag property (for which a query may be defined). The approver will acknowledge by setting the flag or taking corrective action if necessary. The convention is that the node is deemed 'approved' when the flag is true, and 'requiring approval' when false.

Approval Groups are complementary to Change Tracking in that they are configurable, whereas Change Tracking is triggered upon any change to a node. However, Change Tracking captures more detail including the ID of the person making the change and the time & date of the change.

Approval Tracking has been largely superseded by Transaction Requests (and now, Data Governance), which permit changes requiring approval to be grouped as a single entity and allow the request to be validated without committing changes to the Data Relationship Management version. In contrast, Approval Tracking only occurs after the changes have occurred.
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms