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

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

 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.

 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.

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

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.

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

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

According to the Integration Procedure Actions page, a Remote Action can use a function in an Additional Output value field or in a Remote Options value field. According to the Response Actions page, a Response Action can use a function in an Additional Input value field.

According to the OmniStudio Developer Guide, “DataRaptor Transform actions can convert JSON to XML and vice versa.” 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.

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 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 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 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 Invoke Mode Fire and Forget feature enables the OmniScript to invoke the Integration Procedure without waiting for a response. This is useful when the response is not needed for the user to proceed

 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.

The Upsert Key checkbox indicates that the field is used as a key for upserting records. The Is Required for Upsert checkbox indicates that the field is mandatory for upserting records. The developer needs to check both checkboxes on the Account Id field to update the Account status only if the Account record already exists. Otherwise, a new account will be created.

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.

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.

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.