Salesforce OmniStudio-Developer Salesforce Certified OmniStudio Developer Plat-Dev-210 Exam Practice Test

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.

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

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 Id Field for Actions in the FlexCard specifies which field from the FlexCard data source will be used as the record ID for the OmniScript. If this field is blank, the OmniScript will not receive any record ID and will not be able to retrieve any Salesforce data. In the DataRaptor Extract Action, the Input Parameters Filter Value determines how to filter the data based on the record ID. If this value is misspelled, the DataRaptor Extract will not be able to match the record ID and will not return any data.

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.

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.

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 cleanest method is to assign a unique CSS class to the second Block and apply the styling once at the Block level. This keeps the design maintainable because all less-critical fields inside that Block inherit or are affected by the same styling pattern. Manually changing each Text element works technically, but it is inefficient and harder to maintain if more fields are added later. A Layout property does not exist as a reliable “Small” styling switch for this requirement. A State element is for alternate card presentations based on conditions, not simply applying a different font style to one section. Salesforce FlexCard documentation supports applying custom CSS classes and inline styles to FlexCard elements when built-in style properties are not enough.

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

In Expression Sets, for any intermediate step (like Calculation) to be referenced in subsequent steps, such as Aggregation, the value must be made available via Output.

B. It must be included in the output – Correct. Each step has an " Include in Output " checkbox. If not checked, its result is not accessible to following steps like Aggregation or Sub Expression.

Incorrect Options:

A. Constants are global but do not affect step dependency.

C. It does not have to be a Calculation Step; any previous step’s output can be used if exposed.

Salesforce OmniStudio → Expression Sets - Step Configuration

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

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

 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.

 A DataRaptor Extract can retrieve data from multiple objects using extraction steps and JSON paths. However, if the data is from a single object, only one extraction step is needed. The Extract JSON Path can use dot notation to access related fields from that object, such as Contact.Account.Name.

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

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

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

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

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

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

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

A FlexCard is the correct front-end component for a single, focused view on a Contact record page. The data may come from Salesforce and an external grant management system, and an Integration Procedure can be used behind the scenes to aggregate that data. However, the question asks which OmniStudio tool should retrieve and display the combined information in a compact record-page view. A Data Mapper Transform reshapes data but does not provide the visual record-page card. A Calculation Procedure performs calculation logic, not case-manager display. OmniScript is better for guided multi-step processes, not quick contextual viewing. Salesforce documentation confirms that FlexCards can be configured with data sources, including Salesforce or external databases, and can display contextual information on record pages.

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

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

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

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

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

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

The Node field for the parent FlexCard should be set to {Records}, which is an array of all the records retrieved by the parent FlexCard data source. This will allow the child FlexCard to access the records and display them in a DataTable.

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

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

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

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

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

A DataRaptor Transform can simplify nested data by transforming it into a flat structure. The developer can use JSON paths to map the input data to the output data and define the output structure.

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.

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

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

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.

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

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

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

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.

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

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.

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

Invoke Mode Non-Blocking is the correct choice because the OmniScript still needs the Integration Procedure response, but the user interface should not be blocked while waiting. Salesforce describes Non-Blocking as running asynchronously while applying the response to the UI. Fire and Forget is different: it is used when the caller does not need a response returned to the OmniScript. Use Future is also asynchronous, but it is best when completion timing is not critical and no response is required. Toast Completion only controls a user notification style; it does not determine whether the OmniScript waits for the Integration Procedure response. Since the response must still come back as JSON while the user proceeds, Non-Blocking is the correct feature.

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

According to the Calculation Matrix Overview page, a Calculation Matrix is “a lookup table that takes an input and returns an output”. In this case, the input is the ProductCode and the output is the Price. The exhibit shows a Calculation Matrix with four rows, each with a different ProductCode and Price. The input given is ProductCode: HRA3320, which matches the second row of the matrix. Therefore, the output is Price: 13.99, which is the value in the same row. 

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

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

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.

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

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.

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

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

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

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

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

QUESTIONNO: 23

A healthcare company wants to enable its subscribers to add, edit, or delete dependents related to their policy Community portal. The developer on the project decides to use an MniScript.

How should the developer configure the OmniScript to providethis functionality?

A. Use an Edit Block element configured with Remote Actions.

B. Use an Edit Block element configured with SOQL statements.

C. Use an Input Block element and a DataRaptor Post Action element.

D. Use a Text Block element and a Remote Action element.

Answer: A

An Edit Block element configured with Remote Actions allows the developer to create a dynamic table that can display, add, edit, or delete records from a Salesforce object. The Remote Actions can be configured to perform CRUD operations on the object using SOQL or Apex.

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.

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

A formula element allows the developer to define formulas using functions and operators to manipulate data in an OmniScript. The output of the formula element can be displayed to the user immediately in the current step using a display element. The CONTIF function counts how many times a value appears in a list1. A Calculation Action element executes a calculation procedure and returns the output as a JSON object. A Set Values element assigns values to variables or fields in an OmniScript. A Range element defines a range of values for a variable or field in an OmniScript1. Based on best practice, a formula element is the most suitable element to use the CONTIF function in this scenario.

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

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.