OmniStudio-Developer Questions and Answers

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.

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

The merge code syntax for accessing a node from an Integration Procedure output is {{ProcedureName:NodeName}}. In this case, the ProcedureName is HTTPGetCaseDetails and the NodeName is CaseData. The % sign is used for single-value merge codes, not node merge codes. The $ sign is used for variables, not merge codes.

A Data Mapper Extract Action is the correct choice when an OmniScript must retrieve many fields from a Salesforce record. Data Mapper Extracts are built specifically to read Salesforce data, select the required fields, apply filters, and return the data in JSON, XML, or another configured output structure. A Lookup element is appropriate for retrieving or selecting a single record or field value, but it is not the best tool for pulling many fields. HTTP Action is for calling external HTTP endpoints, not directly querying Salesforce records. Select is a user-input element, not a Salesforce data retrieval tool. For a multi-field Salesforce record retrieval requirement, Data Mapper Extract provides the correct declarative query and mapping capability.

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

 According to the FlexCard Designer Overview page, another possible cause of a field showing only the label is that “the field is null on the Salesforce record”.

The correct configuration is the Knowledge Articles property on the Step element. OmniScript supports Salesforce Knowledge integration through Knowledge Options configured on a Step. This lets the developer display or filter Knowledge content where the user needs it in the guided process, such as a complex product-information step. A Knowledge Action is not the standard OmniScript element used for step-level help article display. Messaging Framework is unrelated because it handles messaging behavior, not Knowledge article rendering. A custom LWC could be built, but that would be unnecessary custom development when OmniScript already provides Knowledge configuration on the step. The requirement is step-specific, context-sensitive article display, so the Step element’s Knowledge Articles configuration is the correct answer.

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

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.

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

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, “DataRaptor Transform actions can convert JSON to XML and vice versa.” Therefore, the correct answer is C.

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 Troubleshoot Flow Errors page, one way to troubleshoot errors is to “check the debug logs for the community”. Another way is to use the Action Debugger tool, which “lets you test and debug actions in OmniStudio”. 

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.

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

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.

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

A FlexCard is the correct user-interface component for displaying summarized, contextual, responsive information from one or more data sources. The scenario is not asking for a guided form or step-by-step process; it asks for a single-page health summary with list-like lab results and interactive display behavior. An Integration Procedure can absolutely be used behind the FlexCard to aggregate Salesforce demographic data and EMR lab results, but the component that displays and manages the responsive interaction is the FlexCard. A Data Mapper Extract only retrieves Salesforce data and does not handle external EMR data or UI interaction. OmniScript is better for guided data collection and process automation, not a compact summary card. Therefore, the front-end OmniStudio component should be a FlexCard.

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

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.

The missing access is execute access to the specific Apex class used by the Remote Action. A Remote Action in an Integration Procedure invokes Apex or an invocable action, so the running user must be authorized to execute that Apex class. Salesforce documentation for OmniStudio Apex class permission checkers states that access must be enabled for the classes used by Remote Action APIs for each profile, permission set, or permission set group. “Run Flows” is irrelevant because this is not Flow execution. General data-model access may still be required for object operations, but it does not authorize the Apex class itself. A Try-Catch Block can catch or handle an error response, but it does not fix the underlying unauthorized Apex execution failure.

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

OmniScript is the correct tool because the scenario describes an end-to-end guided business process: collecting property details, applying conditional steps, calling calculation logic, and submitting the final application. Integration Procedures are excellent for server-side orchestration, integrations, and calculations behind the scenes, but they do not provide the user-facing guided interaction by themselves. Data Mappers retrieve, transform, or save data; they are not the process UI. FlexCards display contextual information and actions but are not designed as the primary multi-step application workflow. Salesforce describes OmniScripts as guided, interactive processes that help users complete business tasks and collect data across channels. Therefore, the core component controlling this process is an OmniScript.

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.

In OmniStudio Integration Procedures, when you want to reference the output of an element in a nested block (e.g., for use in a Remote Action or another step), you must use dot notation that mirrors the block structure hierarchy.

In the exhibit:

Action1 is nested inside:

BlockB, which is nested inside:

BlockA

Therefore, the correct Send JSON Path to access the result of Action1 is:

CopyEdit

BlockA.BlockB.Action1

This format complies with the standard output reference syntax in Integration Procedures, which follows the pattern:

php-template

CopyEdit

< ParentBlock > . < ChildBlock > . < ActionElement >

Incorrect Options:

B. BlockA:BlockB:Action1 – Uses colons instead of dots. This is invalid syntax in JSON path resolution within Integration Procedures.

C. Action1:BlockB:BlockA – Incorrect order and invalid separators.

D. Action1.BlockB.BlockA – Incorrect order (reversed path).

When an OmniScript receives incomplete data from an Integration Procedure, the issue is typically in Response JSON path mapping or naming mismatches.

A. The missing data is trimmed in the Integration Procedure Action Response JSON Path – If the Response JSON Path only points to part of the structure, any nested or unrelated values are excluded from the output.

B. The element name for the missing data does not match the JSON node key in the Integration Procedure Response – OmniScript expects a matching node name to bind the data to UI elements. If the key doesn’t match, that field will appear blank.

Incorrect Options:

C. Preview Input Parameters are only for testing in the Integration Procedure editor; they don’t affect runtime execution.

D. Even if the JSON from the Integration Procedure Action is different from the original IP input, it would cause a failure or unexpected data, not necessarily missing specific values.

Salesforce OmniStudio → Integration Procedures → JSON Path and Data Binding

The first responsible action is to validate the Data Mapper query design before committing to the implementation. Prefilling 15 user-based fields can be efficient, but only if the query is selective, returns only needed fields, and uses appropriate filters. Salesforce’s Data Mapper best practices warn developers to avoid server performance problems and to ensure filtering and sorting operations use indexed fields where possible. A Data Mapper Load is wrong because the requirement is to read current user data, not write data back to the User object. Converting the process to a FlexCard does not solve the prefill query risk. A Formula element cannot query Salesforce records. Therefore, option A is the correct risk-reduction step before development proceeds.

Runtime OmniScript access alone is not always enough when the OmniScript executes Data Mappers, Integration Procedures, or Remote Actions that rely on Apex-backed services. Salesforce has OmniStudio security checks for Apex class access, and its documentation specifically describes configuring Apex class permission checkers so users require explicit access to the Apex class that administers a Remote Action. Save Options do not control Lightning component authorization. Multi-language settings affect labels and translations, not runtime component permissions. FlexCard permissions are not the most likely cause because the error occurs while launching an OmniScript and the scenario already confirms OmniScript runtime access. The developer should therefore investigate missing Apex class access behind the OmniScript’s actions.

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

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

Conditional Rendering is best when only one element, or a small number of elements, must be hidden or shown based on simple data logic. For example, if one field, label, icon, or block depends on a single Boolean or status value, a rendering condition is more efficient and easier to maintain than creating another FlexCard State. States are better when the card must switch to a substantially different layout or when many elements change together. Option D describes a state-level use case, not a single-element rendering condition. Option A is wrong because no condition is needed if the element is always visible. Option B is not the deciding factor; repeaters can contain conditional elements, but the reason is still the simplicity of the condition.

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

In Preview, the JSON node that shows the data sent to the Response Action is the name of the Response Action itself. In this case, it is ResponseCart. The other nodes show either the input data or the output data of the Integration Procedure.

The Lookup element is used to retrieve data from a single field in a Salesforce record. The Lookup element allows the developer to specify the object, field, and filter criteria for the data retrieval. The Select element is used to display a list of options for the user to choose from. The HTTP Action element is used to send or receive data from an external system using HTTP methods. The DataRaptor Post Action element is used to create or update Salesforce records using a DataRaptor Transform.

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

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.

 Using the LIMIT filter on the Extract definition allows the developer to specify the maximum number of results to return from the DataRaptor Extract. Defining a formula with the Filter function is used to filter the results based on a condition. Using a Custom Output Type when creating the DataRaptor is used to define the structure of the output data. Setting the Limit Property on the Action that calls the DataRaptor Extract has no effect on limiting the results.

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.

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

The correct answer is D. Data Mapper Turbo Extract, based on best practices in the official OmniStudio documentation.

From the OmniStudio Developer Guide → DataRaptors → Turbo Extract:

DataRaptor Turbo Extract is a lightweight, high-performance extract designed specifically for retrieving data from a single Salesforce object, where no data transformation or complex joins are required.

It is recommended over DataRaptor Extract for performance reasons when only one object and minimal transformation is needed.

Why not the others?

A. DataRaptor Load is used for writing data to Salesforce, not retrieving.

B. DataRaptor Transform is used when you need to transform data, not simply extract it.

C. DataRaptor Extract can be used, but Turbo Extract is preferred for the use case of single object, no transformation — per best practices.

Salesforce OmniStudio Developer Guide → DataRaptor Turbo Extract Best Practices

OmniStudio Certification Study Guide → " When to use Turbo Extract "

The best practice is to create a separate child FlexCard for the related-contact display. A child FlexCard gives the team a reusable UI component that can be embedded in other FlexCards without copying layout elements, actions, fields, and styling each time. Duplicating the elements would create maintenance problems because later changes must be repeated everywhere. A global CSS class can standardize appearance, but it does not make the component logic reusable. A Data Mapper can retrieve or transform data, but it is not a display component. Salesforce documentation confirms that FlexCards can be embedded inside other FlexCards and can use either their own data source or the parent FlexCard’s data, which supports modular reuse.

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

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.

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.

The AccountId is not the issue because the Debug Log already shows that the Data Mapper Extract retrieved data successfully. The failure is at the response-return stage of the Integration Procedure. In OmniStudio, a Response Action is used to end the Integration Procedure and return data to the caller. If the Data Mapper action runs but no Response Action is configured, the internal debug data can exist while the external response remains empty. Option A is weaker because the core requirement is not only adding data to an internal response JSON property; the Integration Procedure needs a Response Action to send the final output. Option C adds unnecessary and inaccurate wording about Send JSON Path. The clean verified cause is that no Response Action was added.

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

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.

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

 Option D is the correct way to configure Additional input to send exactly the same data as Input Data. The Additional input should have the same key/value pairs as Input Data, and the value should be set to {{InputData.key}} for each key. This will pass the value of Input Data for each key to Additional input.

According to the Transform External Data Unit, the Expected Output JSON should match the Output Path of the DataRaptor Transform. In option D, the Output Path is Current:CityState, which matches the Expected Output JSON. The other options have different Output Paths that do not match the Expected Output JSON. Therefore, the correct answer is D.

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.

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

 According to the FlexCard Designer Overview page, one possible cause of a field showing only the label is that “the field name in the FlexCard state does not match the DataRaptor Extract’s Output JSON Path name”. 

The correct design is to call the second Integration Procedure as a Sub-Integration Procedure and enable chainable execution. Chainable Integration Procedures are specifically used to split long-running processing into multiple transactions to avoid Salesforce governor limits. A plain Sub-Integration Procedure Action promotes reuse, but without chainable configuration it does not necessarily create the separate transaction behavior required here. An HTTP Action is for making HTTP callouts, not the cleanest way to invoke internal OmniStudio transaction chaining. A Set Values element only changes data JSON values and cannot execute another Integration Procedure. Because the requirement explicitly says separate transaction context and governor-limit prevention, chainable execution through the Sub-Integration Procedure call is the best answer.

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

 The merge code syntax for passing data from a DataRaptor Extract Action to an HTTP Action is %DataRaptorName: NodeName%. In this case, it is %DRReadCase: CaseNumber%.

The data action should be placed where the step can retrieve the required data before the user needs to see or use it. Placing the Data Mapper Extract Action on the same relevant step keeps the data retrieval close to the UI elements that depend on it and avoids loading unrelated data globally in the Header. Placing the action after the data usage is obviously too late because the fields or options would already be rendered without the needed values. A Set Values element cannot execute a Data Mapper Extract; it only sets or changes values in the OmniScript data JSON. Salesforce’s OmniScript action-element documentation explains that action elements are used to get, modify, and write data during the OmniScript process.

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

 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.

 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 three elements: Step, Block, and Telephone. The Step element is an empty object, the Block element is an object with two properties: Text and Telephone, and the Telephone element is a string. Therefore, the JSON code that correctly represents the step in the OmniScript Structure panel 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.

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 Params node contains the data that is passed from the parent FlexCard to the child FlexCard. The developer should use {Params.postalcode} to refer to the contact’s postal code in the child FlexCard.

According to the Salesforce OmniStudio DataRaptor documentation, specifically under DataRaptor Load Best Practices and Common Issues:

A. “The Input JSON paths in the Data Mapper Load do not match the JSON sent from the OmniScript.”This is a common configuration issue. If the paths between the OmniScript ' s structure and the DataRaptor Load mapping are mismatched, fields may not map correctly, resulting in partial updates or no updates.

B. “The fields that are not updated are read-only in Salesforce.”If a field is Read-Only at the field-level security (FLS) or object schema, DataRaptor Load will not be able to write to it, which explains why only some data is updated.

Incorrect Options:

C. The RecordId from the wrong record type would typically cause a complete failure, not a partial update.

D. A misspelled ContextId could prevent data from being linked correctly, but this is less likely to cause partial field-level issues, and more likely to affect record association.

Salesforce OmniStudio Developer Guide → DataRaptor Load → Troubleshooting

Salesforce Help Documentation: OmniStudio DataRaptor Best Practices

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.

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