User Defined (UD) Date Fields Are Not Getting Audited When Updating Them With NULL Through Post Save (Doc ID 3049395.1)

Last updated on NOVEMBER 05, 2024

Applies to:

Symptoms

The system audits the change correctly in the audit log when User Defined (UD) dates in the case form are updated with a proper date through post-save.
However, system is creating a blank audit revision when the existing date value in User Defined (UD) dates in the case form updated with a Null through post-save.

STEPS TO REPEAT:
================
Steps to Create:
1. Configure a User Defined Date field and make it visible under the Event Information section
    a. Go Argus Console > System Configuration> Field Properties > Events> Event Information > User Defined Date 2
    b. Change the field Label to 'Fatal Outcome Date'
    c. Hidden to No and save it

2. Create the following Post Save Function in the database as the schema owner

3. Configure the post save function FN_POST_SAVE under Console (Argus Console > System Configuration> System Management > Custom routine after commit)
4. Add CASE_EVENT (Event Information) under the table config section (that is there next to the post save check box)
5. Create a case and go to the events tab
6. Check the Death check box and enter a date into the 'Fatal Outcome Date' field and save the case
7. Check the audit log and observe that the system audits the change to the 'Fatal Outcome Date' field properly
8. Open the case again go to the events tab, uncheck the Death check box, and save the case
9. Check the audit log and observe that the system created a blank audit revision

Cause

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