Audit change details¶
Open the eye action or double-click a multi-change row in Audit History. Audit Details shows the event summary followed by its recorded field-level changes.
| Column | Meaning |
|---|---|
| Field | Friendly label for the affected value or relationship. |
| Old Value | Recorded value before the action, when applicable. |
| New Value | Recorded value after the action, when applicable. |
| Type | Field set, field changed, relationship changed, association added or removed, module change, notification sent, or another recorded change type. |
Interpret blank values¶
A blank Old Value often indicates a value was first set or an association was added. A blank New Value can indicate a value was cleared or an association was removed. Use the Type and parent event action together; do not interpret a blank column by itself.
Some relationship values are resolved to a friendly current name when the related record still exists. If it no longer exists or cannot be resolved, the grid may show a stored technical reference or identifier instead. Because a resolved label can reflect the related record's current name, use the event timestamp and identifier when historical naming matters.
Binary images, uploaded templates, and similar payloads are represented without exposing their complete stored content. The history can establish that protected data changed without reproducing the original file.
Why Details is unavailable¶
The details action appears only when an event has more than one stored change. A single change is summarized directly in the parent grid, and some workflow events contain only a stored summary with no field rows.
Audit coverage also depends on the workflow that wrote the record. Absence of a field row does not prove that no surrounding application or integration activity occurred. Correlate the audit entry with AllBox Activity Logs, health events, access or LPR transactions, provider logs, and the affected module's record history as appropriate.
Capture an audit finding¶
For an internal investigation or support escalation, record:
- the site or client and source record;
- event date and displayed time zone;
- action and user;
- parent summary;
- affected field names and relevant old and new values;
- any associated record identifiers.
Do not copy passwords, tokens, recording URLs, personal data, or sensitive infrastructure details into an unrestricted ticket or message.