Changed OmniStudio-Consultant Exam Questions

The three tools that should be used in the solution are DataRaptor Turbo Extract, Integration Procedure, and DataRaptor Load. DataRaptor Turbo Extract can be used to retrieve all open cases that have a case type of “network issue” from Salesforce in batch mode. Integration Procedure can be used to orchestrate the data flow between Salesforce and the back-office system, as well as trigger an email to the supervisor after the cases have been submitted. DataRaptor Load can be used to write data to the back-office system using REST or SOAP APIs. OmniScript is not needed for this scenario, as there is no user interface involved. FlexCard is not relevant for this scenario, as it is used to display contextual data on record pages.

The group element that will control whether an individual action executes in an Integration Procedure is Conditional Block. Conditional Block allows the designer to specify a condition that determines whether the actions inside the block will run or not. Cache Block is used to store data in memory for later use. Try-Catch Block is used to handle errors and exceptions. Loop Block is used to iterate over a collection of data.

The consultant should consolidate the 10 client-side calls into one server-side Integration Procedure. Calling many Data Mappers directly from the browser increases network traffic, creates more round trips, complicates error handling, and exposes the UI to unnecessary latency. An Integration Procedure can orchestrate multiple Data Mapper actions and external calls in a single server-side transaction, then return a shaped response to the OmniScript. Replacing the Data Mappers with Apex is unnecessary unless the requirement cannot be met declaratively. Keeping the current design is weak architecture because client-side calls are not automatically faster. A FlexCard is a display component, not the correct orchestration layer for OmniScript data fetching. Salesforce describes Integration Procedures as server-side processes that support API calls, transformations, conditional logic, and chaining in a single server call.

================

 The two FlexCard features that the consultant should use to meet these requirements are States and OmniStudio Action. A State is a condition that determines how a FlexCard displays data and actions based on certain criteria. The consultant can use States to filter the installed products by their status and display different fields and actions accordingly. An OmniStudio Action is a button that can invoke an OmniScript or an Integration Procedure from a FlexCard. The consultant can use OmniStudio Actions to enable the agents to complete different processes for each installed product, such as pay bill, cancel service, etc