OmniStudio-Developer Salesforce Certified OmniStudio Developer Plat-Dev-210 Questions and Answers

The Timeout property on the HTTP Action in the Integration Procedure specifies how long to wait for a response from the external system before throwing an error. The Chain On Step checkbox on the HTTP Action in the Integration Procedure indicates that the next action should be executed only if the current action is successful. These two configurations should be used to implement the call to the external system given its known performance issues. 

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

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: ContactName, ContactPhone, ContactEmail, CaseNumber, CaseSubject, and CaseStatus. The DRGetContactDetails action is a DataRaptor Extract action that retrieves data from the Contact and Case objects in Salesforce. The BlkCases element is a Repeat Block that displays a list of cases related to the contact. Therefore, the JSON from the DRGetContactDetails action that would display all six values correctly shown is option A, which has the following structure:

The other options have different structures that do not match the OmniScript structure shown.

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.

In OmniStudio, the Edit Block element is purpose-built for allowing users to dynamically add, edit, or delete rows of related data, such as dependents under a policy. To save these changes, Remote Actions (typically backed by Apex or API) are used to process each record operation (Create/Update/Delete).

A. Use an Edit Block element configured with Remote Actions – Correct. This is the recommended and most scalable way to support CRUD operations in OmniScripts for collections (e.g., dependents). The Edit Block provides UI-level support, while Remote Actions handle back-end interaction with Salesforce or external systems.

Incorrect Options:

B. Text Block is for display purposes and cannot manage data input or backend actions.

C. Input Block elements do not support row-level add/edit/delete functionality as Edit Blocks do.

D. SOQL is a read-only query language and cannot be used to update or delete records directly within an OmniScript.

Salesforce OmniStudio Guide → OmniScript Edit Block Element

OmniStudio Best Practices → CRUD Operations in OmniScripts

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.

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

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.

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

Integration Procedure is the correct tool because the requirement goes beyond a simple Salesforce record extraction. Complex filtering, sorting, aggregation, orchestration, and preparation should be handled server-side before the OmniScript displays the result. A Data Mapper Extract is appropriate for retrieving Salesforce data, but it is not the best orchestration layer when multiple operations and preparation logic are required. An HTTP Action only calls an external endpoint; it does not by itself manage the full data-preparation workflow. A Set Values Action is useful for assigning values in the OmniScript data JSON, not for complex server-side data shaping. Salesforce describes Integration Procedures as server-side processes used to automate data operations between Salesforce and external systems, which matches this requirement.

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

The correct best practice is to use one Data Mapper Load configured for the related object mappings. Salesforce documentation explains that Data Mapper Load supports updates to multiple Salesforce objects and displays separate mapping tabs for each target object. It also documents Multiple Related Object Loads, or Link Mappings, for propagating data between related objects during a load sequence. This avoids unnecessary multiple sequential Data Mapper Load Actions and keeps the update logic declarative, maintainable, and transactionally cleaner. A Remote Action with Apex should only be used when declarative mapping cannot satisfy the requirement. A Salesforce REST API HTTP Action is also unnecessary because the operation is inside Salesforce and OmniStudio already provides Data Mapper Load for this exact use case.

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

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.

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.

This scenario relates to FlexCard preview behavior and data mapping issues.

B. There is no Salesforce record for the FlexCard based on the RecordId in the layout ' s Test Data Source Settings – If the test record does not exist, the FlexCard will not display any data during preview. This is a common setup mistake.

C. The Data Node field for the FlexCard is empty – The Data Node field must be set correctly to match the JSON node where the expected data resides. If it is empty or incorrect, the FlexCard won’t bind data to UI elements.

Incorrect Options:

A. Even if the RecordId is from a different record type, as long as the data structure aligns, it would still render; it’s not a definitive reason for the card failing to display.

D. Attributes are not required to display field values directly; they are used for passing data between cards or from context, not for direct field rendering.

Salesforce OmniStudio → FlexCard Data Source Setup & Troubleshooting

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

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

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

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.

The correct approach is to rely on OmniScript’s standard responsive layout behavior instead of manually hard-coding field widths or replacing the entire layout with custom Lightning web components. OmniScript designers support previewing scripts across device form factors such as Mobile, Tablet, and Desktop, and element display properties are intended to support responsive behavior. Manual width settings and custom media-query CSS should be reserved for exceptional branding or layout needs because they increase maintenance burden and can conflict with framework behavior. A custom LWC for the full layout would be excessive and would bypass much of OmniScript’s declarative value. Since the requirement is that input fields adjust correctly on smaller screens, the standard responsive OmniScript layout is the best-supported answer.

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

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.

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

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

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

 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.

Multi-language OmniScripts use Salesforce translation infrastructure and custom labels. In normal Salesforce runtime usage, the language shown to the user is driven by the user’s Salesforce language setting, not simply by the browser language or by a random session variable. The default OmniScript language is only the fallback/base design language; it does not decide which translated bundle is displayed for each user when translations exist. Option A is wrong because a global Session Variable is not the standard translation selector. Option B is also wrong in this context because OmniScript translations are tied to Salesforce language and Translation Workbench/custom-label behavior. Therefore, the user’s Salesforce language setting is the correct controlling source for displayed translations.

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

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.

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

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

A Sub-Integration Procedure Action lets a parent Integration Procedure call another Integration Procedure, so shared logic can be built once and reused wherever needed. This improves maintainability because future changes are made in the child Integration Procedure instead of being copied manually across many parent procedures. It also supports cleaner modular design: one procedure can handle a specific reusable operation, while parent procedures orchestrate the overall flow. Option A is not the key advantage because asynchronous behavior depends on specific chainable or queueable configuration. Option B is wrong because exception handling may still be required. Option C is not guaranteed, especially when chainable execution is used. The central design benefit is reuse and modularity of server-side logic.

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

When data changes every five minutes, the cache lifetime should be close to that refresh cycle. A 300-second Cache Duration gives the Integration Procedure a performance benefit while limiting stale data exposure to approximately the same interval as the source data change frequency. A contextual key controls cache separation by context, but it does not define when cached data expires. Disabling caching ignores the stated requirement that the developer wants to use caching. A very high value, such as 24 hours, is dangerous because users could receive stale data long after the underlying source changed. Salesforce’s OmniStudio caching guidance explains that Integration Procedures can cache results and that Cache Blocks are appropriate when different data must expire at different times.

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

The DataRaptor Formula tab allows the developer to define formulas using functions and operators to manipulate data. The TOINTEGER function converts a string value to an integer value. The developer can use this function to output the field value as an integer and use the formula as output

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.

The FirstName, LastName, and BirthDate fields should be placed inside the Type Ahead Block, so that they can receive the data from the selected record in the Type Ahead list. The Type Ahead Block has a Data JSON Path property that specifies the path to the data node that contains the record fields. For example, if the Data JSON Path is set to Contact, then the FirstName field should have a Value property set to {{Contact.FirstName}}.

 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 requirement is element-level visibility: only one Overdue status block must appear when Account Balance is greater than zero. The correct FlexCard configuration is a rendering condition directly on the Block element. FlexCard element conditions are designed to show relevant information based on field values from the card’s data source. Creating a separate Card State is excessive because the whole card layout does not need to change; only one block must be conditionally visible. A Setup tab filter controls data retrieval, not the display of a specific UI block after data is returned. A Flyout action is also unrelated because it opens additional content after user interaction. The verified implementation is to add a rendering condition to the Block element.

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

A DataRaptor Load Action can be used to retrieve data from a Salesforce object by specifying the object name, fields, and filter criteria. A Lookup Input Element can be used to retrieve data from a Salesforce object by allowing the user to search for a record using a lookup field

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

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

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

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

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.

Seed Data JSON inserts static launch-time values into the OmniScript data JSON. These values are not stored under a node named “Script Configuration”; that is only where the developer configures the seed data in the designer. At runtime, the seeded key/value pairs are placed into the OmniScript’s data JSON under the seed structure, so the correct representation is option B. This is useful when an OmniScript must start with hidden or prefilled values before any user interaction occurs. Salesforce documentation explains that the Seed Data JSON property is used to prefill OmniScript fields or add hidden nodes to the OmniScript Data JSON during initial load.

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

the calculation procedure version that would execute on 2/15/2020 at 12:00 PM is the one that has the start date time and end date time that include that date and time, and also has the highest priority among the enabled versions. In this case, only version number 4 meets these criteria, as it has a start date time of 2/1/2020 12:00 AM, an end date time of 4/1/2020 12:00 AM, a priority of 1, and is enabled. The other versions either have a different start or end date time, a lower priority, or are not enabled.

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

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

 An OS Action is the most efficient way to configure the action that invokes the OmniScript, as it allows the developer to reuse the same OmniScript across multiple FlexCards without creating separate actions for each one. A Custom Action is used to invoke a custom Apex class or Lightning web component. An OmniStudio Action is used to invoke an Integration Procedure or a Calculation Procedure. A Lightning Action is used to invoke a Lightning component or a Visualforce page.

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

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

The required SOQL behavior has two separate parts: ORDER BY and LIMIT. Ordering controls the sort sequence, such as sorting Tasks by CreatedDate descending so the newest Tasks appear first. Limit restricts how many records are returned, so setting the limit to five produces only the five most recent records. Filter is used to define matching criteria, such as records related to a specific Contact, but it does not create a LIMIT clause. Output Path controls where returned data appears in the JSON structure, not the query ordering or row count. Therefore, the necessary properties are Limit and Ordering. Salesforce’s Data Mapper configuration guidance confirms that Extracts read Salesforce data, can filter/select returned fields, and support extract configuration properties for returned records.

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

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.

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.

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

The verified answer is C. The selected answer in the PDF appears to be wrong. For OmniStudio managed package runtime, upgrades are package-based and can require installing the newer managed package version. Salesforce documentation for installing or upgrading the OmniStudio package says to install the latest OmniStudio managed package by going to OmniStudio Managed Package Releases and using the installation URL. That is different from standard runtime behavior, where functionality is more directly tied to Salesforce platform releases. Option D incorrectly treats managed package runtime as automatically upgraded only through seasonal Salesforce releases. Option A is wrong because a support case is not the normal upgrade mechanism. Option B overstates the process; deactivating all components is not the defining characteristic.

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

According to the OmniStudio Developer Guide, “To return a response from an Integration Procedure, add a Response action as the last action in your Integration Procedure.” Therefore, the correct answer is C.

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.