Which statement best describes how to enable passing data from a parent OmniScript to a nested OmniScript when the child requires the AccountId?

Which statement best describes how to enable passing data from a parent OmniScript to a nested OmniScript when the child requires the AccountId?

• A. Both scripts must share identical element names for Set Values
• B. A Navigation Element must be added to pass data
• C. The LWC PubSub Message flag in the Set Values action of the parent must be set
• D. DataLacing between scripts is automatic and requires no extra configuration

Answer: (C)

Passing data between a parent OmniScript and a nested one uses the LWC PubSub messaging mechanism. When you enable the LWC PubSub Message flag on a Set Values action in the parent, those values are published to a PubSub channel during execution. The nested OmniScript subscribes to that channel and can receive the AccountId (and any other needed data) so the child has what it needs to run. Without this flag, the parent’s values don’t automatically flow to the child, even if the child requires AccountId. The other ideas don’t provide the reliable cross-script data handoff that PubSub delivers.

Passing data between a parent OmniScript and a nested one uses the LWC PubSub messaging mechanism. When you enable the LWC PubSub Message flag on a Set Values action in the parent, those values are published to a PubSub channel during execution. The nested OmniScript subscribes to that channel and can receive the AccountId (and any other needed data) so the child has what it needs to run. Without this flag, the parent’s values don’t automatically flow to the child, even if the child requires AccountId. The other ideas don’t provide the reliable cross-script data handoff that PubSub delivers.