OmniStudio Integration Procedures + DRs Flashcards
What are OmniStudio Integration Procedures?
They are applications used to read and write data from Salesforce and from external systems. An Integration Procedure can be called from an OmniStudio component such as an OmniScript or FlexCard, an API, or even from an Apex method.
OmniStudio Integration Procedures are declarative, server-side processes that execute multiple actions in a single server call.
What does a Cache Block do?
Saves the output of the steps within it to a session or org cache for quick retrieval
Stores frequently accessed and infrequently updated data, which saves round trips to the database and improves performance
Allows data updates without caching
Allows different cached data to expire at different times
What does a Conditional Block do?
Executes if a specified condition is true or treats the steps within it as a series of mutually exclusive alternatives
Supports branching workflows, which function like conditional views in an OmniScript
Note: this is the most basic block type.
What does a Loop Block do?
Iterates over the items in a data array, enabling the Actions within it to repeat for each item rather than requiring separate Action elements for each item
What does a Try-Catch Block do?
Lets you “try” running the steps inside the block and then “catch” the error if a step fails Returns specified output or calls an Apex class if a step within it fails
What are naming conventions for DataRaptor actions?
prefixVerbObjectDetails
Use camel case for Lightning Web Component (LWC) compatibility
How do you ensure you do not create duplicate records in Salesforce when you create your DataRaptor Load?
By defining the right field mappings in the Load DR as “Upsert” and/or “Is Required for Upsert”
Differences between DR Turbo Extract vs Extract?
DataRaptor Turbo Extract retrieves and filters data from a single Salesforce object type with support for fields from related objects. You can filter the data and select the fields to return. Unlike a standard DataRaptor Extract (which we describe next), a DataRaptor Turbo Extract doesn’t support formulas or complex output mappings.
It has two advantages over a standard DataRaptor Extract:
Simpler configuration
Better performance at runtime
What can a DR Transform do?
Convert JSON input to XML output, and vice versa.
Restructure input data and rename fields.
Substitute values in fields (all DataRaptors can substitute values).
Use DataRaptor Transforms for the following situations:
When an OmniScript must populate a DocuSign template.
When an OmniScript must fill fields in a PDF document.
Advantages to using integration procedures as data sources?
They can be versioned
Separated from Omniscript / FlexCard config (e.g. Stub data to live data)
Multiple DataSources (SF, API, Apex) can be combined in one server call.
In loop blocks, how do you iteratively reuse (recursion) a variable in Set Value block?
Define the Response JSON parameters where the Path is the source element (key) name, and the response JSON node name as an input to the element’s value field (or refer to parent node name if it’s from a different node)
