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

Comment: *

Name: *

Email: *

Verification: *

A developer creates an Integration Procedure with a Set Values and a DataRaptor Extract Action that requires AccountId as a key. When the developer previews the Integration Procedure, the developer enters the AccountId correctly and execute the Preview. The developer sees the data extract by the DataRaptor in the Debug Log, but the response is empty.
What is the likely cause of this issue?

• A.The DataRaptor Action did not have the add response Ro Response JSON property set to true.
• B.A Response Action was not added to the integration Procedure.
• C.The AccountId used for the preview is invalid.
• D.The Response cannot be previewed directly.

Comment: *

Name: *

Email: *

Verification: *

You are troubleshooting an Integration Procedure with two elements: a Remote Action named FetchCart and a Response Action named ResponseCart. In PREVIEW, what JSON node shows the data sent to the Remote Action?

• A.ResponseCartDebug
• B.ResponseCart
• C.FetchCartDebug
• D.FetchCart

Comment: *

Name: *

Email: *

Verification: *

You are building a DataRaptor Load for an Integration Procedure used in an OmniScript.
Based on best practices, how should you configure the Input JSON?

• A.Copy the Input JSON from the OmniScript {Data} modal.
• B.Build the Input JSON node by node in an editor.
• C.Build the Input JSON node by node in the DataRaptor Designer.
• D.Copy the Input JSON from the DataRaptor Action Debug node.

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 %%sDetails: Customer|0: ID%%
• C.To %Details: Customer|1: ID%
• D.To %Details: Customer|n: ID%

Comment: *

Name: *

Email: *

Verification: *