v4.13.3 - Optionally Enforce Scenario-Based Logging Usage

[jongpie]

Core Unlocked Package Changes

• Resolved Add a way to enforce the usage of scenarios #645 by adding the ability to optionally enforce using scenario-based logging. This is controlled by a new LoggerParameter__mdt record, RequireScenarioUsage, and is disabled (false) by default.
  • When set to false, specifying a scenario is completely optional.
  • When set to true, a scenario is required to be set before any logging can occur. If a logging method is called &; the current scenario is null/blank, then Nebula Logger will throw a runtime exception.
• Upgraded LoggerScenarioRecordPage flexipage to use dynamic related lists for Log__c and LogEntry__c
• Added missing field permission for Log__c.TransactionScenario__c to LoggerAdmin permission set

Installation Info

Core Unlocked Package - no namespace

Full Changelog: v4.13.2...v4.13.3

• SF CLI: sf package install --wait 20 --security-type AdminsOnly --package 04t5Y000001MkEwQAK
• SFDX CLI: sfdx force:package:install --wait 20 --securitytype AdminsOnly --package 04t5Y000001MkEwQAK
• Sandbox: https://test.salesforce.com/packaging/installPackage.apexp?p0=04t5Y000001MkEwQAK
• Production: https://login.salesforce.com/packaging/installPackage.apexp?p0=04t5Y000001MkEwQAK

---

This discussion was created from the release Optionally Enforce Scenario-Based Logging Usage.