Releases: j-fischer/rflib
Releases · j-fischer/rflib
Version 2.5.0
- Added initial version of Permission Explorer
- Fixed issue with navigation buttons in Log Monitor getting confused when searching for Log Events
Version 2.4.0
- Replaced queries for Custom Metadata Type
rflib_Global_Setting__mdt
with the new Apex API methods
Version 2.3.0
- Implemented finalizer interface support for Queueables
- Provided the ability to mask text within the collected log messages when publishing a log event
Version 2.2.0
- All metadata was upgrade to API version 50.0
- Added input field for User filter Log Monitor
- Introduced the Salesforce Request ID into the logging framework
- Added Salesforce Request ID to TraceID token to make it completely unique
- Added Log Timer actions support for Flow
- Updated unit tests for Winter 21 release where new dedicated limits for publishing platform events immediately are introduced. See https://releasenotes.docs.salesforce.com/en-us/winter21/release-notes/rn_platform_events_publish_immediate_limit.htm?edition=&impact=
Version 2.1.0
- Introduced Log Timer for LWC, Aura, and Apex to add a log statement including the duration of the timer
- Added new custom setting to set the log level for when to flush log statements after a Log Event is published, default level is NONE
- Fixed bug where the Log Reporting Level did not allow for NONE as a valid value
Version 2.0.0
Separated RFLIB package into multiple modules: RFLIB, RFLIB-FS, RFLIB-TF
- RFLIB 2.0.0 contains the core logging framework. The log event email handler got converted into a Invocable Action, which is used by a Platform Event triggered Flow to send out the email message based on the configuration in the Logger Settings
- RFLIB-FS 1.0.0 contains the Feature Switch framework and depends on RFLIB 2.0.0
- RFLLB-TF 1.0.0 contains the Trigger Framework, which depends on RFLIB 2.0.0 and RFLIB-FS 1.0.0
- All metadata was upgrade to API version 49.0.
Version 1.0.0
Initial release with logging, trigger and feature switch framework. See README and CHANGELOG for details.