v4.16.5 - Capture Apex Cursor Transaction Limits #898
jongpie
announced in
Announcements
Replies: 1 comment
-
|
Super excited to see this go live in v4.16.5 🎉 Thanks for all the support and collaboration throughout the process — I had a great time working on this and would love to contribute more in the future. Thanks @jongpie 🙌 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Thanks to @vikashkrml for working on this release in PR #892 🥳👏
Core Unlocked Package Changes
Fixed #760 by adding auto-capturing of Apex cursor transaction limits for rows & fetch calls, stored in new fields on
LogEntryEvent__e&LogEntry__cAdded 4 new number fields on both
LogEntryEvent__eandLogEntry__cto capture Apex cursor limit values returned by theLimitsclassLimitsApexCursorFetchCallsUsed__c🟰System.Limits.getFetchCallsOnApexCursor()LimitsApexCursorFetchCallsMax__c🟰System.Limits.getLimitFetchCallsOnApexCursor()LimitsApexCursorRowsUsed__c🟰System.Limits.getApexCursorRows()LimitsApexCursorRowsMax__c🟰System.Limits.getLimitApexCursorRows()Added 2 new formula fields on
LogEntry__cto show the percentage used of both Apex cursor fetch calls and Apex cursor rows. This formula fields provide the same functionality as the other existing formula fields onLogEntry__cshown on theTransaction Limitstab of the flexipageInstallation Info
CoreUnlocked Package - no namespaceFull Changelog: v4.16.4...v4.16.5
sf package install --wait 20 --security-type AdminsOnly --package 04tKe0000011N4KIAUThis discussion was created from the release v4.16.5 - Capture Apex Cursor Transaction Limits.
Beta Was this translation helpful? Give feedback.
All reactions