OmniStudio-Consultant Salesforce Certified OmniStudio Consultant Exam (SU24) Questions and Answers

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

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

 The two OmniStudio tools that the consultant should recommend to meet these requirements are: Calculation Matrix and DataRaptor Extract. A Calculation Matrix is a tool that can perform complex calculations based on multiple input variables and output values. The consultant can use a Calculation Matrix to look up the unit price using the product code, the grade, size, and then multiply the unit price by a discount factor. A DataRaptor Extract is a tool that can retrieve data from a Salesforce object or invoke a Salesforce API. The consultant can use a DataRaptor Extract to get the product code, grade, size, and discount factor from Salesforce

Based on the user analysis exhibit, the three actions that should appear on the card are: verify a transaction, request higher limit, and make a payment. These actions have the highest frequency and importance scores among the six actions listed. The other actions, such as view credit score history, view statements, and view rewards, have lower frequency and importance scores, and can be accessed through other means

 The purpose of a DataRaptor Load is to write data to Salesforce objects. A DataRaptor Load can map data from an Interface object or a JSON object to one or more Salesforce objects, and perform insert, update, upsert, or delete operations. A DataRaptor Load can also use formulas and functions to transform the data before writing it to Salesforce

An Integration Procedure is the best data source to use for a FlexCard that needs to provide fields from both an external API and a Salesforce object. An Integration Procedure can combine multiple DataRaptor actions, such as Extract, Transform, and Load, and also invoke REST or SOAP services. This way, the FlexCard can display data from different sources in one place

The two cases where an integration procedure should be used as a data source for FlexCards and OmniScripts are: To retrieve multiple data sources in a single response and To separate the user interface from changes in the data sources. An integration procedure is a tool that can execute multiple DataRaptor actions, such as Extract, Transform, and Load, and also invoke REST or SOAP services. The consultant can use an integration procedure as a data source for FlexCards and OmniScripts when they need to retrieve data from different sources, such as Salesforce objects or external systems, and store it in a JSON object for display. This way, the integration procedure can provide multiple data sources in a single response, without requiring multiple elements or actions in the FlexCard or OmniScript. The consultant can also use an integration procedure as a data source for FlexCards and OmniScripts when they want to separate the user interface from changes in the data sources. This way, the integration procedure can handle any changes in the data sources without affecting the FlexCard or OmniScript design or configuration.

 The two OmniScript features that the consultant should recommend to meet this validation requirement are: Messaging and Formula. A Messaging element is an element that 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 Messaging element to display an error message stating that the age cannot be less than 18 if the user’s birthday indicates they are under 18 years old. A Formula element is an element that can perform calculations or validations on data values using expressions or functions. The consultant can use a Formula element to validate the user’s birthday by subtracting it from the current date and checking if the result is greater than or equal to 18 years

The correct OmniScript elements to capture the information are Select, TypeAhead, and Number. Select allows the user to choose one option from a list of values, TypeAhead provides autocomplete suggestions for address fields, and Number validates that the input is a numeric value. Radio, Multi-Select, and Checkbox are not suitable for single selection scenarios. Geolocation is not an OmniScript element, and Telephone is not a valid data type for phone numbers.

Reusable OmniScripts are OmniScripts that can be embedded within other OmniScripts to create modular and reusable components. They can be nested up to unlimited levels deep, as long as there are no circular references or conflicts between the parent and child OmniScripts.

The other options are not correct because:

• 2: This is too low and does not reflect the full potential of reusable OmniScripts.
• 5: This is also too low and does not reflect the full potential of reusable OmniScripts.
• 1: This is incorrect and does not make sense, as reusable OmniScripts are meant to be nested within other OmniScripts.

The two OmniStudio tools that should be recommended to meet these requirements are Calculation Procedure and Calculation Matrix. Calculation Procedure allows the designer to define a multi-step calculation process that can use data from various sources. Calculation Matrix allows the designer to define a table of values that can be used as inputs or outputs for calculations. In this case, a Calculation Matrix can be used to store the discount thresholds based on region and customer lifetime score, and a Calculation Procedure can be used to apply them to the orders. OmniStudio Action is not needed for this scenario, as there is no interaction involved. DataRaptor Transform is not suitable for this scenario, as it is used to transform data from one format to another.

The data source that is needed when using the TypeAhead element is DataRaptor Extract Action. A TypeAhead element is an element that can display a list of suggestions for the user to select from, as they type in a text field. A DataRaptor Extract Action is an action that can retrieve data from a Salesforce object or invoke a Salesforce API, using SOQL queries or Apex methods. The consultant can use a DataRaptor Extract Action as a data source for the TypeAhead element, to get the contact names from Salesforce and display them as suggestions

The OmniScript feature that should be recommended to meet this requirement is Conditional Views. Conditional Views allow the designer to create different paths within an OmniScript based on user responses or data values. User Roles are used to control access and visibility of OmniScripts based on user profiles or permissions. Script Configuration is used to define general settings and properties of an OmniScript. Script Profiles are used to assign different versions of an OmniScript to different user groups.

When designing OmniScripts, the best practices that should be followed to optimize performance and user experience are:

• Use a single DataRaptor to save the information: Instead of using multiple DataRaptors to update the account information after each step, it is better to use a single DataRaptor at the end of the OmniScript to save all the information at once. This reduces the number of database operations and improves performance.
• Combine the three steps into one step: Instead of having three separate steps to capture the required information, it is better to combine them into one step with a simple layout. This reduces the number of page transitions and improves user experience.

The suggestions that are not best practices are:

• Create a reusable OmniScript for this process: This may not be necessary if the process is specific to creating new billing accounts and not used by other OmniScripts. Creating a reusable OmniScript may add complexity and maintenance overhead.
• Configure the save for later property: This may not be useful if the process is short and simple and does not require the user to resume it later. Configuring the save for later property may add unnecessary storage and retrieval logic.

 A Text Block element in OmniScript can perform three functions: display links or images, apply text formatting, and format tables. A Text Block element can use HTML tags to create hyperlinks or embed images in the OmniScript. It can also use CSS properties to style the text, such as font size, color, alignment, etc. Additionally, a Text Block element can use HTML table tags to create and format tables in the OmniScript

The two actions that the consultant should recommend to the project team are replace existing APEX using DataRaptors and HTTPActions, and implement FlexCards and OmniScripts for the front-end. Replacing existing APEX using DataRaptors and HTTPActions would reduce implementation time, as these tools are declarative and do not require coding. Implementing FlexCards and OmniScripts for the front-end would ensure end-user processes are as simple as possible, as these tools provide guided interactions and contextual data. Creating new LWC templates for branding and styling would increase implementation time, as this would require coding and testing. Using existing APEX classes as data sources would not ensure optimal UX, as this would limit the flexibility and scalability of the solution.

The three elements that the consultant should include in the OmniScript design solution are: Telephone, Line Break, and Text. A Telephone element can display a field for the user to enter a phone number, with validation and formatting options. A Line Break element can insert a line break between two elements, making them display on separate lines. A Text element can display a field for the user to enter text, such as a website URL

 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

 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 consultant should design the OmniScript solution using the Save property to allow the user to stop and resume a process at a later time. The Save property is a property that determines whether an OmniScript can be saved as a draft and resumed later from where it was left off. The consultant can enable the Save property on an OmniScript to allow the user to stop and resume a process at a later time, without losing any data or progress.

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 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 OmniStudio data tool that the consultant should recommend in this scenario is an Integration Procedure. An Integration Procedure can execute multiple DataRaptor actions, such as Extract, Transform, and Load, and also invoke REST or SOAP services. In this case, the Integration Procedure can retrieve data from an external system via a REST API and store it in a JSON object for the OmniScript to display

The three tools that should be used in the solution are OmniScript, OmniStudio Action, and DataRaptor. OmniScript can be used to create a user interface for generating invoices from contracts. OmniStudio Action can be used to conditionally display the invoice generation option on the contract page based on the contract status. DataRaptor can be used to read, transform, and write data between Salesforce and external systems. Interaction Launcher is not needed for this scenario, as it is used to launch interactions from other applications. FlexCards are not relevant for this scenario, as they are used to display contextual data on record pages.

The consultant should design the FlexCards using a Parent FlexCard with multiple Child and Card Actions to meet these requirements. A Parent FlexCard is a FlexCard that can display data and actions in a card format, and also contain one or more Child FlexCards. The consultant can use a Parent FlexCard to display the account information, including account name, phone, and website. A Child FlexCard is a FlexCard that can display data and actions in a card format within a Parent FlexCard. The consultant can use multiple Child FlexCards to display the active opportunities and contracts related to the account. A Card Action is a button or a link that can invoke an OmniScript or an Integration Procedure from a FlexCard. The consultant can use multiple Card Actions to enable the user to view and renew contracts

 The OmniStudio tool that is optimized for performance and minimizes configuration time is DataRaptor Turbo Extract. A DataRaptor Turbo Extract is a tool that can retrieve data from one or more Salesforce objects using a graphical interface, without writing any SOQL queries. A DataRaptor Turbo Extract can also use filters, joins, and formulas to manipulate the data. A DataRaptor Turbo Extract is faster and more efficient than a DataRaptor Extract, and can handle large amounts of data without hitting governor limits

The two use cases that are best solved using Calculation Procedures & Matrices are: To apply the correct factor when determining a cost and To return output that is calculated differently based on the date. A Calculation Procedure is a tool that can perform complex calculations based on multiple input and output variables. A Calculation Matrix is a tool that can perform complex calculations based on multiple input variables and output values within groups. The consultant can use Calculation Procedures & Matrices to solve these use cases, because they involve applying rules and formulas to different data values and scenarios

 The three OmniStudio tools that are needed to meet these requirements are: FlexCards, OmniStudio Actions, and OmniScript. A FlexCard is a tool that can display data and actions in a card format. The consultant can use a FlexCard to display the account information and icons for each action. 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 launch guided processes for frequent tasks, such as change of plan, new sale, or loyalty. An OmniScript is a tool that can design customer interactions using elements and actions. The consultant can use OmniScripts to create the guided processes for each task

 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 OmniStudio tools that should be recommended to meet these requirements are single OmniStudio Action that invokes separate Omniscripts. OmniStudio Action can be used to conditionally launch different Omniscripts based on the record type of the contact. Omniscripts can be used to implement the verification processes for each type of contact. Specific FlexCards with Actions for each type of Contact would require creating redundant FlexCards and Actions for each record type. Multiple OmniStudio Actions that invoke separate Omniscripts would require creating redundant Actions for each record type. Single FlexCard with an Action to invoke an Omniscript would not allow for different verification processes based on the record type.