1. What is FlexCard?
Ans: A Flex Card is like a info-packed block, offering key details and links specific to a context. For instance, an account card could show things like status, priority agreement, and creation date.
2. How do you define the name of your FlexCards?
Ans: When naming your FlexCards, skip spaces, dashes, or funky symbols. Stick to letters and numbers. Choose either camel case (like “createAccountRecord”) or Pascal case (like “CreateAccountRecord”) for the name. Steer clear of two underscores in a row. Good examples include “createAccountRecord” and “create_Account_Record.”
3. What Data Sources can you use with FlexCards?
Ans: FlexCards can pull data from various sources, including SOQL Query for Salesforce data, SOSL Search for text-based queries, Apex Remote for Apex Remote calls, Apex REST for Apex REST calls, DataRaptor for Vlocity DataRaptors, REST for standard REST API calls, Integration Procedures for Vlocity Integration Procedures, Streaming API for event streaming in near real time, and Custom for using sample JSON.
4. What’s the scoop on FlexCard Actions?
Ans: FlexCard Actions are the power moves for launching or updating OmniScripts, navigating, displaying flyouts, firing events, or updating data field values. Check out these available actions:
- Card: Handles card-level actions like reload, updating data source, and removal.
- Event:
- Custom: Fires a Custom Event to alert the parent FlexCard of an occurring event.
- PubSub: Fires a PubSub Event to notify another component on a page or application.
- Flyout: Shows extra info from a child card, OmniScript, or custom Lightning web component in a modal or popover.
- Navigate: Choose a target URL or PageReference type for Lightning Experience, Communities, or an external web address.
- OmniScript:
- Launch: Fires up an OmniScript from the FlexCard.
- Update: Refreshes an OmniScript from a FlexCard embedded as a custom Lightning web component in an OmniScript.
- OmniScript Action: Launches OmniScripts, components, web pages, or external applications from a reusable OmniStudio Action. One action can launch the same OmniScript from multiple FlexCards.
5. Can you explain the Flexcard?
Ans: FlexCards are your go-to for summarizing info at a glance, showing details when needed, and offering quick access to context-specific tasks. Picture a call center scenario—agents interact with customers, view their info, and kick off guided processes right from the FlexCard during calls.
Here’s the lowdown on FlexCards:
- Summarize Contextual Info in a snap.
- Start and end customer transactions with FlexCards.
- Design them to meet customer needs.
- View them on any device or channel like Adobe Experience Manager or in a custom web container.
- FlexCards can blend internal Salesforce info with external data.
- Build them quick with Drag-and-Drop in FlexCard Designer.
- The WYSIWYG editor in FlexCard Designer gives you style control without templates.
- Embed them in other FlexCards or an LWC OmniScript.
- Show details with Flyouts and display elements conditionally.
6. Tell me about Flex Card Designer.
Ans: Flex Card Designer is your go-to for swift configuration, previewing, and debugging of cards. It’s a powerhouse where you can drag, drop, position, and resize UI elements on a canvas—think text, buttons, icons, images, links, charts, tables, and even other Flex Cards. Plus, in the Designer, you can set up actions to launch or update OmniScripts, navigate, display flyouts, fire events, update field values, and more.
7. What does Flex Card Designer do?
Ans: Flex Card Designer lets you swiftly set up, preview, and debug cards. You can arrange text, buttons, icons, images, links, charts, tables, and other Flex Cards using drag-and-drop on a canvas. Plus, you can create actions that open or modify Omni Scripts, navigate to web pages or apps, display flyouts, trigger events, adjust field values, and more within the Flex Card Designer.
8. Can you Explain FlexCard in Vlocity.
Ans: FlexCard Designer makes Vlocity configuration a breeze, allowing for quick and easy setup to complete the entire development process.
9. Can you explain the Email Action?
Ans: The OmniScript Email action utilizes the Salesforce Email API to send an email design template to a user, lead, or contact, or deliver a physical email body specified in the action configuration to any email address.
