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

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

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
3 26-Nov-2021 10:22 1 KB JEscott to previous
2 26-Nov-2021 10:22 119 bytes RForbes to previous | to last
1 26-Nov-2021 10:22 74 bytes JMyers to last

Page References

Incoming links Outgoing links
CONTEXT_1
CONTEXT_1

Version management

Difference between version and

At line 1 changed one line
CONTEXT_1 is an optional 4000-character alphanumeric field.
CONTEXT_1 is a field that will hold (in XML format) the Parent Table Context information; this is based on the Unique Keys of the changed record and its parents. This field will show the person code, candidate code or recruiter code of the user logged in making the change.
At line 3 changed one line
[CLEANUP]
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.
----
![Notes|Edit:Internal.CONTEXT_1]
[{InsertPage page='Internal.CONTEXT_1' default='Click to create a new notes page'}]
This page (revision-3) was last changed on 26-Nov-2021 10:22 by JEscottTop