Auditing Transactions from Committed Governance Requests

 

Before You Begin

Purpose

This tutorial demonstrates how to audit transactions originating from committed governance requests in Oracle Data Relationship Management.

Time to Complete

Approximately 10 min.

Background

Governance requests which are committed to a Data Relationship Management version result in transactions recorded in the transaction history for auditing purposes. The transaction history can be queried to identify the changes made by a committed request, who was responsible, and when they occurred. Transactions are linked to requests so users can follow the audit trail from a transaction back to the governance request from which it originated.

Scenario

In this tutorial, you query transaction history to identify changes made to a hierarchy which originated from a committed governance request. You can view request details for each transaction and navigate to the originating request for complete information about why the change occurred.

What Do You Need?

Before starting this tutorial, you should:

 

Logging On to the COAMGMT Application

  1. Launch Data Relationship Management Web Client.

    The logon page for Oracle Data Relationship Management is displayed.

    The Logon Page
  2. Log on to the COAMGMT application as user JStein with a password of Welcome!.

    The Browse page is displayed.

 

Auditing Transactions for Governance Requests

 

Querying Transactions By the Request ID

In this section, you query transactions for a specific request by filtering on request ID.

  1. Click Worklist and then click All.

    The Worklist page displays governance requests. Copy a request ID that you would like to audit (for example, 18).

  2. Click Audit.

    The Audit page is displayed. By default, the Audit Type is set to Transactions.

  3. On the Source tab, in the Request ID text box paste the request ID (for example, 18) that you copied in step 1 and clear the System Transactions option.

    The Source Tab
  4. On the Source tab, click the ellipsis button (Select Hierarhy) for Hierarchies. In the Select Hierarchies dialog box, select Vision Jan 2013 from the Version drop-down list and Parent Total from the Hierarchy drop-down list, and click the Select button (Select).

    The Select Hierarchies dialog box.
  5. Click OK.

    New Request
  6. Select the Filters tab and clear the Filter to Current Session option.

  7. Select the Columns tab and select the Workflow Request ID column. Optionally, move the Workflow Request ID column to the top of the list of the selected columns.

  8. Click the Run Query button (Run Query).

    The query returns a list of transactions that are associated with the workflow request 18.

    Query Results
 

Identifying Transactions Originated From Requests

In this section, you query trasactions to identify those that have been originated from workflow requests.

  1. On the Source tab, clear the Request ID text box.

    The Request ID resets to 0 (zero).

    The Source Tab
  2. Click the Run Query button (Run Query).

    The query returns a list of transactions including those that are associated with the workflow requests that added nodes into the Parent Total hierarchy. The Workflow Request ID column values identify the originating request for each transaction returned.

  3. Click the Expand icon (Expand) for the transaction that added the 6230 node.

    The transaction details are displayed across Action, Object, History, and Request tabs.

    Transaction Details
  4. Select the Request tab to view the request details for the transaction.

    The Request tab displays information associated with the Add Node transation such as request id and title, workflow model upon which the request is based, the workflow task and stage title, the user name who submittied the request, and the timestamp of the request submission.

    Request transaction details
  5. Optional. If you want to view all the request details, click the Navigate to Request button (Navigate to Request).

    Request Details
  6. Log out as user JStein.

 

Want to Learn More?