WP-DETAILED CHANGE AUDITING
Back to current versionRestore this version

Detailed Change Auditing #

Detailed change auditing was created to fulfill the need to identify “who” has changed “what” data, “when” and “how”. The rules of what data to log are configurable by table and column. The scope of detailed change auditing embraces all changes made by P2K users, eP users, SS users, candidates and external users (e.g. SQL*Plus).

Features#

Session Identification#

Change Monitoring#

Auditing#

Who made the change? This could be any of the following: eP user - has a User Name on IMUS and ===should have=== a Person Code on IEID SS user - has a Person Code and User Profile on IEID Candidate - has a Candidate Code on IRCA P2K user - has a User Name on IMUS (may or may not have a Person Code on IEID) Batch Process user - has a User Name on IMUS Oracle user - if change is made outside the application Recruiter – has a Recruiter code on IRRE What was changed? Where was the change made? When was the change made?

Change Logs#

Implementing Detailed Change Auditing#

The following screens show the scenario where logging is turned ON for the IECT function.

View Change Logs and Audit Details#

VMCL#

Show Change History Dialog#

  1. Show Change History when pressed will bring up the following dialog:

Show Audit Details#