---
schema_version: "1"
id: 7a0f983ce8fb2183941deef3e37b8aa0a7532418a93e52b711fc121ccf4ad3fb
title: Cards Framework Versioning (Managed Package)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_cards_framework_versioning.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_cards_framework_versioning.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: ed6bfc3313f585e6586b5c0b01d893d8adc729fc380fbe2a5fe29e32469f2537
description: 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.
products:
  - Omnistudio
release: "264"
---
# Cards Framework Versioning (Managed Package)

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.

![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).

Use the following fields to create unique versions of a component:

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col>
          <col>
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d172335e50">
              <p style="margin-bottom:0;">Field</p>
            </th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d172335e56">
              <p style="margin-bottom:0;">Description</p>
            </th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d172335e50 ">
              <p style="margin-bottom:0;">
                <strong class="uicontrol">Name</strong>
              </p>
            </td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d172335e56 ">
              <p style="margin-bottom:0;">Components are requested by name.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d172335e50 ">
              <p style="margin-bottom:0;">
                <strong class="uicontrol">Author</strong>
              </p>
            </td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d172335e56 ">
              <p style="margin-bottom:0;">Specifies the user organization that created the record. Use author names
                that describe the team creating the content. Vlocity-authored components
                have Vlocity as the author. You cannot modify these components, but you
                can clone them.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d172335e50 ">
              <p style="margin-bottom:0;">
                <strong class="uicontrol">Version</strong>
              </p>
            </td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d172335e56 ">
              <p style="margin-bottom:0;">An integer that increases by one with every new version.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d172335e50 ">
              <p style="margin-bottom:0;">
                <strong class="uicontrol">Active</strong>
              </p>
            </td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d172335e56 ">
              <p style="margin-bottom:0;">Indicates whether a record is active for runtime use. One active record
                per name is allowed in an org. Activating a component deactivates all
                other components of the same type that have the same name. Only active
                records are exported when a DataPack is created.</p>
            </td>

          </tr>
        </tbody>
      </table>

- **[Card and Card Layout Naming Conventions (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_card_and_card_layout_naming_conventions.htm&release=264.0.0&type=5)**  
    For the managed package runtime, follow Vlocity's requirements and best practices when naming cards and card layouts.
- **[Activation in the Cards Framework (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_activation_in_the_cards_framework.htm&release=264.0.0&type=5)**  
    For the managed package runtime, multiple versions of a component can exist, but only one version at a time can be active.
- **[Versioning in the Cards Framework (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_versioning_in_the_cards_framework.htm&release=264.0.0&type=5)**  
    For the managed package runtime, creating a version of a component creates an exact copy of the record with a Version equal to the latest version number plus one.
- **[Cloning in the Cards Framework (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_cloning_in_the_cards_framework.htm&release=264.0.0&type=5)**  
    For the managed package runtime, when you clone a component, you must change the **Name** and/or **Author** fields.
- **[Understanding the Author of a Card Layout (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_understanding_the_author_of_a_card_layout.htm&release=264.0.0&type=5)**  
    For the managed package runtime, the **Author** property in templates, layouts, and cards specify the user organization that created the record.
- **[Sample Versioning Workflow (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_sample_versioning_workflow.htm&release=264.0.0&type=5)**  
    For the managed package runtime, this example shows the differences in versioning between a clone and a new version.
- **[Versioning Best Practices (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_versioning_best_practices.htm&release=264.0.0&type=5)**  
    For the managed package runtime, consider the following best practices for versioning in Omnistudio.
- **[Exporting Vlocity Layouts and Cards (Managed Package)](https://help.salesforce.com/s/articleView?id=xcloud.os_exporting_vlocity_layouts_and_cards.htm&release=264.0.0&type=5)**  
    For the managed package runtime, when deploying components in a new org, you must export any applicable Vlocity Cards framework components, particularly those that you modified. The Vlocity Cards Framework supports versioning for all components (layouts, cards and templates). Only active versions are exported.