-
-
Notifications
You must be signed in to change notification settings - Fork 168
Logging in Flow
Jonathan Gillespie edited this page Sep 16, 2024
·
1 revision
Within Flow & Process Builder, you can select 1 of the several Logging actions
In this simple example, a Flow is configured after-insert and after-update to log a Case record (using the action 'Add Log Entry for an SObject Record')
This results in a Log__c
record with related LogEntry__c
records.
Within Flow (and Process Builder), there are 4 invocable actions that you can use to leverage Nebula Logger
- 'Add Log Entry' - uses the class
FlowLogEntry
to add a log entry with a specified message - 'Add Log Entry for an SObject Record' - uses the class
FlowRecordLogEntry
to add a log entry with a specified message for a particular SObject record - 'Add Log Entry for an SObject Record Collection' - uses the class
FlowCollectionLogEntry
to add a log entry with a specified message for an SObject record collection - 'Save Log' - uses the class
Logger
to save any pending logs
- Assigning Permission Sets to Users
- Configuring Global Feature Flags
- Configuring Profile & User-Specific Settings
- Configuring Data Mask Rules
Manual Instrumentation
- Logging in Apex
- Logging in Flow & Process Builder
- Logging in Lightning Web Components & Aura Components
- Logging in OmniStudio
- Logging in OpenTelemetry (OTEL) REST API
ISVs & Package Dependencies
- Overview
- Optionally Use Nebula Logger (When Available) with
Callable
Interface - Require Nebula Logger with Strongly-Coupled Package Dependency
Troubleshooting
Pub/Sub with Platform Events
Persisted Data with Custom Objects
- Logger Console app
- Assigning & Managing Logs
- Using 'View Related Log Entries' Component on Record Pages
- Deleting Old Logs
Official Plugins