Log record page

Nebula Logger ships two custom record pages that make each transaction and each entry immediately usable without customization.

Log__c record page

The LogRecordPage FlexiPage powers the Log__c record view. It surfaces:

• Standard fields - transaction ID, save method, user, profile, scenario, tags, start/end times, totals.
• Roll-up counts by level - TotalERRORLogEntries__c, TotalWARNLogEntries__c, TotalINFOLogEntries__c, etc. Instantly tells you how severe the transaction was.
• Related LogEntry__c list - all entries in the transaction, chronological within the log.
• Related child logs - when the transaction was linked to a parent via Logger.setParentLogTransactionId(...), the parent shows the child logs and vice versa.

Manage Log quick action

All editable fields on Log__c (owner, priority, status, comments) can be updated in one place via the Manage Log quick action. Useful in production, QA, and UAT for tracking ongoing investigation work on each transaction.

Nebula Logger auto-populates four related fields when Log__c.Status__c changes:

Field	Populated when
Log__c.ClosedBy__c	The status is moved to any “closed” status. Records who closed the log.
Log__c.ClosedDate__c	Same. Records when.
Log__c.IsClosed__c	Same. Boolean flag driven by which statuses are marked as closed in LogStatus__mdt.
Log__c.IsResolved__c	Reached a status that is both “closed” AND “resolved” (required work is done).

Customizing statuses via LogStatus__mdt

Log__c.Status__c picklist values are driven by LogStatus__mdt records. Each record defines a status name and two flags:

• IsClosed__c - closed statuses stop the log from appearing in the “open” list views.
• IsResolved__c - resolved statuses indicate the underlying issue was fixed (not just dismissed).

To add or rename statuses:

1. Update the picklist values on Log__c.Status__c.
2. Create or edit the matching LogStatus__mdt record so IsClosed__c and IsResolved__c are set correctly for the new status.

Nebula Logger reads the CMDT at runtime, so status semantics don’t require code changes.

View JSON quick action

The View JSON quick action renders the current Log__c plus all related LogEntry__c records as JSON, with a button to copy the JSON to the clipboard. Field-level security is respected - only fields the current user can view are included. Custom fields added in your org or by plugins are picked up automatically.

Log mass delete

Selected rows in a Log__c list view can be mass-deleted via a shipped List View button. Pick the rows, confirm, and Nebula Logger deletes the Log__c records and cascades to their LogEntry__c and LogEntryTag__c children.

LogEntry__c record page

The LogEntryRecordPage FlexiPage powers LogEntry__c records. It shows:

• Message, level, origin type / API name, and timestamp - the “what and when” of the entry.
• Related record snapshot - if the entry was created with .setRecord(...), the JSON snapshot of the record at log time is rendered here. Compare against the live record to see what changed.
• Stack trace and exception details - populated when the entry came from an exception.
• Tags - via the LogEntryTag__c junction. Clickable through to the LoggerTag__c records for taxonomy navigation.
• Origin details - Apex class + method, LWC bundle, Flow name, or OmniStudio process, depending on the entry’s source.

Customizing the pages

The shipped pages are a starting point. To customize:

1. In App Builder, open LogRecordPage or LogEntryRecordPage.
2. Save As under a new name.
3. Assign the new page to your Logger Console app for the profiles you want.

The shipped pages remain the default for other apps and profiles.

Where next

• Related Log Entries component - reuse the entry list on any record page.
• Investigation playbooks - workflows using these pages.