The consultant should add an Integration Procedure Action inside Step 3 to meet the requirements. An Integration Procedure Action can execute an Integration Procedure that invokes a REST API and retrieves the product price. The Integration Procedure Action can be configured to run automatically when Step 3 is loaded, and display the price in a field or label element

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 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 features that the consultant should highlight to address IT's concerns are Custom Styles and FlexCard Designer. Custom Styles are a feature that allows applying custom CSS properties to an OmniScript or a FlexCard element. Custom Styles do not require any coding skills, and can be easily configured using a graphical interface. FlexCard Designer is a tool that allows creating and editing FlexCards using a drag-and-drop interface. FlexCard Designer also does not require any coding skills, and can be used by anyone who has access to OmniStudio tools

In OmniScript, pages or groups of fields can be controlled based on the choices made by the user by using the Conditional View property on a Step or Block element. A Conditional View property is a property that determines whether a Step or Block element is displayed or hidden based on certain criteria, such as data values or user roles. The consultant can use the Conditional View property to show or hide different pages or groups of fields in the OmniScript depending on the user's input