v4.13.2 - Track OrgLimits data on Log__c #647
jongpie
announced in
Announcements
Replies: 1 comment 1 reply
-
Aw yeah! Congratulations! |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
🎉 🪵 💯 Nebula Logger's 100th Release! 💯 🪵 🎉
Yet another neat milestone for the project 🥳
Core Unlocked Package Changes
Resolved Capture OrgLimits data on Log__c #630 by adding new functionality to automatically track organization limits data, returned by the class
System.OrgLimits
This data is automatically stored as JSON in the new field
Log__c.OrganizationLimits__c
You can disable storing this data, using the new
LoggerParameter__mdt
recordStoreOrganizationLimits
This data is displayed within a new "Organization Limits" tab on the
Log__c
flexipage, using a new LWClogOrganizationLimits
(shown below). The design of this LWC is intended to mimic the existing formula fields shown onLogEntry__c
that are used to track transaction limits.For comparison, this image shows the existing formula fields on
LogEntry__c
that are used to track transaction limits.Added another new
LoggerParameter__mdt
record,StoreTransactionLimits
, to control if transaction limits are retrieved from the classSystem.Limits
& stored onLogEntry__c
System.Limits
class does seem to have some overhead (namely, it uses CPU time), so being able to disable this functionality can, hilariously, help to reduce transaction limits usage.loggerPageSection
LWC changes: Fixed some padding inloggerPageSection.html
so it's more consistent with 'real' field section headersInstallation Info
Core Unlocked Package - no namespace
Full Changelog: v4.13.1...v4.13.2
sf package install --wait 20 --security-type AdminsOnly --package 04t5Y000001MkEmQAK
sfdx force:package:install --wait 20 --securitytype AdminsOnly --package 04t5Y000001MkEmQAK
This discussion was created from the release Track OrgLimits data on Log__c.
Beta Was this translation helpful? Give feedback.
All reactions