For the managed package runtime, consider the following best practices for versioning in Omnistudio.
This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.
-
When working with Omnistudio-authored components in a client org:
-
Set a unique name for the new component if you are only using the original component as a template to start from.
-
Set a unique author for the new component when replacing a Vlocity component with your own inside of a larger app. For example, inside of CPQ you can replace one component without having to overwrite and clone the whole app.
-
-
When you import data packs, components of the same type are matched by Name, Author, and Version combination. If this combination is not unique, a warning is displayed that there is a pending overwrite. Importing components doesn't create new versions of them.
-
Make sure to activate your components before creating a data pack. When you export data packs, only active components are exported.
-
Use source control. This versioning workflow is not as fail-safe as the security that source control provides.
-
To work efficiently, use IDX Workbench, or, for large or complex deployments, use the Omnistudio Build Tool, which is available from GitHub. The Build Tool is a command-line tool that packages related objects together as data packs, ensuring that dependencies are preserved.