New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Certified Omnistudio Consultant (Plat-Con-201) Exam - Topic 4 Question 86 Discussion

Actual exam question for Salesforce's Salesforce Certified Omnistudio Consultant (Plat-Con-201) exam
Question #: 86
Topic #: 4
[All Salesforce Certified Omnistudio Consultant (Plat-Con-201) Questions]

A consultant is designing a FlexCard for a client. The client wants the FlexCard to launch a child card with additional information and actions related to the parent card when the agent clicks on a button. How should the consultant design the FlexCard to meet the client's requirements?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

0/2000 characters
Joana
3 months ago
A child card? Isn't that a bit complicated for just extra info?
upvoted 0 times
...
Dick
3 months ago
Definitely not C, that doesn't fit the requirement at all.
upvoted 0 times
...
Malcom
3 months ago
Wait, why would you use a new DataRaptor? That seems unnecessary.
upvoted 0 times
...
Brande
4 months ago
I think A could work too, but B is more efficient.
upvoted 0 times
...
Luisa
4 months ago
Option B sounds right, Flyout Actions are perfect for this!
upvoted 0 times
...
Wilson
4 months ago
I vaguely recall that launching a child card directly is usually the best approach, but I can't remember if that was option A or something else.
upvoted 0 times
...
Madalyn
4 months ago
I’m a bit confused about whether we should be launching a DataRaptor or an OmniScript. I feel like both could be relevant in different scenarios.
upvoted 0 times
...
Theresia
4 months ago
I think option B sounds right because Flyout Actions can provide additional context without leaving the parent card.
upvoted 0 times
...
Shannon
5 months ago
I remember we practiced a similar question about launching child cards, but I’m not sure if it was through a Flyout Action or just a direct launch.
upvoted 0 times
...
Carlee
5 months ago
I'm leaning towards option A - designing the parent card to launch a child card when the specific action is taken. That seems like the most intuitive way to give the agent the extra details they need without disrupting the main card.
upvoted 0 times
...
Lenny
5 months ago
Launching a new DataRaptor or OmniScript when the action is taken doesn't seem quite right. The client wants the additional information and actions to be in a child card, not a separate component.
upvoted 0 times
...
Tish
5 months ago
Hmm, I'm not sure about that. Launching a child card through a Flyout Action might be a better approach. I'll need to review the details on how Flyout Actions work to be sure.
upvoted 0 times
...
Anglea
5 months ago
I think the key here is to design the parent card to launch a child card when the specific action is taken. That seems like the most straightforward way to meet the client's requirements.
upvoted 0 times
...
Antonio
10 months ago
Haha, imagine the client's face if we went with Option C and tried to launch a new Data Mapper. They'd be like, 'Wait, what?'
upvoted 0 times
Carylon
9 months ago
Haha, imagine the client's face if we went with Option C and tried to launch a new Data Mapper. They'd be like, 'Wait, what?'
upvoted 0 times
...
Dominga
9 months ago
B) Design the parent card to launch a child card through a Flyout Action.
upvoted 0 times
...
Jarod
9 months ago
A) Design the parent card to launch a child card when the specific action is taken.
upvoted 0 times
...
...
Graham
10 months ago
I disagree. I think the consultant should design the parent card to launch a child card through a Flyout Action for a more interactive experience.
upvoted 0 times
...
Page
10 months ago
Option D is an interesting choice, but I think a Flyout Action (Option B) is the most straightforward solution here.
upvoted 0 times
Lanie
10 months ago
I think designing the parent card to launch a child card through a Flyout Action is the best option for this scenario.
upvoted 0 times
...
Kenda
10 months ago
I agree, a Flyout Action would make it easy for the agent to access additional information.
upvoted 0 times
...
...
Gilberto
11 months ago
I agree with Mozelle. It makes sense to directly launch the child card when the button is clicked.
upvoted 0 times
...
Breana
11 months ago
I'm leaning towards Option B as well. It's a clean and efficient way to handle the additional information and actions the client wants.
upvoted 0 times
Avery
10 months ago
Definitely, we want to make sure the child card is easily accessible for the agent.
upvoted 0 times
...
Kayleigh
10 months ago
It's important to consider the user experience when designing the FlexCard.
upvoted 0 times
...
Na
10 months ago
I agree, using a Flyout Action would make the FlexCard design more user-friendly.
upvoted 0 times
...
Malcolm
10 months ago
I think Option B is the best choice for this scenario.
upvoted 0 times
...
...
Kristel
11 months ago
Option B seems like the way to go. Launching a child card through a Flyout Action sounds like the perfect fit for the client's requirements.
upvoted 0 times
...
Mozelle
11 months ago
I think the consultant should design the parent card to launch a child card when the specific action is taken.
upvoted 0 times
...

Save Cancel