The merge code syntax for passing data from a DataRaptor Extract Action to an HTTP Action is % DataRaptorName: NodeName%. In this case, it is %DRReadCase: CaseNumber%.

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.

From OmniStudio Best Practices for Modular Script Design, OmniScript Actions are the preferred mechanism to invoke another OmniScript within a parent OmniScript. This approach enables reusability and modularization, especially when a function (like updating billing information) is common across many interactions.
* A. OmniScript Action - This is the correct and standard method for embedding or launching one OmniScript from another. It allows developers to reuse common scripts without duplicating logic.
Incorrect Options:
* B. Custom Action requires custom Apex or LWC development, which is unnecessary for this use case.
* C. Lightning Action is typically used to invoke OmniScripts from Lightning pages, not within OmniScripts themselves.
:
OmniStudio Developer Guide # OmniScript Actions

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