Question 41
Choose 2
A pop-up window will display additional information about the campaign, such as details about the members. A button must initiate a guided process to add new leads to the campaign.
Which two FlexCard features should the consultant recommend to meet these requirements? Choose 2 answers
Which two FlexCard features should the consultant recommend to meet these requirements? Choose 2 answers
Correct answer:
B. OmniScript Action
E. Flyout Action
Explanation
The requirement has two distinct parts, and we need to identify the FlexCard features that address each one directly.
"A pop-up window will display additional information about the campaign, such as details about the members."
This describes a Flyout. A Flyout is a panel that slides out or pops up to display additional information that isn't visible on the main card.
Correct Feature: E. Flyout Action
Why: You would configure an element (like a button or a link labeled "View Members") with a Flyout Action. When the user clicks it, the flyout opens. Inside this flyout, you could use a Data Table (Option D) to neatly display the list of campaign members, but the action that triggers the pop-up window itself is the Flyout Action.
"A button must initiate a guided process to add new leads to the campaign."
This describes launching an OmniScript. A "guided process" is the textbook definition of an OmniScript.
Correct Feature: B. OmniScript Action
Why: You would add a button to the FlexCard and configure its action as an OmniScript Action. This action would be set to launch a specific OmniScript (the one designed for adding leads to a campaign). This provides the step-by-step, form-based experience implied by "guided process."
How the Features Work Together: The consultant would likely design the FlexCard to have:
A "View Members" button with a Flyout Action that opens a panel containing a Data Table of existing members.
A separate "Add Leads" button with an OmniScript Action that opens the guided process in a modal window or a new tab.
Why the Other Options Are Incorrect:
A. Block Element: A Block Element is a container for organizing the layout within a card or flyout. It is not an action that triggers a pop-up or launches a process. It's a structural component, not a functional one for this use case.
C. Interaction Launcher: This is a distractor. While it sounds relevant, "Interaction Launcher" is not a standard, named feature within the FlexCard toolbox. The specific actions you configure are "OmniScript Action," "Flyout Action," "URL Action," etc.
D. Data Table: A Data Table is a display element used to show a list of records in a tabular format. It is what you would put inside the flyout to show the member details, but it is not the feature that creates the pop-up window. The action that creates the pop-up is the Flyout Action.
Summary / Key Takeaway:
To meet both requirements, you need two different types of Actions on your FlexCard:
A Flyout Action to create the pop-up for displaying information.
An OmniScript Action to launch the guided process for adding records.
Reference:
The configuration of these actions is a fundamental part of building interactive FlexCards and is covered in the "Add Actions to FlexCards" unit of the OmniStudio Trailmix on Trailhead.
The requirement has two distinct parts, and we need to identify the FlexCard features that address each one directly.
"A pop-up window will display additional information about the campaign, such as details about the members."
This describes a Flyout. A Flyout is a panel that slides out or pops up to display additional information that isn't visible on the main card.
Correct Feature: E. Flyout Action
Why: You would configure an element (like a button or a link labeled "View Members") with a Flyout Action. When the user clicks it, the flyout opens. Inside this flyout, you could use a Data Table (Option D) to neatly display the list of campaign members, but the action that triggers the pop-up window itself is the Flyout Action.
"A button must initiate a guided process to add new leads to the campaign."
This describes launching an OmniScript. A "guided process" is the textbook definition of an OmniScript.
Correct Feature: B. OmniScript Action
Why: You would add a button to the FlexCard and configure its action as an OmniScript Action. This action would be set to launch a specific OmniScript (the one designed for adding leads to a campaign). This provides the step-by-step, form-based experience implied by "guided process."
How the Features Work Together: The consultant would likely design the FlexCard to have:
A "View Members" button with a Flyout Action that opens a panel containing a Data Table of existing members.
A separate "Add Leads" button with an OmniScript Action that opens the guided process in a modal window or a new tab.
Why the Other Options Are Incorrect:
A. Block Element: A Block Element is a container for organizing the layout within a card or flyout. It is not an action that triggers a pop-up or launches a process. It's a structural component, not a functional one for this use case.
C. Interaction Launcher: This is a distractor. While it sounds relevant, "Interaction Launcher" is not a standard, named feature within the FlexCard toolbox. The specific actions you configure are "OmniScript Action," "Flyout Action," "URL Action," etc.
D. Data Table: A Data Table is a display element used to show a list of records in a tabular format. It is what you would put inside the flyout to show the member details, but it is not the feature that creates the pop-up window. The action that creates the pop-up is the Flyout Action.
Summary / Key Takeaway:
To meet both requirements, you need two different types of Actions on your FlexCard:
A Flyout Action to create the pop-up for displaying information.
An OmniScript Action to launch the guided process for adding records.
Reference:
The configuration of these actions is a fundamental part of building interactive FlexCards and is covered in the "Add Actions to FlexCards" unit of the OmniStudio Trailmix on Trailhead.
