Open topic with navigation

TIBCO iProcess® Engine 11.9.1

# audit_trail

The `audit_trail` table holds information about each event that has happened to each case on the system.

## Structure

The `audit_trail` table has the following structure:

    TABLE audit_trail (
    	node_id		INTEGER			NOT NULL,
    	proc_id		INTEGER			NOT NULL,
    	casenum		NUMERIC(20)		NOT NULL,
    	type_id 	INTEGER			NOT NULL,
    	audit_date	DATETIME		NOT NULL,
    	stepdesc	VARCHAR(24)		NULL,
    	user_name	VARCHAR(64)		NULL,
    	stepname	VARCHAR(8)		NULL,
    	audit_usecs	NUMERIC(10)			NOT NULL,
    	major_vers	INTEGER			NOT NULL,
    	minor_vers	INTEGER			NOT NULL)

Column | Description
`node_id` | ID of the node that this audit event is hosted on, as defined in the nodes table.
`proc_id` | ID of the procedure that this audit event belongs to, as defined in the proc_index table.
`casenum` | Case number that this audit event belongs to, as defined in the case_information table.
`type_id` | ID of the audit event that occurred. Either:
| • | a system-defined audit event (<=`255`), as defined in the `SWDIR``\etc\``language``.lng\audit.mes` file.
| • | a custom, application-defined event (`256`-`999`), as defined in the `SWDIR``\etc\``language``.lng\auditusr.mes` file.
Note: See "Defining Audit Trail Entries" in TIBCO iProcess swutil and swbatch Reference Guide for more information about system-defined and application-defined audit trail entries.
`audit_date` | Date and time that this audit event occurred. Note: The `audit_usecs` column can be combined with this column to provide resolution to a microsecond.
`stepdesc` | If `type_id` is:
| • | <= `255`, the step description of the step that this audit event occurred to.
| • | => `256`, a user-defined string, containing for example the description of this audit event.
`user_name` | If `type_id` is:
| • | <= `255`, the name of the user who performed this audit event, as defined in the user_names table.
| • | => `256`, a user-defined string, containing for example the name of the user who performed this audit event.
`stepname` | Name of the step that this audit event occurred for. For internal use only.
`audit_usecs` | Number of microseconds since the start of the seconds value specified in the `audit_date` column. Note: On systems that have been upgraded from Version 9, for any existing cases the 6 least significant digits of the `at_id` column are copied into this column to ensure that audit trail entries remain in the correct order.
`major_vers` | Major version number of the version of the procedure that this audit event belongs to, as defined in the proc_version table.
`minor_vers` | Minor version number of the version of the procedure that this audit event belongs to, as defined in the proc_version table.

## Primary Key

None.

## Triggers

None.

## Indexes

The following clustered index is defined for this table.

Index Name | Column(s) Indexed
`idx_audit_trail_fk` | `casenum proc_id node_id`

## Table Activity

The `audit_trail` table contains one or more rows for each step of each case on the system. Rows are added, updated and deleted in the following situations.

A row is... | When...
added | an audit event occurs.
updated | never.
deleted | a case is purged.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO iProcess® Engine