v4.14.16 - CallableLogger Enhancements #791
jongpie
announced in
Announcements
Replies: 0 comments
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 @aBerean2 for some great feedback on logging in OmniStudio (see discussion #785)!
Core Unlocked Package Changes
Added 3 enhancements to the
CallableLoggerclass (used for OmniStudio logging & loosely-coupled dependencies)Resolved Log the JSON input provided for Steps in OmniStudio #788 - It now automatically appends OmniStudio's input data for OmniScript steps as JSON to the
Message__cfields onLogEntryEvent__eandLogEntry__c.In the screenshot below, a simple OmniScript has been setup with 2 steps (each of which shows some inputs), with logging actions after each step:
It now automatically stores the JSON from each of the steps & appends it to the message. Long-term, it might make sense to create a new field to store this data, but for now, appending it to
Message__cis a quick & easy way to capture the JSON.The
newEntryaction now supports setting the parent log transaction ID, using the optional argumentparentLogTransactionId.Transaction details are now returned in the output for all actions:
transactionId: The current transaction ID, returned fromLogger.getTransactionId()parentLogTransactionId: The parent log transaction ID (ornullif no parent has been set), returned fromLogger.getParentLogTransactionId()requestId: The Salesforce-generated request ID, returned fromSystem.Request.getCurrent().getRequestId()Installation Info
Core Unlocked Package - no namespace
Full Changelog: v4.14.15...v4.14.16
sf package install --wait 20 --security-type AdminsOnly --package 04t5Y0000015ocHQAQsfdx force:package:install --wait 20 --securitytype AdminsOnly --package 04t5Y0000015ocHQAQThis discussion was created from the release CallableLogger Enhancements.
Beta Was this translation helpful? Give feedback.
All reactions