OmniStudio-Developer Salesforce Certified OmniStudio Developer (SU24) Questions and Answers

 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 syntax for the Send JSON Path is ActionName: BlockName, where ActionName is the name of the action element and BlockName is the name of the block element that contains the output data. The other options are either missing the colon or using incorrect names.

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.

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

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

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

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

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

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

According to the OmniStudio Developer Guide, “DataRaptor Transform actions can convert JSON to XML and vice versa.” Therefore, the correct answer is C.

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.

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

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 element name for the missing data must match the JSON node key in the Integration Procedure Response, otherwise the data will not be mapped correctly. The JSON sent from the Integration Procedure Action must match one of the Original Input for the Integration Procedure, otherwise the Integration Procedure will not execute properly. The Integration Procedure Preview Input Parameters and the Response JSON Path have no effect on displaying data in OmniScript.

 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.

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 Additional Input property allows the developer to specify additional input parameters to be sent to the Integration Procedure element. The input parameters can be specified as a JSON object or as a list of key-value pairs. If the developer checked Send Only Additional Input, then only the input parameters specified in Additional Input are sent, and the SEND/RESPONSE TRANSFORMATIONS are ignored. Therefore, the developer needs to specify the same input parameters as in the SEND/RESPONSE TRANSFORMATIONS in Additional Input. Option C shows how to do this using a JSON object with two properties: “DBExtractAction:Account” and “DBExtractAction:SecondaryAccount”. The values of these properties are the same as in the SEND/RESPONSE TRANSFORMATIONS. 

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.