Overview
- What is the Audit Concept?
- Audit embodies the tracking and recording of key events during the operation of a Site (including database table modifications, etc.)
- Why use the Concept?
- It allows authorized Administrators to diagnose why a particular element (Match, User, Event, etc.) ended up with particular field values and the sequence of events that led to it.
- How is the concept implemented?
- Whenever someone updates, deletes, or adds information to the Database or another key processing point is encountered, the action is recorded in the Audit table. Authorized Administrators can use the Administrator: Manage-Audit function to search and review these entries.
Comments
You should note the following special aspects of the Audit mechanism:
- Audit entries are retained in the online database for a fixed period of time. The Site automatically deletes Audit entries that exceed the fixed limit (established via Setting=DeleteAudit).
- Each Database Table contains a unique internal Key that identifies a specific Element within the Table. This "key" is stored in the Audit information and permits you to select only those Audit entries that apply to a specific element. This unique Key value is unique within the context of a single Database Table.
- User
actions are tracked by recording the specific User Key for the User completing the change. If you delete a User AFTER that User has done an auditable action, you will not be able to display the User's name in the Audit table.
It is also possible for the Webmaster to customize which Audit points are recorded by manipulating the context of Setting=Audit (see the RidgeStar Manual: Settings-Audit
for more information.
