What are two possible use- cases for a FlexCard?

FlexCards are a core component of OmniStudio, designed to display contextual information and actions. A primary use case is to aggregate data from multiple sources using a DataRaptor and present it as "at-a-glance" summary information on a record or home page (C). This allows users to quickly understand complex data without navigating to multiple records.

Another key function is to act as a launchpad for user actions. FlexCards can be configured with buttons or links to initiate common processes, such as starting a guided workflow (OmniScript), navigating to another page, or triggering a Quick Action, making them ideal for homepage widgets (D).

A. While FlexCards can launch editing actions, complex inline edits and calculations within a table are more characteristic of an OmniScript or a custom Lightning Web Component, which a FlexCard might host.

B. Asking multiple pages of questions is the primary function of an OmniScript, which is designed specifically for creating guided, step-by-step user processes and forms.

1. Salesforce Trailhead, OmniStudio Documentation, FlexCards Basics module, "Get to Know FlexCards" unit.

This unit states, "FlexCards summarize contextual information at a glance... With FlexCards, you can... Display a 360° view of the customer..." This directly supports option C. It also states, "FlexCards are the beginning and end of customer transactions. They are the portals through which a user launches a process..." This directly supports option D.

2. Salesforce Help, OmniStudio Documentation, Build a Basic FlexCard.

The documentation outlines the core purpose: "Create cards that display information from multiple data sources and that users can act on." This reinforces that the two main functions are displaying aggregated data (C) and providing actionable elements (D).

3. Salesforce Help, OmniStudio Documentation, OmniScripts section.

The documentation describes OmniScripts as the tool for creating "guided paths for completing a business process." This confirms that multi-page forms (B) are the domain of OmniScripts, not FlexCards.