---
schema_version: "1"
id: 2a8a41654e4f0bd6db5ee92f7d7cbc8738268599b1446e0a77bec13b5429abe9
title: Configuring a Card (Managed Package)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_configuring_a_card.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_configuring_a_card.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: e2c94886ee796ba84ece4d7dfab2e02334ecec1b6c46b243ab49a5b56fc8b870
description: "For the managed package runtime, to configure a card on a layout, set these optional properties:"
products:
  - Omnistudio
release: "264"
---
# Configuring a Card (Managed Package)

For the managed package runtime, to configure a card on a layout, set these optional properties:

![Managed Package app icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/resources-global/_corporate/images/managedpackageicon.png) This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see [Omnistudio Help](https://help.salesforce.com/s/articleView?id=xcloud.os_omnistudio_standard.htm&language=en_US).

1. To create a new version of a card, click **Create Version**. The new version is added underneath the current card. Creating a version of the card creates an exact copy of the card with a Version equal to the latest version number plus one, such as **Version 2**. See [Cards Framework Versioning (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_cards_framework_versioning.htm&release=264.0.0&type=5 "For the managed package runtime, the Vlocity Cards Framework supports versioning for all components. The name, author, and version combination must be unique for each component of a given type (layout, card, or template) in an org.").
2. To filter the output of the returned data from the data source:
    
    1. In the **Filter** section of the card, click **\+ Add Filter**.
    2. In the first column's input field, enter the name of a field returned from the data source. For example, \['AccountName'\]. To view available data fields to filter, click **View Data** in the card or the card layout.
    3. In the second column's input field, enter the value to filter. For example, Acme.
3. To configure a card to store data from the data source, or to enable additional features from a card template, in the **Card Session Variables** section, click **\+ Add Session Variables** to enter a variable **Name** and **Value**.
4. To use metatags to enable search engine optimization (SEO) options in your metadata, click +Add Metatags. The metatags feature enables the layout to write metatags to a page header. Available card metatags are:
    
    - `author`
    - `description`
    - `keywords`
    - `viewport`
    
    The metatags are inserted after a layout or card loads, whether or not the data source is set.
    
    Vlocity recommends that you replace metatags with the same name. Do not duplicate metatags. Web crawlers ignore duplicate tags.
5. Select a data source for the layout in the **Data Source** field.
    
    The data source holds the master query that returns results in a JSON structure for cards in the layout. For example, you might query every policy associated with an account, then create a card for each policy type. For more information on how to configure a data source and to see a complete list of data sources, see [Configuring Data Sources](https://help.salesforce.com/s/articleView?id=xcloud.os_configuring_data_sources_for_cards_components.htm&release=264.0.0&type=5 "For the managed package runtime, configure a data source on a card, layout, or flyout to retrieve data from a Salesforce object or an external database. Display the returned data on cards in a layout or flyout.").
    
    ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/images/icon_note.png)
    
    Note
    
    Cards can have data sources different from the layout data source.

What’s next: Add card states to your cards. See [Adding a State to a Card (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_adding_a_state_to_a_card.htm&release=264.0.0&type=5 "For the managed package runtime, add card states to display data fields from the card or card layout data source, to present different interactions and layouts based on specified conditions, to add actions, and to add flyouts to display additional information about a record. For example, for cards displaying past due policy information, use a card state template, and display actions, fields, and flyouts different from those on cards displaying information for active policies in good standing.").