Database-Trigger-Based Audit Trails

Before Version 9 of IndySoft, it was common to create audit-trail events (much like they are now performed automatically in the client with Admin. Log Events) through database-level triggers. These triggers would specifically monitor equipment-level field changes and automatically create 'AUDITTRAIL' events. These database-level triggers are disabled in the upgrade to version 9x in favor of Admin. Log Events. These db-level triggers can be (re)enabled if the above client-level functionality is still needed by contacting IndySoft Support for the triggers specific to your installation and database platform.

Note: the potential advantage of running database-level triggers is that these triggers will catch any changes to equipment-level fields from ANY source, even manual SQL commands or external/custom utilities.

For proper display in the History grid, these database triggers require the presence of an 'AUDITTRAIL' event type in the Workflow Configuration, which is provided along with the trigger script as an IXP file that can be imported through the Workflow Configuration Module. Generally, this is simply a one-step event showing only 'Event Information' and very basic fields (event date, event time, performed by, Comments, etc.)

For details on installing the MSSQL or Oracle versions of these triggers, see:

·MSSQL - Audit Trail Setup

·Oracle - Audit Trail Setup |