My Oracle Support Banner

EGRC Issue With Last Updated By On Incidents Records (Doc ID 1643807.1)

Last updated on OCTOBER 10, 2023

Applies to:

Oracle Application Access Controls Governor - Version 8.6.4 to 8.6.4 [Release 8]
Oracle Transaction Controls Governor - Version 8.6.4 to 8.6.4 [Release 8]
Information in this document applies to any platform.


On : version, Basic Operations & Functionality

Everytime we re-run the Control to refresh the Incidents and analyze any new incidents, the 'Last Updated by' and 'Last Update On' field switches back to person running the Control Analysis Job and Control Analysis Run Date respectively. Therefore, if a user took action on an incident previously, that history does not stay because the controls get re-run again. And the 'Last updated by' field changes back to the user ID who runs the jobs.

Control Analysis Job should not change the 'Last Updated by' and 'Last Update On' field values when nothing is getting changed for those incidents in Control Analysis run.

The issue can be reproduced at will with the following steps:
1. Login as User A and Run the Control Aanlysis.
2. Check the Incidents and identify one which shows Last Changed By As User A.
3. Login as User B, identify the incident as in Step2.
4. Edit the Incident, Accept and add Comment. Click on Submit.
5. Verify the Incident and it shows Last Updated By as User B.
6. Login as User A and re-run the Control Analysis.
7. Identify the incident as in Step2, It retains the status correctly as Accepted but shows Last Updated By as User A... which is incorrect.

The issue has the following business impact:
Due to this issue, this prevents users from knowing who took what action in the tool.


To view full details, sign in with your My Oracle Support account.

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

In this Document

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