The Button field's click events on a record's activity history now record the user who clicked and the action that ran (Create a Record, Open a Form, Open URL, or Run an Automation). Button-driven workflows that dispatch actions from a record — service-desk agents opening a ticket-creation form, GRC reviewers launching an automation to snapshot evidence, PMO leads clicking through to a linked record — now have per-user attribution in the audit trail instead of an anonymous "button was clicked" entry.
Key Highlights
- User Attribution on Every Click: Activity history now identifies the user who clicked the button by name — no more anonymous entries in the audit trail.
- Action Type on Every Click: The log entry also records which action ran — Create a Record, Open a Form, Open URL, or Run an Automation — so auditors can distinguish a link-out from an automation trigger without cross-referencing the button configuration.
- Click Events Remain Separate: Button click events continue to be logged as their own events, never grouped with other field changes on the same record — preserving the pattern that made these entries usable for audit and incident review.
- Covers Every Button Action Type: All four Button action types (Create a Record, Open a Form, Open URL, Run an Automation) capture the same enriched context.
- Covers Every View That Supports Clicks: Grid, Card, Kanban, and the record edit surface all route their Button clicks into the same enriched activity log. Extended and Table formats for Linked Records that display Button fields do too.
- No Configuration, No Backfill: Existing Button fields inherit the enriched logging automatically. No configuration migration; historical activity history entries are not backfilled.
How It Works
- Users click a Button field on a record (in Grid, Card, Kanban, the record edit modal, or an Extended/Table Linked Record display). The configured action runs the way it always has.
- Open the record's activity history. The click event now shows the user's name and the action that ran — for example, "Peter Novosel clicked Submit for Review button. Action: Run an Automation."
- Auditors, incident reviewers, and compliance teams can trace per-user attribution directly on the record's own activity history without a separate log to reconcile.
Available on all plans. No configuration required; existing Button fields inherit the enriched logging automatically.