v4.15.0 - Winter '25 Release (API v62.0)

[jongpie]

Core Unlocked Package Changes

Winter '25 Release Upgrade

• Bumped all metadata to API v62.0 (Winter '25 release)
  • Also updated the list of picklist values in several 'API version' picklist fields on Log__c and LogEntry__c
• Resolved Replace compact layouts with new dynamic highlights component #733 by updating all 5 record flexipages to use the new dynamic highlights component (released in Salesforce's Winter '25 release) in place of compact layouts.
  • The compact layouts are still included in the repo, but they're now considered deprecated.

Log__c Object Changes

• Updated the flexipage LogRecordPage to use the newer component 'dynamic related list - single' instead of the older component 'related list - single' for displaying related lists
• Updated the order of fields shown on the LogEntry__c related list to have LoggingLevel__c as one of the first fields (instead of as one of the last fields)
• Updated all list views to have the existing field Log__c.ProfileLink__c
• Added new list views
  1. AllChildLogs: shows any logs that have a parent log set using Logger.setParentLogTransactionId(String) (based on Log__c.ParentLogLink__c != null)
  2. AllImpersonatedLogs: shows any logs where an admin was impersonating the logging user (based on Log__c.ImpersonatedByUsernameLink__c != null)

LogEntry__c Object Changes

• Updated the flexipage LogEntryRecordPage to use the newer component 'dynamic related list - single' instead of the older component 'related list - single' for displaying related lists
• Added 3 new formula fields on LogEntry__c that reference the existing formula fields on Log__c so that the same data can easily be shown in list views, etc.:
  1. ImpersonatedByUsernameLink__c
  2. ParentLogLink__c
  3. ProfileLink__c
• Updated all list views to have the existing field Log__c.ProfileLink__c
• Added new list views
  1. AllERRORLogEntries: shows any records where LogEntry__c.LoggingLevel__c == 'ERROR'
     • This is very similar to the existing list view AllERRORandWARNLogEntries that shows both ERROR and WARN
  2. AllImpersonatedLogEntries: shows any log entries where an admin was impersonating the logging user (based on LogEntry__c.ImpersonatedByUsernameLink__c != null)
     • This is conceptually the same as the new Log__c list view AllImpersonatedLogs mentioned above

Note: The new formula fields on LogEntry__c (ImpersonatedByUsernameLink__c, ParentLogLink__c, and ProfileLink__c) also help to circumvent an issue with the new dynamic higlights panel - even though the dynamic highlights panel is capable of referencing parent object fields, it expects the namespaced relationship Nebula__Log__r for the managed package, despite the fact that the fields themselves don't need the namespace prefix (e.g., it expects Nebula__Log__r.ParentLogLink__c, which is nonsense & inconsistent 😅). I don't want to have to make a script to add the namespace in the pipeline, and the whole thing feels like a flaw on Salesforce's side, so these formula fields are used in the dynamic highlights panel to avoid the problem.

LogEntryTag__c Object Changes

• Updated the flexipage LogEntryTagRecordPage to use the newer component 'dynamic related list - single' instead of the older component 'related list - single' for displaying related lists
• Added 3 new formula fields on LogEntryTag__c that reference the new formula fields on LogEntry__c (mentioned above) so that the same data can easily be shown in list views, etc.:
  1. ImpersonatedByUsernameLink__c
  2. ParentLogLink__c
  3. ProfileLink__c
• Updated the existing list view All to include the new fields LoggedByUsernameLink__c and ProfileLink__c
• Added a new list view:
  1. AllImpersonatedLogEntryTags: shows any log entry tag where an admin was impersonating the logging user (based on LogEntryTag__c.ImpersonatedByUsernameLink__c != null)
     • This is conceptually the same as the new Log__c list view AllImpersonatedLogs and the new LogEntry__c list view AllImpersonatedLogEntries mentioned above

LoggerTag__c Object Changes

• Enabled field history tracking on Name and UniqueId__c
• Added the standard History related list component to the flexipage LoggerTagRecordPage

LoggerScenario__c Object Changes

• Updated the flexipage LoggerScenarioRecordPage to use the newer component 'dynamic related list - single' instead of the older component 'related list - single' for displaying related lists
• Updated the order of fields shown on the Log__c and LogEntry__c related lists to have a more consistent order as other related lists & list views for those objects

Updated Permission Sets

• Updated 3 of the included permission sets to have read access to the new formula fields on LogEntry__c and LogEntryTag__c (mentioned above)
  1. LoggerAdmin
  2. LoggerLogViewer
  3. LoggerEndUser

Internal Optimizations

• Updated all Apex SObjectType and SObjectField usages of getDescribe().getName() to toString() - it's easier to read, and based on some benchmarking @jamessimone did, it's faster too 🏎️
• Updated a helper method in LogBatchPurgeController_Tests to try to avoid recurring flaky test failures due to (presumably) non-unique data being (previously) generated in parallel test methods

Dev / Pipeline Changes

• Removed old sfdx commands in README.md, related scripts, and release notes - now only sf commands are provided
  • Salesforce is beginning to fully remove sfdx commands (see issue #2974 in the CLI repo), and sf commands will be the only set of commands in the future, so it makes sense to remove references the now-partially-deprecated sfdx commands
• Added settings metadata to dev subdirectory to enable the new (beta) local dev setting for LWC in scratch orgs
  • This only impacts people working within Nebula Logger's repo (i.e., people making bugfixes & enhancements to Nebula Logger's codebase) - it doesn't have any impact to Nebula Logger itself
  • This new feature is controlled by the node enableLightningPreviewPref in nebula-logger/dev/main/default/settings/LightningExperience.settings-meta.xml

[codecov]

Codecov Report

Attention: Patch coverage is 95.45455% with 1 line in your changes missing coverage. Please review.

Project coverage is 92.73%. Comparing base (1b437ce) to head (08685a3).

Files with missing lines	Patch %	Lines
...management/classes/RelatedLogEntriesController.cls	0.00%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #794   +/-   ##
=======================================
  Coverage   92.73%   92.73%           
=======================================
  Files          75       75           
  Lines        7294     7294           
  Branches      200      200           
=======================================
  Hits         6764     6764           
  Misses        510      510           
  Partials       20       20           

Flag	Coverage Δ
Apex	94.22% <95.23%> (ø)
LWC	85.97% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.