This page (revision-9) was last changed on 26-Nov-2021 10:22 by JMyers

This page was created on 26-Nov-2021 10:22 by Administrator

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
9 26-Nov-2021 10:22 9 KB JMyers to previous
8 26-Nov-2021 10:22 9 KB JMyers to previous | to last
7 26-Nov-2021 10:22 9 KB RForbes to previous | to last
6 26-Nov-2021 10:22 9 KB JAiken to previous | to last
5 26-Nov-2021 10:22 9 KB RForbes to previous | to last
4 26-Nov-2021 10:22 8 KB RForbes to previous | to last WP - DETAILED CHANGE AUDITING ==> WP-DETAILED CHANGE AUDITING
3 26-Nov-2021 10:22 8 KB RForbes to previous | to last WP - DDETAILED CHANGE AUDITING ==> WP - DETAILED CHANGE AUDITING
2 26-Nov-2021 10:22 8 KB RForbes to previous | to last WP - Detailed Change Auditing ==> WP - DDETAILED CHANGE AUDITING
1 26-Nov-2021 10:22 8 KB Administrator to last

Page References

Incoming links Outgoing links
WP-DETAILED CHANGE AUDITING...nobody
WP-DETAILED CHANGE AUDITING

Version management

Difference between version and

At line 2 changed one line
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 Personality users, SS users, candidates and external users (e.g. SQL*Plus).
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).
At line 21 changed one line
*In Personality, all of the change logging is done via Java code in the middle tier
*In [{$applicationname}], all of the change logging is done via Java code in the middle tier
At line 24 changed one line
*Personality sessions are fully tracked and more extensively audited than in the past
*[{$applicationname}] sessions are fully tracked and more extensively audited than in the past
At line 43 changed one line
*The user session - may be related to Personality users, SS users, candidates and external users (e.g. SQL*Plus). , SS, CSS, other
*The user session - may be related to P2K, eP, SS, CSS, other
At line 52 changed one line
*It is possible to view the historical changes associated with each block on every screen of Personality by the use of the Show Change History icon
*It is possible to view the historical changes associated with each block on every screen of eP by the use of the Show Change History icon
At line 74 changed one line
*The Logged in As field will display the IMUS user name associated to the employee if they are logged into Personality while making changes. If they are logged into Self Service while making the change, the user’s Person Code will be displayed. Changes mapped to roles will display the role name. If a change is made in Self Service that is tied to a Personnel Action, the IMUS user name of the individual who processes the PA will display in the Logged In As field.
*The Logged in As field will display the IMUS user name associated to the employee if they are logged into eP while making changes. If they are logged into Self Service while making the change, the user’s Person Code will be displayed. Changes mapped to roles will display the role name. If a change is made in Self Service that is tied to a Personnel Action, the IMUS user name of the individual who processes the PA will display in the Logged In As field.
At line 82 changed one line
*A derived field was added to the Change History dialog to display the System Accessor code for each change log detail. Therefore, if an Personality user is logged in and has made a change, the user name will be displayed as the one who made the change, if logged into Self Service while making the change the person code will be displayed, changes mapped to roles will display role name, recruiter will display the recruiter code and candidates will display candidate code.
*A derived field was added to the Change History dialog to display the System Accessor code for each change log detail. Therefore, if an eP user is logged in and has made a change, the user name will be displayed as the one who made the change, if logged into Self Service while making the change the person code will be displayed, changes mapped to roles will display role name, recruiter will display the recruiter code and candidates will display candidate code.
At line 96 added 2 lines
[{If var='loginstatus' contains 'authenticated'
At line 97 changed 2 lines
![Notes|Edit:Internal.WP-DETAILED+CHANGE+AUDITING]
[{InsertPage page='Internal.WP-DETAILED+CHANGE+AUDITING' default='Click to create a new notes page'}]
![Discussion|Edit:Internal.WP-DETAILED+CHANGE+AUDITING]
[{InsertPage page='Internal.WP-DETAILED+CHANGE+AUDITING' default='Click to create a new discussion page'}]
}]
This page (revision-9) was last changed on 26-Nov-2021 10:22 by JMyersTop