Backend Updates Without Using Standard Audit Package (Doc ID 2898691.1)

Last updated on JULY 13, 2023

Applies to:

Goal

Audit log functionality for backend updates, is the below expected behaviour?

Scenario-1:

Create a case from within the Argus application, and update some case data fields data from the backend via SQL.  The next day, the case is saved from the Argus UI by adding further data e.g. Zip Code, but when the audit log is checked, the previous day's changes from backend are also audit trailed with today's date.

Scenario-2:

Create a case from the Argus application, update some case data fields from the backend without invoking the audit trail function and then on the next day updated some different fields and invoked the audit trail function AUDIT_MODIFY_CASE_DATA.
Both the day's changes are audit trailed in a single revision.


 

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.