Salesforce OmniStudio-Developer Dumps

The correct Output JSON Path is input:BasePrice. The required JSON places BasePrice inside the lowercase input node, so the path must preserve both the correct parent node and the exact field name casing. Option A is wrong because it uses dot notation and incorrectly lowercases BasePrice as baseprice. Option B is wrong because it uses Input with an uppercase I, while the JSON node is input. In JSON-based mappings, path and field names must match the expected output structure. Salesforce’s Data Mapper Transform documentation states that the Output JSON Path defines the desired output path and that path levels are separated using colon syntax, for example Contact:LastName. Therefore, C is the only mapping that correctly targets the BasePrice node under input.

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

The correct configuration is to disable Save for Later through the OmniScript setup configuration, not by hiding it with CSS or deleting a nonexistent structural element. Save for Later is a framework-level OmniScript capability controlled by Save Options, so the proper approach is a configuration setting in the Setup tab. Conditional View is used for OmniScript elements, but Save for Later is not a normal element placed in the script structure. Custom CSS would only hide the button visually and would be a poor, fragile workaround. Salesforce documentation describes Save and Resume behavior as an OmniScript Save Options feature and confirms that Save for Later can be enabled or disabled through configuration rather than custom UI manipulation.

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

An OmniScript and a Child FlexCard are both valid components that can be embedded in a flyout. An Integration Procedure and a DataRaptor are not components, but actions that can be performed within an OmniScript or a FlexCard.

The best design is to combine a Loop Block with calculation-oriented actions. A Loop Block iterates over each item in a data array, allowing the actions inside the block to repeat for every element. A Set Values element inside the loop can set intermediate values, reshape nodes , or apply simple formulas per array item. For more complex, multi-step calculation logic, an Expression Set Action is appropriate because it invokes a configured Expression Set and returns calculated results to the Integration Procedure. A Decision Matrix is mainly for table-driven decision lookups, not general multi-step per-item calculation. A List Action can merge or manipulate lists, but it does not perform the required calculation on every array element.

According to the Integration Procedure Actions page, a Remote Action can use a function in an Additional Output value field or in a Remote Options value field. According to the Response Actions page, a Response Action can use a function in an Additional Input value field.

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.” 

A contextual cache key partitions cached Integration Procedure data by the key value. Since the first request used AccountId = 001A, that cache entry is valid only for that contextual value. A later request using AccountId = 001B is a different context, so OmniStudio should not return the 001A response. Instead, the Integration Procedure runs again and creates a separate cache entry for 001B. This is the point of contextual caching: improve performance without mixing data across records or users. Option A is wrong because a new key does not clear the previous key. Option B is wrong because contextual keys are valid cache configuration. Option C would be a serious data leakage issue.

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

he Aggregation Step in a calculation procedure allows the developer to perform aggregate functions such as SUM, COUNT, MIN, MAX, and AVG on the output of a previous step. The developer can use this step to calculate the sum of the entire base price by specifying the field name and the aggregation function

A permission set license is an entitlement layer. The OmniStudio User PSL makes the user eligible to access OmniStudio functionality and related OmniStudio objects. It does not by itself grant every object, field, or administrator permission needed to build or manage assets. Those permissions still come from assigned permission sets such as OmniStudio User or OmniStudio Admin, plus object and field-level security. Option A is wrong because package installation and administration require separate administrative permissions. Option B is too broad and refers to general Salesforce platform access, not OmniStudio entitlement. Option C incorrectly treats the PSL as the permission set itself. The PSL’s primary purpose is licensing entitlement to OmniStudio features and custom objects.

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

Versioning a FlexCard allows the developer to make changes to the FlexCard without affecting the existing instances of the FlexCard. The developer can choose to update all instances of the FlexCard with the new version or keep them as they are. This is useful when the changes are minor and do not affect the functionality or layout of the FlexCard. Cloning a FlexCard creates a copy of the FlexCard with a new name and ID. The developer can make changes to the cloned FlexCard without affecting the original FlexCard. This is useful when the changes are major and require a different configuration or design of the FlexCard1. In this case, since all instances of the FlexCard must be updated with the changes, versioning is the best course of action.

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

The correct approach is to use the responsive sizing properties available in the element Display configuration, such as Extra Small, Small, Medium, and Large. These settings align the element with the responsive grid model instead of forcing custom widths. Newport Design System styling is intended to provide consistent visual behavior across OmniScripts and FlexCards, so using framework-supported sizing is cleaner than hard-coding CSS. Option B can add utility classes, but it is not the primary standard grid-sizing property for the input element. Option D is weaker because custom CSS makes the layout harder to maintain. Option A is unrelated because Repeat CSS is not the standard way to control horizontal grid width.

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

Two separate Group elements with mutually exclusive conditions provide the cleanest declarative control. One Group should execute only when updateBillingAddress is true and updateShippingAddress is false. The other Group should execute only when updateShippingAddress is true and updateBillingAddress is false. This enforces that only one address update path runs. A single OR condition would allow either or both flags to be true, so it cannot prevent simultaneous updates. A Try-Catch Block reacts after an error occurs; it is not the right way to express business-rule branching. An HTTP Action would add unnecessary external dependency. Integration Procedure blocks and groups are designed to run related steps conditionally, so mutually exclusive Group conditions are the correct structure.

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

The correct parameter is ContextId. When an OmniScript is launched from a Lightning Record page, Salesforce passes the current record ID into the OmniScript as a context ID. The OmniScript can then use ContextId to query related data through Data Mapper Extracts, Integration Procedures, or other actions. Using AccountId might work only if the developer manually maps that value, but it is not the standard automatic page-context parameter. recordId is common in Lightning Web Components, but OmniScript’s record-page launch behavior uses ContextId. CurrentRecord is not the standard OmniStudio parameter. Salesforce documentation explicitly states that, by default, the record ID on a Lightning Record page passes into the OmniScript as a context ID.

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

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.

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

Functions like CONCAT, DATEDIFF, and IF are supported in value fields where expressions can be parsed at runtime.

B. In a Set Values Action in a Value field – Correct. The Set Values element supports expression functions in its Value field, allowing for real-time evaluation during IP execution.

C. In a Data Mapper Action in an Input Parameters value field – Correct. Input Parameters to DataRaptors in Integration Procedures can use expression logic to dynamically compute and pass values.

Incorrect Options:

A. Output JSON Path in DataRaptor is for structural mapping, not function execution.

D. Remote Action Output fields typically receive data, not compute it.

Salesforce OmniStudio Developer Guide → Expression Functions in Integration Procedures

The Integration Procedure needs three separate responsibilities: retrieve Salesforce data, process it with Apex, and return the final response. A Data Mapper Extract Action reads Salesforce data and returns selected records and fields to the Integration Procedure data JSON. A Remote Action calls an Apex class method or invocable action, which satisfies the requirement to process data through Apex. A Response Action then returns the final data to the caller. Data Mapper Post Action is wrong because it writes data to Salesforce rather than retrieving it. HTTP Action is wrong because it calls an external REST endpoint, not an Apex class. The correct Integration Procedure design is therefore Data Mapper Extract Action, Remote Action, and Response Action.

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

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.

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.

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

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

Updating Salesforce data from an OmniScript requires a write operation, so the correct tool is a Data Mapper Load. A Data Mapper Extract reads data from Salesforce; it cannot update the Contact record. A Data Mapper Transform only reshapes data between formats and does not perform the Salesforce database update. The Data Mapper Load should include the Contact identifier and the new Phone value so Salesforce can update the correct record. When upsert behavior is needed, the appropriate field mapping must identify the key used to determine whether the record already exists. The question asks specifically about changing a Contact phone number from an OmniScript, so the correct configuration is a Data Mapper Load with the RecordId/key and updated phone value.

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

The merge code syntax for accessing an array element is %%Details:Customer|1:ID%%, where 1 is the index of the element. The index starts from 1, not 0, so the first element is Customer|1. The % sign is used for single-value merge codes, not array merge codes. The $ sign is used for variables, not merge codes.

The correct syntax for the Send JSON Path is ActionName: BlockName, where ActionName is the name of the action element and BlockName is the name of the block element that contains the output data. The other options are either missing the colon or using incorrect names.

According to Salesforce OmniStudio Integration Procedures documentation, when working with deeply nested JSON, Integration Procedures are ideal. They allow developers to flatten and manipulate JSON data, especially when handling external responses.

C. Integration Procedure – This is correct. IPs provide Response Transformers, DataRaptor Transforms, and Response Actions to reshape and simplify nested data structures for consumption by front-end components.

Incorrect Options:

A. DataRaptor Transform is used inside IPs but cannot directly handle external HTTP calls or manage complex orchestration.

B. HTTP Action Element is used inside an Integration Procedure, but by itself, it does not process or simplify the data.

D. Guided Workflow is not a recognized OmniStudio component for data transformation.

OmniStudio Integration Procedures Guide → Handling Nested JSON

According to the Integration Procedure Actions page, a Calculation Action can be used to “call a Calculation Procedure that performs calculations on input data” and a Matrix Action can be used to “call a Calculation Matrix that performs calculations on input data”. 

When testing a FlexCard data source in the designer, the developer must provide valid runtime values for context variables so the configured Integration Procedure can execute as it would at runtime. In this scenario, that means manually entering a valid Context ID, such as an Account record ID, in the Setup or Test Data Source settings and then viewing the returned data. Without a valid context value, the Integration Procedure may not receive the input required to query Account, Opportunity, and Case data. Option C is important inside the Integration Procedure design, but the question asks about testing the FlexCard’s data configuration in the designer. Option B is not generally required for SOQL. Option D is a design choice, not the key testing step.

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.

To build and modify OmniStudio components, the user needs both entitlement to OmniStudio features and permissions to create or manage the designer artifacts. The OmniStudio User permission set license provides access to OmniStudio features and objects, while the OmniStudio Admin permission set grants administrator/developer-level access to create and manage OmniScripts, FlexCards, Integration Procedures, and Data Mappers. A Salesforce platform license alone is not enough because it does not automatically expose OmniStudio designers. Option D is wrong because “OmniStudio Developer permission set” is not the standard answer in this context. Options B and C incorrectly rely on an Admin PSL combination rather than the common OmniStudio User PSL plus Admin permission set pairing. Salesforce’s OmniStudio permission guidance supports assigning OmniStudio Admin permissions for users who need to work with the designers.

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

For off-platform use, OmniStudio uses OmniOut so LWC OmniScripts and FlexCards can run on third-party websites. Salesforce documentation explains that an activated OmniScript can be downloaded as an Off-Platform LWC and then added to the OmniOut project for integration into the external application. This makes option B correct because the external site embeds the OmniScript as a Lightning Web Component artifact, not as a Visualforce page. Visualforce is Salesforce-hosted legacy UI technology and is not the primary external embedding model. A REST API could call backend logic, but it would not render the OmniScript user interface. An Integration Procedure call only executes server-side logic; it does not embed the guided OmniScript experience.

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

The Data Node field for the FlexCard is required to specify which data source will be used to populate the FlexCard. If it is empty, the FlexCard will not display any data. The Record Id in the Test Data Source settings is used to preview the layout with a specific record. If there is no Salesforce record for that Record Id, the FlexCard will not display any data either.

The wording of this question is imperfect. Official Salesforce documentation identifies the OmniStudio Build Tool, formerly Vlocity Build Tool, as the Node.js command-line automation tool designed to package, export, and deploy OmniStudio DataPacks in a source-control-friendly format. Since “OmniStudio Build Tool” is not one of the listed choices, the only command-line deployment option given is Salesforce Command-Line Interface. Visual Studio Code Integrated Terminal is merely a shell host, not a migration tool. Metadata API is a deployment API, not the OmniStudio-specific CLI named in the documentation. Change Data Capture is an event-streaming feature and has nothing to do with OmniStudio component migration. So D is the only usable answer from the provided options, but the technically precise tool name is OmniStudio Build Tool/Vlocity Build Tool.

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

The Add Response To Response JSON property on the DataRaptor Action indicates that the output of the DataRaptor should be added to the response JSON of the Integration Procedure. If this property is not set to true, the response will be empty even if the DataRaptor extracts data successfully. 

The correct tool is the Test Data and Parameters panel in the FlexCard Designer. The requirement is specifically to test the FlexCard directly in its designer with different JSON inputs before deployment. The OmniScript Test Console is for OmniScript logic, not FlexCard data rendering. IDX Workbench is a migration/deployment tool, not the FlexCard’s built-in data-testing panel. A Data Mapper Turbo Extract preview only tests the Data Mapper query output; it does not validate how the FlexCard processes different JSON structures and renders states, fields, or conditional elements. Salesforce documentation for FlexCard testing describes adding test parameters in the FlexCard Designer and previewing/debugging the card using those values, which directly supports option C.

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

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.

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

 The correct syntax for passing all of the parent FlexCard’s records to a child FlexCard is {Records}, which represents an array of records. The other options are incorrect because they either use an invalid syntax or refer to a single record instead of an array of records.

The best answer is D because the requirement combines two constraints: the OmniScript must be embedded on a third-party website and it must be prefilled using URL-passed data. An Experience Cloud page can host the OmniScript, and the third-party website can embed that page in an iFrame while passing URL parameters. Salesforce documentation confirms that OmniScript URL parameters can prefill fields and must use the c__ prefix in URL query-string format. Option A describes the parameter style, but by itself it does not explain how the OmniScript is embedded on the third-party website. Option C is the standard off-platform LWC/OmniOut-style idea, but the question specifically emphasizes URL-based prefill, which fits the Experience Cloud/iFrame pattern more directly.

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

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 DataRaptor Transform Overview page, a DataRaptor Transform can be used to “pre-populate data in PDFs used by OmniScripts”.

Margin controls spacing outside an element, so Margin Bottom is the correct property when the goal is to create or reduce space between the Text element and the Button below it. Padding controls internal spacing inside the boundaries of the selected element; it would move the text within its own box rather than primarily controlling the gap between two separate elements. Layout controls structural placement and responsiveness, not direct vertical spacing. Spacer can be used as a separate layout object, but it is not the property on the Text element itself. Salesforce’s FlexCard styling guidance separates dimensions, spacing, classes, and inline styles, and the spacing-around-element documentation specifically uses margin controls for external spacing.

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

Padding is the correct property because padding controls the internal space between an element’s content and its border. In this scenario, the developer wants to reduce horizontal space inside the FlexCard on small mobile screens, so the relevant adjustment is left and right padding. Margin would control space outside the element, between the element and surrounding elements, not inside the element. Border controls the line or visual boundary around the element. “Spacing” is too generic and is not the precise CSS box-model property being tested. Salesforce FlexCard styling documentation explains that FlexCard elements can be styled through the Style panel and CSS-related properties, and the CSS box model distinction makes padding the correct answer for internal spacing.

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

In OmniScripts, if you need to apply a function (like COUNTIF) to dynamic data and show the result immediately, the Formula element is the correct choice.

B. Formula element – The Formula element supports real-time calculation using OmniStudio expression functions (like COUNTIF, SUM, etc.) and updates values instantly on the screen without the need for server calls.

Incorrect Options:

A. Set Values element is used to set static or conditional values but doesn’t support formula evaluation.

C. Range element is used for value comparisons and conditions, not for calculations.

Salesforce OmniStudio Developer Guide → OmniScript Formula Element

The vlocity OmniScript wrapper is the correct choice when another Lightning component must dynamically pass or change runtime attributes. The standard App Builder component is easier for basic static placement, but it is not the best fit when the theme and layout must respond to values from another component on the same page. This requirement is not mainly about performance; it is about dynamic control of component attributes. Option B is only valid for simpler configuration where the administrator can choose settings at design time. Option C gives the wrong reason. Option D is true for a basic use case, but the scenario is not basic. The wrapper is designed for more flexible programmatic embedding and dynamic attribute behavior.

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

 The Send JSON Path syntax for accessing an element from an Integration Procedure structure is BlockName.ElementName. In this case, the BlockName is BlockX and the ElementName is ActionZ. The colon (:) is used to separate the input and output parameters, not the block and element names. The order of the block and element names should follow the hierarchy of the structure, from top to bottom. The Additional input parameter is not needed in this case, as it is already included in the Send JSON Path.

The Send JSON Path syntax for accessing an element from an Integration Procedure structure is BlockName.ElementName. In this case, the BlockName is BlockX and the ElementName is ActionZ. The colon (:) is used to separate the input and output parameters, not the block and element names. The order of the block and element names should follow the hierarchy of the structure, from top to bottom.

The JSON code correctly represents the step in the OmniScript Structure panel shown. The JSON code has the following properties:

The type is “Step”, which indicates that this is a step element in the OmniScript.

The label is “Step 1”, which matches the label shown in the panel.

The name is “Step1”, which matches the name shown in the panel.

The elements property is an array that contains one element, which is a text field.

The text field element has the following properties:

The type is “Text”, which indicates that this is a text field element.

The label is “Text Field 1”, which matches the label shown in the panel.

The name is “TextField1”, which matches the name shown in the panel.

The value property is an empty string, which indicates that this text field has no default value.

Navigation button labels such as Next are controlled through OmniScript setup-level label mapping/custom label configuration, not by editing each Step element or creating Navigate Actions. The Next button is part of the OmniScript framework navigation, so changing it globally for the script belongs in the setup configuration where element names and labels can be mapped. A Navigate Action is used to navigate to another page or component; it is not the framework Next button. LWC Component Override is for replacing component rendering behavior with a custom LWC, which is excessive and incorrect for a simple label change. Salesforce documentation describes OmniScript setup configuration and custom label references for OmniScript properties, supporting the setup-label approach.

The correct syntax for merge codes in Integration Procedure is {(NodeName)}, where NodeName is the name of the JSON node in the data source. The other options are either missing the parentheses or using incorrect symbols.

The Debug Console, or Test Panel, is the correct browser-based tool for testing OmniScript logic and data integration during development. Salesforce CLI and Vlocity Build Tool are deployment or source-control tools; they are not the interactive runtime testing panel inside the OmniScript Designer. Developer Console can inspect Apex and logs, but it is not the built-in OmniScript testing interface. The OmniScript designer preview/debug capability lets the developer execute actions, inspect action requests and responses, and verify how data moves through the script before deployment. Salesforce documentation specifically describes opening the Action Debugger from Preview to view and debug action request and response data, which directly matches the requirement to test script logic and integration behavior.

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

If the user already has OmniScript runtime access, the next security issue to investigate is access to the underlying Apex classes used by OmniStudio runtime operations, Data Mappers, Integration Procedures, or Remote Actions. Salesforce’s OmniStudio security checks include Apex class access enforcement, especially where Remote Actions or managed package classes are involved. Save Options would affect how data is saved, not whether the Lightning component can be accessed. Multi-language settings do not cause a permission-to-access-component error. FlexCard permissions are not the most likely cause when the problem occurs while launching an OmniScript. Therefore, the developer should verify the user’s permission sets/profile grant access to the Apex classes required by the OmniScript’s runtime and called actions.

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

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.

 Setting the collapsible property on the block element allows the user to expand or collapse the block as needed. Using a Data table element is not suitable for displaying contact information. Setting the class’’ collapsible’’ on the block element has no effect. Using a conditional FlexCard State requires a condition to be met, not a user choice.

According to the OmniScript Action Elements page, a DataRaptor Extract Action can be used to “get data from one or more Salesforce records” and an HTTP Action can be used to “get, save, or delete data through a web application programming interface (API)”. 

The minimum access is the OmniStudio User permission set license plus the OmniStudio User permission set. This user only executes guided flows; they do not build or modify OmniScripts, FlexCards, Data Mappers, or Integration Procedures. Assigning OmniStudio Admin would over-permission the user because Admin access is intended for users who create and manage OmniStudio components. A developer permission set would also be excessive and is not the minimum runtime configuration. A PSL alone is not enough because it entitles the user to the feature set, while the permission set grants usable permissions. Salesforce permission guidance states that users must have the appropriate OmniStudio permission set assigned, and the OmniStudio User assignment is appropriate for runtime users rather than designers/admins.