Answer : B
Comprehensive and Detailed In-Depth The requirement is for a FlexCard (parent card) to launch a child card with additional information and actions when an agent clicks a button. In Salesforce OmniStudio, the Flyout Action is the specific mechanism designed within FlexCards to achieve this, making B the most precise and correct answer.
Here's why B. Design the parent card to launch a child card through a Flyout Action is the correct answer:
Flyout Action Overview: A Flyout Action in FlexCards is an interactive feature that displays a pop-up panel (flyout) when triggered, typically by a button or link. This flyout can contain a child FlexCard, OmniScript, or custom content, showing additional details or enabling actions related to the parent card's data.
Meeting the Requirement:
Child Card Launch: The Flyout Action can embed a child FlexCard, which displays supplemental information (e.g., related records or details) and includes actions (e.g., buttons to update data).
Button Trigger: In the FlexCard Designer, the consultant can add a Button element to the parent card, configure its action type as ''Flyout,'' and link it to a child FlexCard. When the agent clicks the button, the flyout appears with the child card.
Contextual Data: The parent card's data (e.g., a record ID) can be passed to the child card via the Flyout Action's context parameters, ensuring the child card shows relevant information.
Example: If the parent card displays a customer's summary (name, account number), clicking the button could launch a child card in a flyout showing order history and a button to initiate a return, all tied to the parent card's account ID.
Now, let's examine why the other options are incorrect or less optimal:
A . Design the parent card to launch a child card when the specific action is taken: While this is conceptually correct, it's vague and lacks specificity. ''Launch a child card'' isn't a defined OmniStudio action---Flyout Action is the actual mechanism to achieve this. Thus, B is the more precise answer, as it names the tool explicitly supported by FlexCards.
C . Design the parent card to launch a new DataRaptor when the specific action is taken: A DataRaptor (e.g., DataRaptor Extract) retrieves or manipulates data, not displays a UI like a child card. While a DataRaptor might fetch data for the child card, it doesn't ''launch'' anything visible to the agent, making this option irrelevant to the UI requirement.
D . Design the parent card to launch a new OmniScript when the specific action is taken: An OmniScript could be launched via a FlexCard action (e.g., an ''OmniScript'' action type), but it's a guided process, not a ''child card.'' The requirement specifies a child card (implying another FlexCard), not a multi-step script, so a Flyout Action with a child FlexCard is more appropriate than an OmniScript.
Salesforce OmniStudio Documentation: FlexCard Actions -- Details the Flyout Action for launching child cards or content.
Salesforce OmniStudio Developer Guide: Flyouts in FlexCards -- Explains configuring flyouts with child FlexCards.