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

The Conditional View property on the Step elements is the correct client-side control. The branching depends on a value selected earlier in the OmniScript, and the constraint explicitly says not to use server-side logic. Conditional View can hide or show elements, blocks, or steps based on conditions in the OmniScript data JSON. Pub/Sub on FlexCard elements is unrelated because this is an OmniScript step-visibility problem, not inter-component messaging. An Integration Procedure conditional block would push the path decision to server-side logic, violating the requirement. A Data Mapper does not control UI step visibility. Salesforce documentation states that Conditional View hides an element or group of elements in a block or step based on specified conditions, which fits this scenario precisely.

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

The intended answer is C, but the wording is sloppy. A true HTTP 401 normally comes from the external service and usually means authentication headers, tokens, or credentials are rejected. However, OmniStudio/Salesforce outbound HTTP calls also require the target endpoint to be allowed through Remote Site Settings or an equivalent named credential setup. If the API key is confirmed correct and the available choices focus on Salesforce configuration, the most probable platform-side cause is that the external URL is not trusted in Remote Site Settings. API Access permission on the user profile does not authorize an external endpoint. Chainable execution does not cause endpoint authorization failure. Missing Set Values would affect input construction, not Salesforce’s permission to call the URL.

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

According to the DataRaptor Transform Overview page, a DataRaptor Transform can be used to “pre-populate data in PDFs used by OmniScripts”.

The JSON data structure in option C supports the card layout and follows best practices. It has a list of objects, each representing a product, with the properties “ProductCode”, “ProductName”, “ProductDescription”, and “ProductPrice”. These properties match the fields in the card layout. The JSON data structure also follows the naming convention of using camel case for property names. The JSON data structures in options A and B do not match the fields in the card layout and do not follow the naming convention.

The Remote Action node is identified by the element name configured in the Integration Procedure. Since the Remote Action is named FetchCart, the relevant Preview JSON node for that action is FetchCart. The debug-specific node, such as FetchCartDebug, is used for diagnostic details, not as the primary action node being evaluated in this question. ResponseCart and ResponseCartDebug belong to the Response Action, not the Remote Action. Salesforce documentation confirms that a Remote Action in an Integration Procedure calls the specified Apex class, method, or invocable action, and Integration Procedure actions are configured and executed as named elements in the procedure sequence.

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

The correct answer is JSON. Vlocity Build Tool, also called the OmniStudio Build Tool in newer documentation, exports and deploys OmniStudio/Vlocity DataPacks in a source-control-friendly structure. A Data Mapper, FlexCard, OmniScript, or Integration Procedure is represented as DataPack metadata, and the component definition is stored in JSON-based files, while job or manifest configuration can use YAML. DOCX is a document format and has no role in OmniStudio deployment metadata. CSV can hold tabular data, not a full component definition. XML is used in some Salesforce metadata contexts, but DataPacks for OmniStudio deployment are not typically represented as XML component files. Therefore, JSON is the correct deployment metadata format.

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

According to the DataRaptor Load Overview page, a Linked Mapping is used to “create or update multiple records in different objects that are related by lookup fields”.

The child Integration Procedure must return the full generated payload, so the Response Action must point to the full/root response instead of a narrowed child node or single response parameter. Setting the Response JSON Path to the root node is the explicit configuration in the given answer set. A Data Mapper Transform can reshape data, but it does not define the final return payload of the Integration Procedure. A single Response Parameter named Output with %AllData% is not the standard configuration. Leaving parameters blank can be acceptable in some caller configurations when the default behavior returns all data, but the question asks what to configure on the child Response Action, and the explicit root Response JSON Path is the strongest answer.

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

From OmniStudio Best Practices for Modular Script Design, OmniScript Actions are the preferred mechanism to invoke another OmniScript within a parent OmniScript. This approach enables reusability and modularization, especially when a function (like updating billing information) is common across many interactions.

A. OmniScript Action – This is the correct and standard method for embedding or launching one OmniScript from another. It allows developers to reuse common scripts without duplicating logic.

Incorrect Options:

B. Custom Action requires custom Apex or LWC development, which is unnecessary for this use case.

C. Lightning Action is typically used to invoke OmniScripts from Lightning pages, not within OmniScripts themselves.

OmniStudio Developer Guide → OmniScript Actions

The input JSON paths In the DataRaptor Load must match the JSON from the OmniScript, otherwise the data will not be mapped correctly to the Salesforce fields. ContextId must be spelled correctly in the merge code that passes the Recordld to the DataRaptor, otherwise the DataRaptor will not be able to identify which record to update. The fields that are not updated are not necessarily read only in Salesforce, as they could be editable by other means. In the DataRaptor Load, in the Preview tab, the Record is from the wrong record type has no effect on updating data in Salesforce, as it is only used for testing purposes.