Audit Log
View live changes made to the database by interrogating the device, operator and branch...
Last updated
Was this helpful?
View live changes made to the database by interrogating the device, operator and branch...
Last updated
Was this helpful?
You can monitor live changes made to the database by reviewing the interactions from the device, operator, and branch.
Filtering the audit log allows you to focus on specific actions or details. The screenshot below demonstrates the "Audit Log Search" modal for this purpose.
To track modifications made to a specific client, filter the Model column by Client and sort by Timestamp.
To review all actions performed by a particular actor, filter the Actor column by their name.
On Model: Monitor changes for specific models, such as Bank Account, Loan, or Client. Track the audit logs for a model to see what changes were made to it.
By User: Each operator generates unique audit log entries based on their actions within the application.
From Device: Log entries are associated with the specific device used by the operator, allowing tracking at the device level.
Of Branch: Devices are linked to specific branches, enabling tracking of actions at the branch level.
During Period: Specify a date range to narrow the results to the desired timeframe.
Blank Fields: Leaving a filter field blank will include all available results for that criterion.
To properly evaluate an audit log, users need to understand the meaning of each column in the results table to assess each record accurately.
This table displays a record of various actions performed within a system, providing information about changes made to different models by specific users over time. Each column serves a unique purpose, detailed below
Action
Indicates the type of action performed. Common actions include:
Create: A new record was added to the system.
Update: An existing record was modified.
Timestamp
Shows the exact date and time when the action was performed. Format: YYYY-MM-DD HH:MM.
Helps track when specific actions occurred, useful for auditing and troubleshooting.
Model
Specifies the category or entity that was affected by the action. Common models include:
Client, Employer, Agent, etc.
Object Description
Provides a brief description or name of the specific object affected by the action.
Example: Efficacious Foodmaker, XYZ5 Pervasive Unicorn.
Actor
The user who performed the action. Typically, it displays the user's name.
Example: Martin Meyer.
Device
Specifies the device from which the action was performed.
Format: <Environment> - <Device> (e.g., Support - Bradley (Laptop), Testing - Martin (Journey)).
App Workflow
Indicates the workflow or process associated with the action. Common workflows include:
Maintenance: Actions related to system maintenance.
Origination: Actions related to the creation or modification of objects.
Updates
Shows the number of updates or changes applied during the action.
A higher number may indicate extensive changes made to the object.
