Salesforce Exam OmniStudio Developer Topic 1 Question 81 Discussion

Actual exam question for Salesforce's OmniStudio Developer exam

Question #: 81
Topic #: 1

A customer sets up two LWC OmniScripts, one embedded into another. AccountId is set in a Set Values element in the parent OmniScript. The Accountid set in the parent OmniScript is used to set another Set values element ContextAccountId in the emvedded OmniScript. The embedded OmniScript is activated.

While previewing the OmniScript flow from the parent, it is found that Account I set correct in the parent OmniScript. However ContextAccount 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.

AThe WLC PubSub Messge flag in the Set Values action of the parent OmniScript has not been set.

BThe flag passData.JSON in the parent OmniScript in not configured correctly.

CA developer failed to include a Navigate Action Element to pass data from the parent OmniScript.

DBoth parent and embedded OmniScripts have the same element name for the Set Values element.

Show Suggested Answer

Suggested Answer: A

by Owen at Nov 15, 2024, 08:04 AM

Limited Time Offer

25%

Off

Get Premium OmniStudio Developer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Matt

7 days ago

Haha, a developer forgot to include a Navigate Action Element? That's a classic mistake. How else would the data get passed from the parent to the embedded OmniScript?

upvoted 0 times

...

Kimberlie

14 days ago

Hmm, I'm not sure about that. Doesn't the flag passData.JSON need to be configured correctly in the parent OmniScript? Seems like a potential issue there.

upvoted 0 times

Reita

6 days ago

I think you might be right. The flag passData.JSON in the parent OmniScript could be the issue.

upvoted 0 times

...

Rory

22 days ago

I think it could also be because of the element name conflict between the parent and embedded OmniScripts.

upvoted 0 times

...

Lavera

24 days ago

The issue here is definitely with the WLC PubSub Message flag not being set in the parent OmniScript. That's the only way to pass data between OmniScripts.

upvoted 0 times

Wilson

4 days ago

I think you're right, the WLC PubSub Message flag needs to be set in the parent OmniScript.

upvoted 0 times

...

Audry

26 days ago

I agree with Pete. The flag might not have been set in the parent OmniScript.

upvoted 0 times

...

Pete

1 months ago

I think the issue might be with the WLC PubSub Message flag.

upvoted 0 times

...