What is the reason for this?

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 passDataJSON in the parent OmniScript in not configured correctly.

View Answer

Answer: C