Documentation
*Preface
*Introduction
*Versions
*Concepts
  -Accounting
  -Audit
  -Compensation
  -Confirmation
  -Directory
  -Logon
  -Location
  -Match Identification
  -MatchReport
  -Method
  -News
  -Profile
  -Ranks
  -Reminders
  -Roles
  -SelfAssign
  -Session
  -Status
  -Turnback
*Construction
*Usage
*Operations
*Questions
*Settings
*Tutorial
*Internals
*Appendices
Information
Logon

Audit

Logon  receiveidleidle  find  Goto

Shortcut LastShow How to order | Version44

Overview

What is the Audit Concept?
Audit embodies the tracking and recording of modifications to the Database Tables
Why use the Concept?
It allows authorized Administrators to diagnose why a particular element (Match, User, Event, etc.) ended up with particular field values
How is the concept implemented?
Whenever someone updates, deletes, or adds information to the Site*, 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:

  1. Audit entries are retained in the online database for a fixed period of time. Most Site's set the limit at 6 months. The Site automatically deletes Audit entries that exceed the fixed limit.
  2. Each Database Table contains a unique internal Key that identifies a specific Element within the Table. This "key" is stored in the Audit trail and permits you to select only those Audit entries that apply to a specific element. This unique Key value is only unique within a single Database Table.
  3. 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.

  ICRA