OmniStudio-Developer Exam Dumps - Salesforce Developer Questions and Answers

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.

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.

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.

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

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.

 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.

The correct syntax for merge codes in OmniScript is %%sNodeName%%, where NodeName is the name of the JSON node in the data source. The other options are either missing the s or using incorrect symbols.

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

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.

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.