The feature that the consultant should recommend to improve performance and address users’

concerns is chaining. Chaining is a property that allows an Integration Procedure Action element to

run asynchronously in the background, without blocking the user interface. The consultant can use

chaining to execute the long-running process in parallel with other actions or steps in the OmniScript,

and notify the user when it is completed. This will improve the user experience and reduce waiting

time

The two reasons that explain why Integration Procedures are recommended as the first choice of

data sources for FlexCards and OmniScripts are: they future-proof your front-end design and they

combine multiple actions into a single server call. An Integration Procedure can abstract the data

source from the front-end design, making it easier to change or update the data source without

affecting the FlexCard or OmniScript. An Integration Procedure can also execute multiple DataRaptor

actions, such as Extract, Transform, and Load, and also invoke REST or SOAP services in one call,

reducing the number of requests and processing time

DataRaptors are OmniStudio data tools that can perform various functions on data, such as reading,

writing, transforming, and validating. They can work with Salesforce data and external data sources.

The two functions that can be performed by DataRaptors are:

Transform data: DataRaptors can use transformation rules to manipulate data, such as changing the

format, applying calculations, mapping values, etc.

Read and write data to Salesforce: DataRaptors can use SOQL or SOSL queries to read data from

Salesforce objects and fields, and use DML operations to insert, update, delete, or upsert data to

Salesforce.

The functions that cannot be performed by DataRaptors are:

Combine requests into a single response: DataRaptors cannot aggregate multiple requests from

different sources into one response. This can be done using Integration Procedures, which can

orchestrate multiple DataRaptors or REST calls into a single process.

Read and write data to external systems: DataRaptors cannot directly access external systems or

APIs. They need to use Integration Procedures or REST elements to invoke external services and pass

the data to or from DataRaptors.

The most efficient approach that the consultant can recommend to the business to meet this

requirement is to add a new Step element with Input elements. A Step element can group related

fields and elements in an OmniScript, and display them in a page or a section. An Input element can

display a field for the user to enter data, such as text, number, date, etc. The consultant can use a

Step element to add a new page or section to the OmniScript, and then use Input elements to collect

the additional customer information

The consultant should recommend adding a Set Errors element to meet this requirement. A Set

Errors element can display an error message and prevent the OmniScript from proceeding if certain

conditions are not met. The consultant can use a Set Errors element to check if the email address

field is empty when the agent selects the checkbox to email the receipt. If it is empty, the Set Errors

element can show an error message and direct the user to return to the first step and enter the

customer’s email address

Below is the formatted question with a 100% verified answer based on official Salesforce OmniStudio

documentation, including a comprehensive explanation and

.

The two elements that the consultant should recommend for this step of the process are: Radio and

Currency. A Radio element can display a list of options for the user to choose from, such as payment

type. A Radio element allows only one option to be selected at a time, and can also have icons for

each option. A Currency element can display a field for the user to enter a currency value, such as

payment amount. A Currency element can also have validation and formatting options, such as

minimum and maximum values, decimal places, etc

The tool that the consultant should recommend to meet this requirement is Lightning web

components. Lightning web components are custom HTML elements built using HTML and modern

JavaScript. They can be used to create rich and interactive user interfaces that display data from

various sources and allow users to take actions. In this case, a Lightning web component can be used

to display customer 360° information in a console using FlexCards, OmniScripts, or other

components. Omniscript is not a tool, but a type of component that can be used to create guided

interactions. Visualforce Page is not suitable for this requirement, as it is a legacy technology that

uses server-side rendering and does not support modern web standards. FlexCards are not a tool,

but a type of component that can be used to display contextual data on record pages.

The FlexCard feature that the consultant should recommend to meet this requirement is a Datatable

element with the Group By property. A Datatable element is an element that can display data in a

tabular format, with columns and rows. The consultant can use a Datatable element to display the

cases for an account, with columns for case status, case number, subject, etc. The Group By property

is a property that allows grouping data by one or more fields, such as case status. The consultant can

use the Group By property to organize the cases by case status, so that Escalated cases appear first,

followed by Active and Closed cases

The two actions that are necessary to design this solution using an Integration Procedure are

DataRaptor Post and DataRaptor Extract. A DataRaptor Post is an action that can write data to a

Salesforce object or invoke a Salesforce API. The consultant can use a DataRaptor Post action to

create an event (platform event) using account information. A DataRaptor Extract is an action that

can retrieve data from a Salesforce object or invoke a Salesforce API. The consultant can use a

DataRaptor Extract action to get the account information from Salesforce