Explanation:

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.

Explanation:

The three OmniScript elements that the consultant should recommend to meet these requirements are: DataRaptor Post Action, Multi-select Input, and HTTP Action. A DataRaptor Post Action 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 save the data back to Salesforce as a lead. A Multi-select Input is an element that can display a list of options for the user to choose from, such as energy products. A Multi-select Input allows multiple options to be selected at once, and can also have icons for each option. An HTTP Action is an element that can invoke a REST or SOAP service to retrieve data from an external system, such as current energy usage data. An HTTP Action can store the response data in a JSON object for further processing

Explanation:

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.

Explanation:

A DataRaptor Extract can retrieve data from multiple related objects. A DataRaptor Extract is a tool that can read data from a Salesforce object or invoke a Salesforce API, using SOQL queries or Apex methods. A DataRaptor Extract can also use filters, joins, and formulas to manipulate the data. A DataRaptor Extract can retrieve data from multiple related objects by using lookup or master-detail relationships in the SOQL queries or Apex methods

Explanation:

The OmniStudio tools that the consultant should use to design a solution to meet these requirements are: Single FlexCard with multiple actions. A FlexCard is a tool that can display data and actions in a card format. The consultant can use a single FlexCard to display the medical test reports for each patient, including the report name, date requested, and date generated. A FlexCard can also have multiple actions, such as buttons or links, that can invoke OmniScripts or Integration Procedures. The consultant can use multiple actions to enable the user to approve, print for review, or send for retest each medical test report

Explanation:

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

Explanation:

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

Explanation:

The consultant should recommend creating a specific OmniScript for each business process to improve the planned design of this OmniScript. Having one OmniScript for three different and complex sales processes will make the OmniScript too long and complicated, and will affect the performance and maintainability. Creating separate OmniScripts for each process will make them more manageable and user-friendly, and will also allow for more customization and flexibility

Explanation:

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.