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

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

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
27 26-Nov-2021 10:22 9 KB rforbes to previous DETAILED CHANGE AUDITING ==> AUDIT LOGGING
26 26-Nov-2021 10:22 9 KB rforbes to previous | to last
25 26-Nov-2021 10:22 9 KB jmyers to previous | to last ENABLE_AUDITING ==> ENABLE_AUDITING(System_Preference)
24 26-Nov-2021 10:22 9 KB rforbes to previous | to last
23 26-Nov-2021 10:22 9 KB rforbes to previous | to last
22 26-Nov-2021 10:22 9 KB rforbes to previous | to last DEaTAILED CHANGE AUDITINGx ==> DETAILED CHANGE AUDITING
21 26-Nov-2021 10:22 9 KB rforbes to previous | to last DeTAILED CHANGE AUDITINGx ==> DEaTAILED CHANGE AUDITINGx

Page References

Incoming links Outgoing links
AUDIT LOGGING
AUDIT LOGGING

Version management

Difference between version and

At line 3 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 P2K users, eP 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 Professional users, Self Service users, Candidates and external users (e.g. SQL*Plus).
At line 13 changed one line
*To enforce tight audit controls, sessions that are initiated outside ePersonality and P2K that must update the database, will be forced to do the following:
*To enforce tight audit controls, sessions that are initiated outside the application that must update the database, will be forced to do the following:
At line 22 changed one line
*All database changes made inside and outside the ePersonality and P2K applications must be monitored
*All database changes made inside and outside the application must be monitored
At line 25 changed 2 lines
**In ePersonality, all of the change logging is done via Java code in the middle tier
**In P2K, all change logging is done via database triggers (created by P2K_SMLTT) which have been enhanced to prevent un-authorized changes from taking place.
**In the application, all of the change logging is done via Java code in the middle tier
At line 28 changed 2 lines
*ePersonality sessions are fully tracked and more extensively audited than in the past
*P2K sessions will be tracked and audited the same as in the past with enhancements to say that they are from Reports or Forms, etc.
*Sessions are fully tracked and more extensively audited than in the past
At line 35 changed 5 lines
***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
***eP user - has a [User Name|USER_NAME] on [IMUS] and should have a [Person Code|PERSON_CODE] on [IEID]
***SS user - has a [Person Code|PERSON_CODE] and [User Profile|USER_NAME] on [IEID]
***Candidate - has a [Candidate Code|CANDIDATE_CODE] on [IRCA]
***P2K user - has a [User Name|USER_NAME] on [IMUS] (may or may not have a [Person Code|PERSON_CODE] on [IEID])
***Batch Process user - has a [User Name|USER_NAME] on [IMUS]
At line 41 changed one line
***Recruiter – has a Recruiter code on IRRE
***Recruiter – has a [Recruiter Code|RECRUITER_CODE] on [IRRE]
At line 44 changed one line
** Described by a table & row (MTD_ID and row reference ID) and a list of columns (MCD_ID)
** Described by a table & row ([MTD_ID] and row reference ID) and a list of columns ([MCD_ID])
At line 46 changed one line
** Context information required for all parent key information will be stored in XML format \\e.g. Distribution 1 \\of Assignment Detail effective 01 Jan 2006 \\ of Assignment 01 \\ of Employment with High Line \\ for Person # 000001
** Context information required for all parent key information will be stored in XML format \\e.g. Distribution 1 \\of Assignment Detail effective 01 Jan 2006 \\ of Assignment 01 \\ of Employment with the organization \\ for Person # 000001
At line 50 changed 2 lines
** The user session - may be related to P2K, eP, SS, CSS, other
** The function being used - e.g. IEAS
** The user session - may be related to eP, SS, CSS, other
** The function being used - e.g. [IEAS]
At line 61 changed one line
*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
*It is possible to view the historical changes associated with each block on every screen within the application by the use of the Show Change History icon
At line 64 changed 4 lines
*Detailed Change Auditing can be turned on or off for a table or individual column by using the ‘Logging Not Allowed” toggles in [IMTD] and [IMCD].
*If clients do not want changes to be captured in certain tables or columns the Logging Not Allowed toggle should be turned ON.
*If logging is currently enabled and users wish to disable it, the ‘Disable Logging’ should be turned ON.
*There are certain tables that High Line has predetermined that Logging is Not Allowed due to the volume of data that these tables can hold. A few examples of these tables are [P2K_PR_PAY_PC_AMOUNTS], [P2K_PR_PAY_LINES], and [P2K_PR_PAY_LINE_DETAILS].
*Detailed Change Auditing can be turned on or off for a table or individual column by using the ‘[Logging Not Allowed|LOGGING_NOT_ALLOWED]” toggles in [IMTD] and [IMCD].
*If clients do not want changes to be captured in certain tables or columns the [Logging Not Allowed|LOGGING_NOT_ALLOWED] toggle should be turned ON.
*If logging is currently enabled and users wish to disable it, the ‘[Disable Logging|DISABLE_LOGGING]’ should be turned ON.
*Set the system preference [ENABLE_AUDITING(System_Preference)] to "Y" in IMST, and __restart the application instance__
*There are certain tables that have been predetermined that [Logging Not Allowed|LOGGING_NOT_ALLOWED] due to the volume of data that these tables can hold. A few examples of these tables are [P2K_PR_PAY_PC_AMOUNTS], [P2K_PR_PAY_LINES], and [P2K_PR_PAY_LINE_DETAILS].
* Changes made outside the application are only captured if you have created the data base logging triggers. To do this, execute the script AM_XMLT.sql, as the P2K user, in SQL*Plus.
At line 69 added 12 lines
----
!!View Change Logs and Audit Details
!VMCL
*The [VMCL] screen is used to view the Data Change Logs per table. The header section of the form displays the date the change was made, which user made the change, what action was done and in what function.
*Context 1 will hold (in XML format) the Parent Context information; this is based on the Unique Keys of the changed record and its parents.
*Context 2 will hold (in XML format) all columns and values except those with domains of VARCHAR2000 & VARCHAR4000.
*The details section shows which columns were changed, when the change took place and what the before and after values are.
*When a change takes place, but before the values are committed to the database, a Change Log record is created without the Context columns populated. When the changes are committed to the database, the context columns are added to the new Change Log Record, and the Change Log Details records are created for every changed column and added to the database.
*If logging is turned on for a table and turned off for a changed column no Change Log Details record will be created.
*If there is an exception between the time the Change Log is created and before the Change Log Details and context information are created, then Context 1 will hold a message indicating that Auditing was not complete.
*The Logged in As will display the [IMUS] user name associated to the employee if logged into the application while making changes. If logged into Self Service while making the change the user’s [Person Code|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|PERSONNEL ACTION], the [IMUS] user name of the individual who processes the PA will display in the Logged In As field.
*Context 1 will show the [person code|PERSON_CODE], [candidate code|CANDIDATE_CODE] or [recruiter code|RECRUITER_CODE] of the user logged in making the change.
At line 82 added 5 lines
!Show Change History Dialog
*It is possible to view the historical changes associated with each record within a screen. This can be done via the “[Show Change History|MMTCL]’ dialog. This dialog is displayed by pressing the [CHANGE_HISTORY.JPG] icon found in the header of all forms or by pressing F10.
*The dialog will display the following information for each column within the record in focus: time the change was made, what action was done, in what function, who made the change and what the before and after values are.
*A derived field was added to the Change History dialog to display the System Accessor code for each change log detail. Therefore, if a Professional 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|PERSON_CODE] will be displayed, changes mapped to roles will display role name, recruiter will display the [recruiter code|RECRUITER_CODE] and candidates will display [candidate code|CANDIDATE_CODE].
*The second tab will display the change history for any user fields associated to the table.
At line 88 added 7 lines
!Show Audit Details Dialog
*The [Show Audit Details|MMCRA] dialog displays the current information for each record on the table that is currently in focus.
*The dialog can be called up by pressing F12 or by pressing the [AUDIT_DETAILS.JPG] icon
*The user can navigate through the list of column names to determine the changed value for each column on the table in focus.
*The dialog can be used to determine the row id of the parent table as well as the dependent table.
*The user can determine when the last change was made to the table and by whom by reviewing the [Change Date|CHANGE_DATE] and [Change User|CHANGE_USER] columns.
*The dialog also displays a preference value should one exist for a column within the table in focus.
At line 72 changed one line
[{If var='loginstatus' contains 'authenticated'
At line 74 removed 3 lines
----
![Discussion|Edit:Internal.DETAILED CHANGE AUDITING]
[{InsertPage page='Internal.DETAILED CHANGE AUDITING' default='Click to create a new discussion page'}]
At line 78 changed one line
}]
----
![Notes|Edit:Internal.DETAILED CHANGE AUDITING]
[{InsertPage page='Internal.DETAILED CHANGE AUDITING' default='Click to create a new notes page'}]
This page (revision-27) was last changed on 26-Nov-2021 10:22 by rforbesTop