Audit Trail Purging

For privileged users, the Purge tab is visible in the Audit Trail module. This tab is visible when the Audit Trail is opened from the Enterprise and the logged-in employee is associated with an Enterprise Role with the option, Purge Audit Trail, enabled. From this tab, the logged-in user can remove old records from the Audit Trail table in the database.

In the date field, users can select a date whereby records that are dated prior to that date are purged. For example, when this field is set to October 30, 2015, all records dated from October 30 and earlier are deleted. Note that records are deleted based on the UTC date of the Audit Trail record.

In addition to this manually initiated purge, the Data Transfer Service (DTS) purges Audit Trail records automatically.

Sub-record Formatting

A sub-record is any record that is added/removed to primary records. Some sub- record examples include Touchscreen Keys, Menu Item Group detail rows, and workstation devices. All sub-record modifications are considered edits. For example, if a touchscreen key is added to screen #10, this logs as an Edit to screen #10.

Note:

For most records, the index included in the brackets for a sub-record is a useful number. For instance, “Key [30]” shown in these examples refers to the 30th key added to the screen. For some records, there is no useful indexing field. For example, Menu Item Groups and CAL Package deployment rows do not have any type of object number that defines the order of the sub-records. When these records log to Audit Trail, additions are logged as index [0]. Deletions and edits to these records are listed with the index of the database primary key for the sub-record.

When a sub-record is added, the Audit Trail shows:

• Field: Name and number of the sub-record, followed by the field that changed (for example, Key [30]: Legend).

• Old/New Value Fields: The old and new values of the field. When a sub-record is deleted, Audit Trail shows:

  • Field: Name and number of the sub-record (for example, Key [30]).

  • Old Value: A description of the sub-record. For touchscreen keys, this is Function: 7-1, Legend: Cash. This text gives a user enough information to know what was removed. In this example, a key that used Tender #1 with the legend Cash was removed.

  • New Value: (removed)

Long Text in the Old/New Value Fields

• The Old Value and New Value fields can hold only up to 2000 characters. If the Old/New value exceeds this length, the text is logged as the first 1980 characters plus the text “....”.

• If a value is too long to read in the Audit Trail results grid, it can be easily viewed if the user expands the row height.