Activity History & Audit Trails
The system logs all changes automatically. This allows managers and auditors to inspect the exact timeline of a service request — who did what, when, and exactly what data changed.
Audit Log Integrity Policy & Search Filters
Audit records are subject to strict data integrity policies to ensure auditability. Below are the CRUD constraints and search filter settings:
| Log Option | Type / Status | Allowed Users | Security Constraint / Description |
|---|---|---|---|
| Create (C) | Automated Log Trigger | System Event Hooks | Logs are automatically written on field edits, approvals, transfers, and rejections. |
| Read (R) | View History Button |
All Roles | Read-only timeline logs. Visible to anyone with permissions to view the instance. |
| Update (U) | Blocked | None | Immutable logs. Once written, descriptions and timestamps can never be edited. |
| Delete (D) | Blocked | None | Permanent history retention. Deleted instances retain their trails for compliance logs. |
| Date Filtering | Start / End Date Inputs |
All Roles | Restricts results to actions recorded within a specific timeframe. |
| Actor Search | Search Actor Name Field |
All Roles | Queries log lines to show only changes made by a specific user. |
What is Logged in the Audit Trail?
Every time a user modifies a service flow, the system records:
- Who performed the action (User name, e.g. "Author", "Approver").
- When the action was recorded (exact local date and time).
- What was changed, showing both the old value and the new value.
Smart Filtering of Changes
To keep logs clean and readable, internal system changes (like updating ID pointers, started timestamps, or system tracking values) are automatically ignored. Only changes to human-meaningful data (like custom fields, user comments, or status changes) are displayed.
How to Read Log Descriptions
Log descriptions are written in a human-friendly format to describe changes clearly. Let's look at some examples:
Example 1: Setting field values for the first time
This tells us the author set the document type to Passport and entered the document number for the first time.
Example 2: Modifying field values
This shows exactly which field was changed and shows the old value alongside the new value.
Example 3: Rejections & Reversions
This shows exactly who rejected the step, why it was rejected, and which step the flow was rolled back to.
How to View the Logs in the App
- Open the Service Flows list page.
- Locate your instance and click on the Action dropdown menu.
- Select View History.
- A modal will open displaying the timeline of all changes, sorted from most recent to oldest action.
Table Filter Reference
The activity logs view includes powerful auditing filters to find events quickly:
- Performing User: Filter logs by the specific staff member who performed the action.
- Action Type: Filter by action category (e.g. Create, Update, Delete, Clone).
- Date Range: Scopes logs to a specific start and end date.
- Search Term: Real-time lookup matching user name, step names, or field keywords.