You are here:
Flexcards and Vlocity Cards Framework (Managed Package)
For the managed package runtime, the Vlocity Cards Framework provides a set of tools to build customer-centric, industry-specific UI components and applications on the Salesforce platform. Create dynamic and engaging omni-channel customer experiences, rich in information and actions relevant to the customer's context with cards.
This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.
When using Vlocity admin tools in the Lightning Console, note that the process to launch a Vlocity object home page (like the Omniscript Designer, Cards Designer, and so on) has changed as of SFDC Winter '19. For the optimal experience, create a new primary tab by CTRL-clicking the link (or Cmd-clicking on the Mac) in the Console's tab selection menu. From the new primary tab, you can open objects in a sub-tab of that primary tab.
Cards are containers for a related group of information. They display Salesforce object information along with discrete, clickable actions that change according to the context in which they appear and based on the information that they contain. Build interfaces with Salesforce specific or external data sources.
The Vlocity Cards Framework features a card designer, a declarative tool used to build cards. Add content to states and create conditions for any state to determine what content displays when. Accelerate incremental development by previewing and testing your interface with actual data from a live Preview tab. Save and activate the card to generate the component to add to your Lightning or Community page.
Beginning with Vlocity Health and Insurance Summer '19, Vlocity supports Salesforce's Lightning Web Components programming model with Vlocity Lightning Web Components. Vlocity Lightning Web Components include components, functionalities, and templates exclusive to LWC enabled cards. With LWC Cards you can use standard JavaScript and HTML to modify and extend Vlocity products.
Classic Card Designer
With the Classic Designer, some coding is required to customize your interfaces. The design and layout of your cards are determined by templates that you can modify in the Template Designer if Angular, or extend in a local development environment if LWC enabled. Each card can have a different data source, including back-office systems other than Salesforce. A large library of Vlocity templates enables you to get ahead of the design process.
Because everything gets built on industry-standard web technologies such as HTML5, CSS3, AngularJS (for Angular Cards only), and Sass, you can perform deeper template branding and customization with your web developers, as desired.
Enable Lighting Web Components in the Classic Card Designer to turn on LWC features and generate a Lightning web component instead of an Angular component to add to your Lightning or Community page.
Flexcard Designer
With the Flexcard Designer, build cards without code using a drag interface and WYSIWYG editing. Drag elements, such as data fields, actions, data tables, charts, icons, images, and so forth, onto a canvas to build the layout of your card. Create the look and feel of the card with graphic user interfaces (GUIs) built into the designer to style individual elements.
From one action element, add actions that enable your users to update Omniscripts, pass data from an Omniscript to a Flexcard, embed cards inside each other, trigger events, create event listeners, and more.
Because the Flexcard Designer is built with the Lightning Web Components programming model, the saved and activated Flexcard generates an LWC component to add to your Lightning or Community page.
- Flexcards (Managed Package)
For the managed package runtime, build customer-centric, industry-specific UI components and applications on the Salesforce platform with Flexcards. Display Salesforce object information along with distinct, clickable actions that change according to the context in which they appear and based on the information that they contain. - Classic Cards (Managed Package)
For the managed package runtime, Classic Cards in the Vlocity Cards Framework are UI components rich in information and actions relevant to the customer's context. The Classic Card Designer is a declarative tool to create cards and card layouts, with minimal HTML, CSS, and AngularJS coding. - Backward Compatibility Support for Passing Page Params (Managed Package)
For the managed package runtime, if you pass a page parameter to a Lightning page you must use a namespace prefix, such as params.ns_contactId, wherensrepresents your namespace prefix. For backward compatibility on older Angular cards, both the page parameter with and without the namespace prefix are read, such as params.contactId and params.ns__contactId. - Cards Caching (Managed Package)
For the managed package runtime, cards, card layouts, templates, custom labels, and profile data load from the VlocityMetadata partition of the Platform Cache when the card is active and viewed from a record page or a community page. You can clear, enable, or disable the user session cache and specific types of data from the Platform Cache. - Enable and Disable Data Sources (Managed Package)
For the managed package runtime, enable and disable data source types for an org, profile, or user level from the Card Framework Configuration custom setting. For example, disable Apex REST, Apex Remote, and other complex data sources for your entire org, or prevent system admins with limited permissions from using these data sources. - Vlocity Customer Story (Managed Package)
For the managed package runtime, a Customer Story is a history of events for an Account or a Contact. Customer stories are driven by metadata configuration. It displays a timeline of all interactions with the customer in a single, chronological feed.
