Pass the Salesforce Salesforce Developer OmniStudio-Developer Questions and answers with CertsForce

 In a calculation procedure, the output of a calculation step must be included in the calculation output in order to be used in an aggregation step. The calculation output defines the variables that are available for aggregation

The best practice for configuring the Input JSON for a DataRaptor Load is to copy the Input JSON from the OmniScript {Data} modal. This ensures that the Input JSON matches the data structure and format of the OmniScript data. The DataRaptor Action Debug node may not have the same data as the OmniScript data, and building the Input JSON node by node in an editor or in the DataRaptor Designer may introduce errors or inconsistencies.

FlexCards support embedding a custom Lightning web component through the Custom LWC element. The developer should drag the Custom LWC element onto the FlexCard canvas and configure the component name so OmniStudio knows which Lightning web component to render. Using an HTML element with an lwc tag is not the supported declarative method and can create security, rendering, and maintenance problems. An Action element is used to trigger behavior such as launching flows, OmniScripts, or navigation, not to host an LWC visually inside the card. Option D is also wrong because the configuration does not point to a “Card” property for the Lightning web component. The required implementation is the Custom LWC element with the component name configured.

================

 According to the OmniStudio Developer Guide, “If multiple states have true conditions, the state that is closest to the top of the FlexCard canvas displays.” Therefore, the correct answer is A.

A FlexCard is the correct front-end component for a single, focused view on a Contact record page. The data may come from Salesforce and an external grant management system, and an Integration Procedure can be used behind the scenes to aggregate that data. However, the question asks which OmniStudio tool should retrieve and display the combined information in a compact record-page view. A Data Mapper Transform reshapes data but does not provide the visual record-page card. A Calculation Procedure performs calculation logic, not case-manager display. OmniScript is better for guided multi-step processes, not quick contextual viewing. Salesforce documentation confirms that FlexCards can be configured with data sources, including Salesforce or external databases, and can display contextual information on record pages.

================

 A Set Values Action in a Value field and a Remote Action in an Additional Output value field can execute a function like CONCAT or DATEDIFF by using the syntax {{function(parameters)}}. For example, {{CONCAT(‘Hello’, ‘World’)}} or {{DATEDIFF(‘2021-01-01’, ‘2021-01-31’)}}.

The LWC PubSub Message flag in the Set Values action of the parent OmniScript enables the parent OmniScript to send data to the embedded OmniScript using a custom event. If this flag is not set, the data will not be passed to the embedded OmniScript

According to the Integration Procedure Actions page, “To pass data from a Set Values action to a DataRaptor action, add the Set Values action name to the Additional Input field of the DataRaptor action.” 

The best available answer is A, but the wording is not perfect. The safe testing pattern is to avoid changing the published cache configuration used by production users. Changing Cache Duration to 0 or disabling the Cache property would alter runtime behavior for everyone using that active Integration Procedure. Changing Type/SubType is also a bad workaround because it changes the component identity and can break callers. A throwaway test input is the least disruptive option because it lets the developer create an isolated request path for testing rather than clearing or disabling shared production cache. In a real implementation, the test value must affect the effective cache signature; if an explicit Cache Key Property is configured and the throwaway value is outside that key, it will not bypass the cached entry.

================

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