A developer creates an Integration Procedure with a Set values and a DataRaptor Extract Action that requires Accountld as a key. When the developer previews the Integration Procedure, the developer enters the Accountld correctly and executes the preview. The developer sees the dataextracted by the DataRaptor in the Debug Log, but the response is empty.
What is the likely cause of this issue?

• A.The Response cannot be previewed directly.
• B.The DataRaptor Action did not have the Add Response To Response JSON property set to true.
• C.A Response Action was not added to the Integration Procedure.
• D.The Accountld used for the preview is invalid.

Comment: *

Name: *

Email: *

Verification: *

A developer is creating an OmniScript that provisions trail orgs to their customers. The following text block in the Omniscript uses a merge code to display the ID for the new trail org:

• A.To %sDetails: Customer|0: ID$
• B.To %Details: Customer|1: ID%
• C.To %%sDetails: Customer|0: ID%%
• D.To %Details: Customer|n: ID%

Comment: *

Name: *

Email: *

Verification: *

Refer to the exhibit.

The card layout uses an integration Procedure as a data source. The cards use the layout data source.
Which JSON data structure supports this card layout and follows best practices?

• A.
• B.
• C.

Comment: *

Name: *

Email: *

Verification: *

A customer sets up to LWC Omniscripts, one embedded into another. Account is set in a Set Values element in the parent Omniscript.
The AccountId set in the parent Omniscript is used to another Set Values element ContextAccountid in the embedded OmniScript. The embedded Omniscript is activated.
While previewing the OmniScript flow from the parent, it is found that Account is set correctly in the parent OmniScript. However. ContextAccountId in the embedded OmniScript is not set with the AccountId from parent Omniscript. On previewing the embedded OmniScript individually, it is found that ContextAccountId is set correctly.
What is the reason for this? Refer to the exhibit below.

• A.Both parent and embedded OmniScripts have the same element name for the Set values element.
• B.A developer failed to include a Navigation Element to pass data from the parent OmniScript.
• C.The LWC PubSub Message flag in the Set Values action of the parent has not been set.
• D.The flag pass Data JSON in the parent OmniScript in not configured correctly.

Comment: *

Name: *

Email: *

Verification: *

A developer has a requirement to create a child FlexCard that contain all of its parent FlexCard's records in a Datatable.

• A.{Records[0]}
• B.{Records}
• C.{Params records}
• D.{recordId}

Comment: *

Name: *

Email: *

Verification: *