OMNISTUDIO-CONSULTANT Practice Questions

The two scenarios where a DataRaptor should be used are: to retrieve an account and its related

contacts, and to merge the city and state fields into a single field. A DataRaptor is a tool that can

read, transform, and write data from Salesforce objects or JSON objects. A DataRaptor Extract can

retrieve data from one or more Salesforce objects using SOQL queries, and store it in an Interface

object or a JSON object. A DataRaptor Transform can map data from one Interface object or JSON

object to another, and apply formulas and functions to transform the data. For example, a

DataRaptor Transform can concatenate two fields into one using the + operator

The order that the consultant should design the elements of the OmniScript to meet these

requirements is: Radio Input, Date Input, HTTP Action, DataRaptor Post Action. A Radio Input

element can display a list of options for the user to choose from, such as customer satisfaction rating.

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

each option. A Date Input element can display a field for the user to enter a date value, such as call

back date. A Date Input element can also have validation and formatting options, such as minimum

and maximum dates, calendar picker, etc. An HTTP Action element can invoke a REST or SOAP service

to retrieve data from an external system, such as a list of bills from the last 5 months. An HTTP Action

element can store the response data in a JSON object for further processing. A DataRaptor Post

Action element can write data to a Salesforce object or invoke a Salesforce API, such as creating a

case with the list of bills in the case description

The OmniScript element that can be used to retrieve data from more than one source is Integration

Procedure Action. An Integration Procedure Action can execute an Integration Procedure that can

combine multiple DataRaptor actions, such as Extract, Transform, and Load, and also invoke REST or

SOAP services. This way, the Integration Procedure Action can retrieve data from different sources,

such as Salesforce objects or external systems, and store it in a JSON object for the OmniScript to

display

The consultant should recommend using a Headline element to ensure the agents can see and follow

these standard scripts. A Headline element can display a text message with an icon and a color, such

as blue for information or yellow for warning. The consultant can use a Headline element to show

the customer greeting script in the OmniScript, and instruct the agents to read it aloud

To improve the user experience, the consultant should use a Block Element with the Collapse

property enabled and a Zone Template. A Block Element with the Collapse property enabled allows

the user to expand or collapse a section of the FlexCard, which is useful for displaying a list of related

records. A Zone Template allows the consultant to define the layout and style of the FlexCard, such as

the number of columns, rows, and margins

Calculation Procedures & Matrices are used to perform complex calculations based on input data

and predefined rules. They are suitable for use cases that involve pricing, rating, scoring, or eligibility

determination. Therefore, the use cases that should be implemented using Calculation Procedures &

Matrices are:

Use a house’s address, size, and age of the building to determine an insurance premium. (This

involves rating based on multiple factors)

Use location and past usage to determine the monthly cost for an energy product. (This involves

pricing based on variable inputs)

Use risk factors for an insured item to determine different insurance product options. (This involves

scoring and eligibility based on criteria)

The use cases that should not be implemented using Calculation Procedures & Matrices are:

Use rules to determine eligible insurance products based on a house’s address and age of the

building. (This can be done using Business Rules Engine or OmniScript logic)

Use the product color and capacity to determine the price of a product. (This can be done using

simple formulas or lookup tables)

The purpose of the Messaging element in OmniScript is to display a warning to users based on

logical conditions. A Messaging element can show a message with an icon and a color, such as red for

error or green for success. The message can be configured to appear or disappear based on certain

criteria, such as field values or user actions

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 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 three functions that are performed by Action elements in OmniScript are get and update data

through APIs, send DocuSign emails for signature, and get and update data in Salesforce. Action

elements are used to perform various operations on data within an OmniScript. Display error

messages to the user is not a function of Action elements, but of Error elements. Organize data into

multiple pages is not a function of Action elements, but of Page elements.