-
-
Notifications
You must be signed in to change notification settings - Fork 239
Query FlowDefinitionView to store additional Flow details on LogEntry__c #129
Copy link
Copy link
Closed
Labels
Layer: Log ManagementItems related to the custom objects & Logger Console appItems related to the custom objects & Logger Console appLogging Source: FlowItems related to using Nebula Logger within FlowItems related to using Nebula Logger within FlowSalesforce Feature: ReportingAnything related to reports, dashboards, and the underlying data modelAnything related to reports, dashboards, and the underlying data modelType: EnhancementNew feature or requestNew feature or request
Milestone
Description
Metadata
Metadata
Assignees
Labels
Layer: Log ManagementItems related to the custom objects & Logger Console appItems related to the custom objects & Logger Console appLogging Source: FlowItems related to using Nebula Logger within FlowItems related to using Nebula Logger within FlowSalesforce Feature: ReportingAnything related to reports, dashboards, and the underlying data modelAnything related to reports, dashboards, and the underlying data modelType: EnhancementNew feature or requestNew feature or request
Within
LogEntryEventHandler, when creating theLogEntry__crecords, it should queryFlowDefinitionViewfor additional details for any Flow entries.LogEntry__crecords being created whereOriginType__c == 'Flow', then queryFlowDefinitionViewbased onFlowDefinitionView.ApiName == logEntry.OriginLocation__clogEntry.OriginLocation__cmay not always have an accurate API name - i.e., some orgs might populate the Flow label (instead of API name), or the string in the Flow might be out of sync with the actual API name. In these situations, the code should still save the log entries & just leave any new Flow-related fields null.Some of the fields to possibly store from
FlowDefinitionVieware:ApiName,DurableId,ActiveVersionId,Description,Label,LatestVersionId,NamespacePrefix,ProcessType