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

Explanation
The FlexCard design solution that the consultant should recommend is to add a menu element and include all the actions. A menu element can display a list of actions in a dropdown menu, with icons and labels for each action. The consultant can use a menu element to show all the 8 actions in the FlexCard, without overloading it with buttons or links. This will improve the user experience and the design of the FlexCard

The parent record ' s Salesforce ID is required to create the correct relationship between the uploaded file and the newly created parent record. Therefore, the Data Mapper Load that creates the parent record must return
/output the new record ID so the OmniScript or subsequent data action can use it to link the file properly.
OmniScripts can support file upload use cases, so option B is false. A Data Mapper Extract cannot search the user ' s local computer; it retrieves Salesforce data. The link is not guaranteed automatically in every multi- step process unless the parent record ID is available and passed into the file-linking step. Salesforce Data Mapper Load examples show that linking related records requires carrying the created parent ID into the related mapping/linking process.

Explanation
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)

Explanation
The type of DataRaptor that can be used to retrieve a list of cases filtered by the customer's asset and the last service date of the asset is DataRaptor Extract. DataRaptor Extract allows the designer to retrieve data from Salesforce or an external system using filters and relationships. In this case, a filter can be used to match the asset ID and the last service date, and a relationship can be used to join the case and asset objects. DataRaptor Turbo is not a type of DataRaptor, but a feature that enables batch mode for DataRaptor Extract. DataRaptor Load is used to write data to Salesforce or an external system. DataRaptor Transform is used to transform data from one format to another using templates.