Audit Trail Behavior

Audit Trail recording exceptions

  • Trailing white space changes can be difficult to determine when looking at the Old Value and New Value columns of the grid. For example, if a user changes the text “Hot Dog” to “Hot Dog ”, the user would not be able to tell that something changed, because the Old/New values would appear to look the same. Because of this, changes of this type display the Old/New value, followed by the value in quotation marks to show where the extra space characters exist. For example, the new value for “Hot Dog” changing to “Hot Dog” appears like this: Hot Dog (“Hot Dog”).

  • Other than the name, changes in the Selection Hierarchies module are not logged to Audit Trail.

  • The configurable data for Credit Card Drivers and Credit Card Merchant Groups are displayed in the EMC using standard controls that are found throughout the EMC. However, this data is actually stored in the database in a single data column as an XML string. Because of this, changes in these modules show the Field as Configuration, and the Old/New values display the entire XML string.

  • When an Audit Trail report is taken, this activity is logged to Audit Trail. All generated Audit Trail Reports are logged as an Enterprise level activity.

Audit Trail record formatting

A sub-record is a record that is added to or removed from a primary record. Examples include Touchscreen Keys, Menu Item Group detail rows, and workstation devices. Audit Trail records all sub-record modifications as edits. For example, when a touchscreen key is added to screen 10, Audit Trail records an edit to screen 10.

Note:

For most records, the index in brackets identifies the sub-record. For example, Key [30] identifies the thirtieth key added to the screen. When a sub-record has no useful indexing field, Audit Trail records additions as index [0] and records deletions and edits using the database primary key.

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

  • Field: The name and number of the sub-record, followed by the changed field, such as Key [30]: Legend.

  • Old Value and New Value: The values before and after the change.

When a sub-record is deleted, Audit Trail shows the sub-record name and number in the Field column, a description of the deleted sub-record in the Old Value column, and (removed) in the New Value column.

The Old Value and New Value fields support up to 2,000 characters. When a value exceeds this length, Audit Trail records the first 1,980 characters followed by ..... Expand the row height to view long values in the results grid.

Translated Audit Trail values

Text is stored in the AUDIT_TRAIL database table so that an EMC user views the text in his/her language. For example, if a user from England changes Menu Item Class option 1 from ON to OFF, the data is stored in the table so that the Audit Trail report shows the name of the option in Japanese for an EMC user from Japan. (The Audit Trail report translates the text key that is stored in the database at the time the Audit Trail report is generated, using the signed in user's EmcText file.)

The following table summarizes the methods for Audit Trail internationalization.

Table 4-2 Audit Trail Translation Capabilities

Audit Trail Column(s) Description Translatable?

Employee Application Module Operation

These fields are all stored as numbers in the database. When taking the report, the number is converted to the appropriate text.

Yes

Field

The name of the field or option that was changed.

Yes

Sub-record Name

The name of the sub-record. A sub-record is something that has its own database table but is used by other records. Examples include Macro Steps, Workstation Devices, and Touchscreen Keys.

Yes

Sub-record Field

The name of the field for the sub-record. Examples include a Touchscreen Key legend and a KDS Bump Bar Scan code Value.

Yes

Old Value New Value

Displays the old/new values of a changed record.

Sometimes. In most cases, these fields are not translatable. For example, if a user changes a Menu Item Definition's SLU or name, Audit Trail determines the old/new value appropriately; there is no need for translation. Sometimes this field is translated when the change is made. For example, if a discount's Menu Level 1 is changed from ON to OFF, the text “ON” and “OFF” comes from the EmcText.xml file of the EMC handler.

Comments

The data in this field is typically not used by EMC users. It is simply a mechanism for providing more information about the audit trail record.

No