Bugfixes for Scenario Rules
Core Unlocked Package Changes
- Fixed #538 by changing
LogEntryEventHandler
to always saveLogEntryEvent__e
records whenLoggerSettings__c.DefaultPlatformEventStorageLoggingLevel__c
is null. Thanks to @arbokrad for reporting this issue (and patience, as it's taken about a year to get this fixed 🙃 )- When previously using the user's logging level from
LoggerSettings__c.LoggingLevel__c
as a fallback value, it could result in entries being lost if a matchingLoggerScenarioRule__mdt
exists with a lower logging level
- When previously using the user's logging level from
- Fixed some unreported issues in
Logger
withsetScenario(String)
andendScenario(String)
not properly updating the field values returned bygetUserSettings()
- Now, both
setScenario(String)
andendScenario(String)
wipe out & reload the in-memory instance ofLoggerSettings__c
(before applying any matchingLoggerScenarioRule__mdt
records) to ensure that there are not any remnants lingering when multipleLoggerScenarioRule__mdt
records have been applied to the user's settings in a single transaction
- Now, both
Installation Info
Core Unlocked Package - no namespace
Full Changelog: v4.13.15...v4.13.16
- SF CLI:
sf package install --wait 20 --security-type AdminsOnly --package 04t5Y0000015oFjQAI
- SFDX CLI:
sfdx force:package:install --wait 20 --securitytype AdminsOnly --package 04t5Y0000015oFjQAI
- Sandbox: https://test.salesforce.com/packaging/installPackage.apexp?p0=04t5Y0000015oFjQAI
- Production: https://login.salesforce.com/packaging/installPackage.apexp?p0=04t5Y0000015oFjQAI