CallableLogger Enhancements #790
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… logging & loosely-coupled dependencies)
1. It now automatically appends OmniStudio's input data for OmniScript steps as JSON to the Message__c fields on LogEntryEvent__e and LogEntry__c.
2. The 'newEntry' action now also supports setting the parent log transaction ID, using the argument 'parentLogTransactionId'.
3. Transaction details are now returned in the output for all actions, including the current transaction ID, the parent log transaction ID, and the Salesforce-generated request ID.
jongpie
added
Type: Enhancement
jongpie
temporarily deployed
to
Base Scratch Org
GitHub Actions
Inactive
jongpie
temporarily deployed
to
Event Monitoring Scratch Org
GitHub Actions
Inactive
jongpie
temporarily deployed
to
Advanced Scratch Org
GitHub Actions
Inactive
jongpie
temporarily deployed
to
OmniStudio Scratch Org
GitHub Actions
Inactive
jongpie
temporarily deployed
to
Platform Cache Scratch Org
GitHub Actions
Inactive
jongpie
temporarily deployed
to
Experience Cloud Scratch Org
GitHub Actions
Inactive
jongpie
added
the
Salesforce Feature: OmniStudio
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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()