OmniStudio-Developer Salesforce Certified OmniStudio Developer (SP23) Question and Answers

 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.

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: AccountName, AccountNumber, AccountType, AccountOwner, ContactName, and ContactPhone. The DRGetAccountDetails action is a DataRaptor Extract action that retrieves data from the Account and Contact objects in Salesforce. The BlkContacts element is a Repeat Block that displays a list of contacts related to the account. Therefore, the JSON from the DRGetAccountDetails action that would display all six values correctly in the OmniScript structure 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 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.

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. 

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.

 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.

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.

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 suitable for this scenario because the developer does not need to transform or load the data

According to the Integration Procedure Actions page, a Calculation Action can be used to “call a Calculation Procedure that performs calculations on input data” and a Matrix Action can be used to “call a Calculation Matrix that performs calculations on input data”. 

The Target property in publishing Options determines where the FlexCard will be displayed. Setting it to the Community page will make the FlexCard available in the community

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

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

 An Integration Procedure Action can execute an Integration Procedure that contains multiple elements, such as DataRaptor Actions, HTTP Actions, or other Integration Procedure Actions. This can be used to save data to multiple systems, such as Salesforce and AWS Order Management, in one OmniScript element.

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 DataRaptor Transform Overview page, a DataRaptor Transform can be used to “pre-populate data in PDFs used by OmniScripts”.

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