New Release v4.7.5 - Made the behavior of Logger.setScenario() configurable via new LoggerParameter__mdt record

[jongpie]

⚠️ For orgs that are upgrading to this version & use the scenario functionality (stored in Log__c.Scenario__c): you may need to update the new CMDT record in your org, if you prefer to keep the previous behavior for setting scenarios. In previous releases, the last scenario specified in a transaction would be used, but going forward, by default, the first scenario specified will now be used.

Resolved #317 by adding a new CMDT record LoggerParameter.UseFirstSpecifiedScenario to control if the first or last specified value is used when Logger.setScenario(String) is called multiple times in the same transaction.

When the CMDT record has Value__c = 'true' (the new default value), this script will output 'first' for both debug statements:

Logger.setScenario('first');
System.debug('scenario 1==' + Logger.getScenario());
Logger.setScenario('second');
System.debug('scenario 2==' + Logger.getScenario());

When the CMDT record has Value__c = 'false', this script will output 'first' for the... first debug statement, and 'second' for the second. This configuration
provides the same behavior used in prrvious releases (buy it will not be the defauly behavior going forward)

---

This discussion was created from the release Made the behavior of Logger.setScenario() configurable via new LoggerParameter__mdt record.