The DataRaptor Formula tab allows the developer to define formulas using functions and operators to manipulate data. The TOINTEGER function converts a string value to an integer value. The developer can use this function to output the field value as an integer and use the formula as output

The Validation property on an OmniScript input element allows the developer to define regex patterns or logical conditions (such as value > 0) to validate user input before proceeding.

The FlexCard Player component is used to display FlexCards in a community page. The developer needs to add the FlexCard's API name to the FlexCard Player component to configure the FlexCard for deployment in a community.

The correct answer is Option B, which shows a FlexCard with a header, a body, and a footer. The header contains the title and the icon of the FlexCard. The body contains a Data table element that displays the records from the parent FlexCard. The footer contains a navigation Action that invokes an OmniScript.
Option A is incorrect because it shows a FlexCard with only a header and a body, and no footer.

In OmniStudio Integration Procedures, when referencing data from a prior step in the HTTP Action URL, the correct merge code syntax is:
* %ElementName.PropertyName%
So, referencing a value called Date from a step named SetValues must be written as:
* %SetValues.Date%
This is the format recognized by the OmniStudio Merge Language (OML) for dynamic value substitution in URLs or headers.
Incorrect Options:
* A. Invalid syntax - not recognized by OmniStudio merge logic.
* B. {{SetValues.Date}} is used in FlexCards, not in Integration Procedures.
* D. %SetValues: Date% is incorrect merge syntax due to space and colon use.
:
Salesforce OmniStudio Documentation # Merge Code Syntax for Integration Procedures