A formula element allows the developer to define formulas using functions and operators to manipulate data in an OmniScript. The output of the formula element can be displayed to the user immediately in the current step using a display element. The CONTIF function counts how many times a value appears in a list1. A Calculation Action element executes a calculation procedure and returns the output as a JSON object. A Set Values element assigns values to variables or fields in an OmniScript. A Range element defines a range of values for a variable or field in an OmniScript1. Based on best practice, a formula element is the most suitable element to use the CONTIF function in this scenario.

When an OmniScript receives incomplete data from an Integration Procedure, the issue is typically in Response JSON path mapping or naming mismatches.
* A. The missing data is trimmed in the Integration Procedure Action Response JSON Path - If the Response JSON Path only points to part of the structure, any nested or unrelated values are excluded from the output.
* B. The element name for the missing data does not match the JSON node key in the Integration Procedure Response - OmniScript expects a matching node name to bind the data to UI elements. If the key doesn't match, that field will appear blank.
Incorrect Options:
* C. Preview Input Parameters are only for testing in the Integration Procedure editor; they don't affect runtime execution.
* D. Even if the JSON from the Integration Procedure Action is different from the original IP input, it would cause a failure or unexpected data, not necessarily missing specific values.
:
Salesforce OmniStudio # Integration Procedures # JSON Path and Data Binding

In OmniStudio, the Invoke Mode: Fire and Forget setting allows an OmniScript to call an Integration Procedure asynchronously, meaning it does not wait for the response to complete before continuing user interaction.
* C. Invoke Mode Fire and Forget - This is the correct setting. It's designed specifically for use cases where the user experience should not be blocked by backend processing.
Incorrect Options:
* A. Use Future is not a valid OmniScript configuration option.
* B. Invoke Mode Non-Blocking is not an official setting in OmniStudio terminology.
* D. Toast Completion is a UI notification setting and does not impact execution behavior.
:
OmniStudio Developer Guide # Integration Procedure Actions in OmniScripts

The Use Data JSON property must be selected in the properties of the Type Ahead Block in order to display the fetched data in the fields. The Lookup Mode property is used to specify the type of lookup to perform. The FirstName, LastName, and BirthDate fields can be placed inside or outside the Type Ahead Block. The typeHead key is in the correct format.

The Expression Set component in OmniStudio allows developers to perform calculations using steps such as Aggregation, Calculation, and Sub Expression.
* C. Add an Aggregation Step as SUM(BasePrice) - This is correct. Aggregation steps are specifically designed to perform functions like SUM, AVG, COUNT, MIN, MAX over collections (arrays) of data. In this use case, summing the entire BasePrice array is best handled using an Aggregation Step.
Incorrect Options:
* A. Sub Expression Step is used to combine or manipulate previously calculated values, not to aggregate across an array.
* B. Calculation Step is used for row-level calculations, not aggregation across multiple rows.
:
Salesforce OmniStudio Documentation # Expression Sets # Aggregation Step