OmniStudio-Developer Sample Questions Answers

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

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

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

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.

 Checking the Send Only Additional Input checkbox allows the Remote Action element to send only the key/value pairs specified in Additional input to the Apex method. The Additional input should have the same keys as the method parameters, and the values should be set to {{InputData.node}} for each node. For example, AccountId: {{InputData.AccountId}} and ProductId: {{InputData.Details.Products}}.

A Data Mapper Transform controls output structure through its mappings. If the generated XML is flat instead of nested, the developer should first inspect the target path used in the transform mapping. Nested structures require hierarchical output paths, commonly expressed with path notation that represents parent and child nodes. If the target output paths are configured as flat fields, the transform has no instruction to create the required nested XML hierarchy. Missing formulas would affect calculated values, not the tag hierarchy. A missing root node can cause a different structural issue, but the question says output is generated and specifically flat. The best answer is therefore to correct the target path so the mapping represents the required nested schema.

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

The verified answer is A, not the mock-highlighted C. FlexCard States display based on conditions configured on the state. For this scenario, the Active, Warning, and Critical states should each have a condition that evaluates the RiskLevel value. For example, Active can evaluate RiskLevel = Low, Warning can evaluate RiskLevel = Medium, and Critical can evaluate RiskLevel = High. At runtime, OmniStudio evaluates the state conditions, and the matching state is displayed. A Set State Action on a button is user-driven and does not automatically evaluate RiskLevel. “Conditional State Logic on the Base FlexCard” is not the precise configuration item used here. A main Block state variable is also not what controls card-level state selection.

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

An Integration Procedure that calls a Remote Action depends on the referenced Apex class existing in the target org. If the Apex class is missing, the Integration Procedure cannot resolve that dependency during deployment or execution. The required fix is to deploy the Apex class first, then deploy the Integration Procedure that references it. Cache Duration has no relationship to metadata dependency resolution. Chainable configuration controls long-running transaction behavior and governor-limit handling, not missing Apex metadata. A Try-Catch Block can help handle runtime failures, but it does not solve a deployment failure caused by an absent Apex class. Salesforce’s OmniStudio deployment guidance specifically includes considerations for Apex class checks and dependencies when deploying Integration Procedures.

 An Integration Procedure Action can execute an Integration Procedure that contains multiple elements, such as DataRaptor Actions, HTTP Actions, or other Integration Procedure Actions. This can be used to save data to multiple systems, such as Salesforce and AWS Order Management, in one OmniScript element.

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.

According to the OmniScript Data JSON page, the OmniScript structure JSON defines the data elements and their properties that are used in an OmniScript. The exhibit shows an OmniScript structure JSON with six elements: AccountName, AccountNumber, AccountType, AccountOwner, ContactName, and ContactPhone. The DRGetAccountDetails action is a DataRaptor Extract action that retrieves data from the Account and Contact objects in Salesforce. The BlkContacts element is a Repeat Block that displays a list of contacts related to the account. Therefore, the JSON from the DRGetAccountDetails action that would display all six values correctly in the OmniScript structure shown is option C, which has the following structure:

{ The other options have different structures that do not match the OmniScript structure shown. Therefore, the correct answer is C.

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.

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

 Deleting a row in Version 3 will only affect that version, not any previous or future versions. The row that contains the Code CA-SF will remain in Versions 1 and 2, as well as any versions created after Version 3. The other options are incorrect because they imply that deleting a row in one version will affect other versions as well.

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

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

A DataRaptor Turbo Extract is a simplified version of a DataRaptor Extract that can retrieve data from a single object without changing the structure of the output data. It is easier to configure because it does not require defining extraction steps or JSON paths. It also has better performance at runtime because it uses a native query engine instead of a custom one

Checking the Enable Cancel checkbox in the Setup tab under Cancel Options allows the developer to enable the cancel functionality for all steps in the OmniScript. The user can cancel the OmniScript at any time by clicking the Cancel button in the top right corner of the OmniScript. Adding a navigation Action inside each step is not necessary and would clutter the OmniScript design. Setting the Component name or Element Name to ‘’Cancel’’ has no effect on enabling the cancel functionality.

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.

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

The requirement is only to show or hide a section based on a value already present in the OmniScript data JSON. That is exactly what Conditional View is designed for. It evaluates client-side conditions and controls whether a step, block, or element is displayed, editable, or required. Using an Integration Procedure would add unnecessary server-side processing because the required VIP value is already available in the OmniScript. A Data Mapper Transform is also unnecessary because there is no structural transformation requirement. Creating a new version may be part of the deployment process, but it is not the functional configuration that controls visibility. The best implementation is to place the special offers section in the script and configure Conditional View logic against the VIP member value.

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

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.

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

The contact information should be available on demand while the account information stays visible. A collapsible Block element is the cleanest FlexCard design for this: place the contact fields in a separate Block and enable the collapsible property so the user can expand or collapse that section as needed. A CSS class named collapsible is not the supported declarative configuration. A conditional FlexCard State is excessive because the entire card does not need to switch state; only one information section needs to expand or collapse. A DataTable is better for tabular lists of repeated rows, not a small group of primary-contact fields. Salesforce FlexCard documentation confirms that Block elements can group content inside collapsible containers.

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

A DocuSign Envelope Action can be used to create and send a document for signature using a DocuSign template. The developer can specify the template ID, recipient details, and prefill data in the action configuration

 The Use Data JSON property must be selected in the properties of the Type Ahead Block in order to display the fetched data in the fields. The Lookup Mode property is used to specify the type of lookup to perform. The FirstName, LastName, and BirthDate fields can be placed inside or outside the Type Ahead Block. The typeHead key is in the correct format.

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.

According to the OmniStudio DataRaptor Extract documentation, if a developer wants to limit the number of records returned, the best way is to set the " Limit " property on the element or action that is calling the DataRaptor, such as in an Integration Procedure or OmniScript Action.

A. Set the Limit property on the action that calls the Data Mapper Extract – This is the correct method. The calling context (e.g., OmniScript Action or Integration Procedure) includes a property for setting the limit on query results, which is a recommended and clean method to ensure only one record is retrieved.

Incorrect Options:

B. There is no " LIMIT " clause within the DataRaptor Extract definition UI or JSON definition itself.

C. Custom Output Type controls the structure, not the quantity of output.

D. The Filter function applies conditional logic, not record count.

Salesforce OmniStudio Developer Guide → DataRaptor Extract Configuration

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.

 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.

The PREVIEW tab in OmniScript allows the developer to test the DataRaptor Extract by providing a record ID and viewing the output data. This is a quick and easy way to troubleshoot whether the DataRaptor Extract is retrieving data correctly.

After defining a formula, the result must be stored and made available in the Data Mapper output structure. In the current Data Mapper design pattern, the formula result path creates a JSON node, and the developer then maps that result into the final output through the mapping configuration. This is why option B is the best answer: the formula is not useful to downstream actions until it is mapped to the required target output. The Extract tab is used to define source data retrieval, not to map formula results. The Output tab applies to specific Extract-style mappings in older terminology, but the question uses the generic Data Mapper mapping workflow. The essential step is to map the formula result into the JSON.

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

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.

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

 According to the OmniStudio Developer Guide, “To upsert a record, select the Upsert Key checkbox for the field that contains the unique identifier for the record. If you want to create a new record when no match is found, select Is Required for Upsert.” Therefore, the correct answer is B.

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.

A DataRaptor Transform can be used to transform data from one format to another, such as JSON, XML, or CSV. The developer can specify the input and output paths for each field in the Transform tab. The developer can also use formulas to manipulate data in the Formula tab1. To transform contact data into a JSON array, the developer can use either of these methods:

Use a formula LIST(Contact), and add the output of the formula as the input in the Transform tab. This will create a list of contact objects from the input JSON and output it as a JSON array.

Set the Input JSON Path as Contact, the Output JSON Path as Contact, and the Output Data Type as List. This will output each contact object as an element of a JSON array.

The most direct and lowest-risk method is to use the Clone button in the Data Mapper Designer. Cloning preserves the original Data Mapper configuration and creates a separate copy that can be modified for the new requirement. Manual copy-and-paste is inefficient and error-prone because mappings, formulas, filters, and output paths can easily be missed. Using SFCLI or deployment tooling to duplicate JSON is possible for advanced source-control workflows, but it is not the most straightforward designer-based approach. Creating an Integration Procedure to call the old Data Mapper does not create a new independent Data Mapper and would not let the developer safely change the mapping logic for the new requirement. Cloning is the intended starting point for this scenario.

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

The correct answer is A. In a parent-child FlexCard design, attributes are passed from the parent FlexCard to the child FlexCard and referenced in the child using the Parent context variable. Salesforce documentation states that the Parent context variable is used to reference attributes from the parent FlexCard on the child FlexCard, and child FlexCard properties allow passing data from the parent by creating attributes and assigning data merge field values. Therefore, when the postal code is passed as a parent attribute, the child FlexCard should reference it as {Parent.postalcode}. {Params.postalcode} is used for URL or runtime parameters, {postalcode} references local data only, and {attr.postalcode} is not the correct OmniStudio parent context syntax.

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

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.

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

The Repeatable Mode property on the data table elements allows the developer to display multiple records in a single data table. The Repeat Records feature on the FlexCard Setup tab is used to display multiple FlexCards for each record in a data source. The Record Looping feature on the data table elements is used to iterate over a list of records and perform actions on each record. The Overwrite Target for all Null input checkbox on the Account id field is used to overwrite the existing value in the target object with null if the input value is null.

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.

From the OmniStudio OmniScript Documentation:

A Repeat Block (like BlkContacts) expects an array of objects.

Each item in the array must contain fields that exactly match the UI elements inside the block.

The parent JSON must include any top-level values used by individual input fields (like AccountName, AccountPhone).

Why the Other Options Are Incorrect:

B. Uses Contacts instead of BlkContacts, and is incomplete/malformed.

C. Repeats keys at the same level instead of using an array structure. This causes the data to overwrite and fail to display properly.

D. Uses incorrect keys like " Name " and " Phone " instead of expected " ContactName " and " ContactPhone " , breaking field binding.

A Data Mapper Transform is used to restructure input JSON into the output JSON format required by a target system. Since the target requires a nested array of objects, the developer must map the source value into the correct nested target path so the Data Mapper output structure creates the ContactDetails array and Phone object. A flat direct mapping does not describe the required parent array and child object structure. A Formula is not required just to place an existing source value into a nested output structure; formulas are used when the value itself must be calculated or transformed. Mapping to the root node would lose the required ContactDetails and Phone hierarchy. The correct method is nested target path mapping.

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

A Remote Action is the Integration Procedure element designed to call custom Apex logic. This scenario requires execution of an Apex method that performs custom authentication and token generation before later data retrieval, which is exactly the type of server-side custom logic handled by a Remote Action. A Data Mapper Transform restructures data; it does not execute Apex. A Sub-Integration Procedure calls another Integration Procedure, not an Apex method directly. An HTTP Action calls an external REST endpoint, which is useful after token generation but does not execute local Apex code. Salesforce documentation explicitly states that the Remote Action element calls the specified Apex class and method or an invocable action.

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

For an active OmniScript, the correct practice is to create a new version, make the change in that new version, test it, and activate it only when it is ready. Editing the active version directly is risky because users can be affected immediately, and in-flight users may experience inconsistent behavior. Cloning creates a separate component and is useful when the new script must be independent, but it is not the best approach for a minor controlled change to the same OmniScript. Waiting for a Salesforce release is irrelevant because this is a configuration lifecycle issue, not a platform-release dependency. Salesforce’s OmniStudio versioning guidance supports using versions so changes can be validated before replacing the active version used by end users.

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

Setting the Timeout property on the HTTP Action in the Integration Procedure allows the developer to specify how long to wait for a response from the external system before timing out. Checking the Chain on Step Check on the HTTP Action in the Integration Procedure allows the developer to chain multiple HTTP Actions together and execute them sequentially. Configuring a Remote action with timeout settings of 120000 is not necessary, as it is already done by default in OmniStudio. Checking the Chainable checkbox on the integration procedure Action in the OmniScript has no effect on calling an external system.

To launch an OmniScript from a FlexCard, the Action element must identify the target OmniScript by its Type, SubType, and related configuration. Because the OmniScript requires the Case ID, the developer must explicitly pass the FlexCard data value, such as CaseId, through the action’s input mapping. Option D is unsafe because the OmniScript does not automatically know which Case ID to use unless the value is passed through context or input parameters. Option B confuses launching the OmniScript with saving Case data; the Data Mapper Load would be used later inside the OmniScript or Integration Procedure. Option C describes a more custom LWC-style configuration, not the standard OmniScript Action setup from a FlexCard.

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

Cloning an Integration Procedure creates a copy of it that can be modified and used independently from the original one. This is useful when the new Integration Procedure has a different purpose or functionality than the original one

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 Expression Set component in OmniStudio allows developers to perform calculations using steps such as Aggregation, Calculation, and Sub Expression.

C. Add an Aggregation Step as SUM(BasePrice) – This is correct. Aggregation steps are specifically designed to perform functions like SUM, AVG, COUNT, MIN, MAX over collections (arrays) of data. In this use case, summing the entire BasePrice array is best handled using an Aggregation Step.

Incorrect Options:

A. Sub Expression Step is used to combine or manipulate previously calculated values, not to aggregate across an array.

B. Calculation Step is used for row-level calculations, not aggregation across multiple rows.

Salesforce OmniStudio Documentation → Expression Sets → Aggregation Step

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