To improve the performance and avoid hitting Governor limits, the consultant should replace the DataRaptor Extracts with DataRaptor Turbo Extracts and combine them into an Integration Procedure. DataRaptor Turbo Extracts are optimized for speed and efficiency, and can retrieve large amounts of data without using SOQL queries. An Integration Procedure can execute multiple DataRaptor actions in one call, reducing the number of requests and processing time

 The two FlexCard features that the consultant should recommend to meet this requirement are: Flyouts and Responsive property. A Flyout is a pop-up window that can display additional information or actions for a FlexCard. The consultant can use a Flyout to show the list of past service dates for each product, without cluttering the main FlexCard. The Responsive property is a property that determines how a FlexCard adapts to different screen sizes and orientations. The consultant can enable the Responsive property to make the FlexCard display well on mobile devices, such as tablets or phones

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.

The number of different data sources that can be configured using FlexCards in this scenario is 6. A FlexCard can have one data source per state, and a state can have multiple child FlexCards, each with its own data source. Therefore, the parent FlexCard can have one data source for its state, and each of the 5 child FlexCards can have a different data source, making a total of 6 data sources

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.

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 two FlexCard features that the consultant should recommend to meet these requirements are Datatable and Repeat Block. A Datatable element can display a list of records in a tabular format, with columns for each field and rows for each record. The consultant can use a Datatable element to display the contacts for an account, with options to edit or send a message. A Repeat Block element is a container that can display multiple instances of a FlexCard based on a data source. The consultant can use a Repeat Block element to display a FlexCard for each contact, and use a condition to apply a blue border for the primary contact

The FlexCard functionality that can be used to meet this requirement is Conditional View. A Conditional View is a property that determines whether a FlexCard element, such as a field or an action, is visible or hidden based on certain conditions. The consultant can use a Conditional View to show or hide the reopen case action based on the status of the case

FlexCards are used to display contextual customer information in a compact and customizable way. They can also provide access to related processes or actions. In this scenario, the features that the consultant should recommend are:

• Actions: These are buttons or links that can launch OmniScripts, DataRaptors, or other processes from the FlexCard. They can help the users to perform tasks related to the customer information displayed on the FlexCard.
• Custom Styles: These are CSS classes that can be applied to the FlexCard elements to match the company’s color scheme and fonts. They can help the users to have a consistent and branded user interface.
• Data Tables: These are elements that can display tabular data from one or more data sources on the FlexCard. They can help the users to see relevant data in a structured and sortable way.

The features that the consultant should not recommend are:

• Menu Elements: These are elements that can display a list of options or submenus on the FlexCard. They are not suitable for this scenario because they do not provide access to processes or actions, but only to other FlexCards or pages.
• Newport Design System: This is a design system that provides a set of predefined styles and components for OmniStudio applications. It is not suitable for this scenario because it does not match the company’s color scheme and fonts, and it may require additional customization.

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 type of state that the consultant should recommend to allow users to create a new case from the canvas is New Card State. A New Card State is a state that allows creating new records in a FlexCard using an OmniScript or an Integration Procedure. The consultant can use a New Card State to enable users to create a new case from the canvas, by invoking an OmniScript or an Integration Procedure that writes data to the Case object in Salesforce.

The feature that can be used to meet this requirement in an Integration Procedure is Loop Block. Loop Block allows the designer to iterate over a collection of data and perform actions on each item. In this case, a Loop Block can be used to loop over each contact record in the list and perform a multi-step calculation using Calculation Actions or Calculation Procedures. Batch Action is not a feature in Integration Procedure, but a type of Action element that can perform bulk operations on data. Conditional Block is used to specify a condition that determines whether the actions inside the block will run or not. DataRaptor Transform Action is used to transform data from one format to another using templates.

 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

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.

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 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.

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 calculation engine will select which calculation procedure to run based on Priority. Priority is a field on the calculation procedure object that determines the order in which calculation procedures are executed when there are multiple active ones for a given date. The lower the priority number, the higher the precedence. Date modified, Sequence, and Date created are not factors that affect the calculation procedure selection logic.

 The state that will be displayed at runtime if two of the states’ condition are true is the state with a true condition that has the highest priority. Priority is a field on the state object that determines the order in which states are evaluated when there are multiple states with true conditions. The lower the priority number, the higher the precedence. The position of the state on the canvas or the order of evaluation does not affect the state selection logic.

The solution that the consultant should recommend to efficiently meet these requirements is to create an OmniScript that uses the reusable property to update contact data and embed it in other OmniScripts. A reusable OmniScript is an OmniScript that can be embedded in another OmniScript as a sub-process. This way, the consultant can create one OmniScript that updates contact data in a consistent way, and then use it in multiple OmniScripts that need to update contact data at different points in the process. This will improve the design and maintenance of the OmniScripts

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

Step elements are used to organize the OmniScript into one or more pages. They define the layout, navigation, and visibility of the OmniScript elements. They can also have pre- and post-actions that can execute DataRaptors, Integration Procedures, or other processes before or after the user completes the step.

The other options are not correct because:

• Allows the user to input data: This is not the purpose of Step elements, but of Input elements, such as Text, Number, Date, Picklist, etc.
• Groups elements that extract data: This is not the purpose of Step elements, but of Data Source elements, such as DataRaptor Extract, Integration Procedure Extract, etc.
• Enables the use of repeatable blocks: This is not the purpose of Step elements, but of Repeatable Block elements, which allow the user to add or remove multiple instances of a group of elements.

 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

The FlexCard feature that the consultant should recommend to address this issue is Flyouts. A Flyout is a pop-up window that can display additional information or actions for a FlexCard. The consultant can use Flyouts to show some of the data elements and actions that are not essential for the main view of the product information, such as product details, specifications, reviews, etc. This way, the consultant can reduce the clutter on the main FlexCard and improve the user experience

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.

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 correct way to design the FlexCard to meet this requirement is to create two states, one for mobile devices and another for non-mobile devices. States allow the designer to define different layouts and behaviors for the same FlexCard based on conditions. The width of the fields can be adjusted for each state using the Size property. Enabling the Responsive feature on the field elements would not change their width, but only their alignment. Enabling the Mobile-First feature in FlexCard settings would not affect the width of the fields, but only the order in which they are displayed. Creating two FlexCards, one for mobile devices and another for non-mobile devices, would create redundant code and maintenance issues.

The consultant should design the solution using OmniScripts and Integration Procedures to meet these requirements. An OmniScript is a tool that can design customer interactions using elements and actions. The consultant can use an OmniScript to create the guided process for the customers. 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 Integration Procedures to retrieve data from Salesforce as well as external systems, and store it in a JSON object for display or processing in the OmniScript