certified-omnistudio-consultant Sample Questions & Answers

For a DataRaptor Load to perform an 'upsert' (update an existing record), it must be provided with the Salesforce Record ID. If the Id field is not mapped or is null in the input data, the DataRaptor will perform an 'insert' and create a new record. The most common cause is an incorrect JSON path mapping for the Contact's Id field from the OmniScript data.

The publish-subscribe (Pub-Sub) event model is the standard method for communication between sibling components, like two FlexCards on the same page. The 'Recent Cases' FlexCard would configure an action (e.g., on record selection) to publish an event on a named channel, passing the Case Id in the payload. The 'Active Policies' FlexCard would have an Event Listener configured to listen on that same channel, receive the Case Id, and store it for use in its own actions.

A Conditional Block is used to execute a set of actions based on whether a condition evaluates to true or false. In this scenario, the consultant would place a Conditional Block after the credit check API call. The condition would evaluate the credit score (e.g., CreditScore > 700). The actions to extract 'Premium' offers would be placed inside the block to run if the condition is true, and the 'Standard' offer extraction could be placed in an 'Else' part of the block or after it with an opposing condition.

The Conditional View property, available on most OmniScript elements, is the standard, declarative way to show or hide an element based on the value of another element in the script's JSON. The consultant would set the Conditional View on the sensitive questions to only render if the consent checkbox element from the previous step has a value of true.

Creating a separate, reusable OmniScript for the common functionality is a core best practice. This child OmniScript can then be embedded into any parent OmniScript using the 'OmniScript' element. This approach ensures that if the address validation process changes, it only needs to be updated in one place, promoting maintainability and consistency.

OmniScript is specifically designed for creating guided, multi-step user processes. It natively supports pre-population of data, complex branching logic, a large number of input fields across multiple steps, and actions to generate documents. A FlexCard is for displaying data, not for multi-step data entry. An Integration Procedure is a server-side process with no user interface.

The Loop Block is designed to iterate over a list of items. It includes built-in functionality for batching, allowing the consultant to specify a 'Batch Size' (e.g., 50). The actions inside the Loop Block, including the HTTP Action to call the external API, will then be executed for each batch, effectively managing the API calls and preventing rate limit errors.

The core function of a DataRaptor Transform is to map data from a source structure to a target structure. In the 'Transforms' tab, you define these mappings. To rename a field, you simply specify the source field's JSON path in the 'Input JSON Path' column and the desired target field's JSON path in the 'Output JSON Path' column.

The Multi-select input element is specifically designed to allow users to choose one or more options from a list. It can be populated dynamically from a data source like a DataRaptor Extract. The Radio and Select elements only allow for a single selection. The Edit Block is for editing fields within an array of data, not for selecting from a list of options.

FlexCards support caching at the card level. By enabling caching and setting a TTL (e.g., 3600 seconds for one hour), the data from the Integration Procedure will be stored in the cache. Subsequent loads of the FlexCard within the TTL period will retrieve data from the cache instead of re-executing the entire Integration Procedure, significantly improving performance.