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.
This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.
Use the following fields to create unique versions of a component:
|
Field |
Description |
|---|---|
|
Name |
Components are requested by name. |
|
Author |
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. |
|
Version |
An integer that increases by one with every new version. |
|
Active |
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. |
- Card and Card Layout Naming Conventions (Managed Package)
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)
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)
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)
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)
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)
For the managed package runtime, this example shows the differences in versioning between a clone and a new version. - Versioning Best Practices (Managed Package)
For the managed package runtime, consider the following best practices for versioning in Omnistudio. - Exporting Vlocity Layouts and Cards (Managed Package)
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.