You are here:
Product Versioning
With the Product Designer , you can create and configure a product, Vlocity picklist, or Vlocity object type to track any changes.
You can introduce those changes without making them visible to sales channels or other catalog functions. When you are ready to deploy your changes, you can release a specific draft version of the product, picklist, or object type with effective dates and a custom auto-generated version number to sales channels or other catalog functions.
After you deploy a new version of the product, picklist, or object type, any further changes are not allowed to that version except for a few fields. See Lifecycle Status for Objects, Products, Projects, and Picklists. Any changes require a new version of the product, object type, or picklist.
Every versioned object supports multiple versions in draft and released states.
-
You can create a draft version from any version of the product.
-
You cannot delete released versions of product specifications, picklist values, and object types.
-
When you need to change a released version of a product specification, picklist value, or object type, you must create a new version. Released versions must have a naming scheme, effective dates, and status.
Searching and Viewing Versions
You can search for existing product specifications, offerings, picklists, and object types by several criteria, including name, description, and version. The search results show you all available versions. You can see the draft and released version details and compare two or more versions to verify the changes.
You can see the version history of your product or picklist by clicking Version History. The Versions dialog appears with the version of your product or picklist, the availability dates, and the created date. From the Versions dialog, you can click New Version and create a new version of your product or picklist.
- Versioning and EPC Entities
When you create a version of an object, commercial product, or picklist, the related entities for each are either automatically cloned or reused across the versions. - Lifecycle Status for Objects, Products, Projects, and Picklists
The Lifecycle Status field is available for objects, product specifications, product offers, picklists, and EPC projects. Using the lifecycle status allows you to manage changes to picklist values over time in a controlled way. - Versioning Reference Dates
For versioned products, reference dates determine which product version to use and affect the product structures. The reference dates and their use vary by object and business process. The availability of products is not based solely on the Versioning Start and End dates. - Product Versioning Start and End Dates
A product version’s Versioning Start Date Time and Versioning Start End Time fields are key for runtime use. The version of a product is picked during runtime, and the available version is derived from these fields. - Enable Versioning in EPC
To use the versioning feature in Product Designer and CPQ, you must update the product data and enable the feature. - Create New Versions of Picklists
With Product Designer, you can track changes to picklist values. When you need to change a released version of a picklist, create a new version. - Create New Versions of Object Types
Use Product Designer to track changes to object types. For example, you can track changes whenever you add a new Attribute Assignment to an ObjectType or make an existing AttributeAssignment inactive. You can also add or remove Product2 fields to or from an ObjectType. - Create New Versions of Products
As a product administrator, you can create a version of a product offer in a workspace in draft mode and modify the product offer until you release it. If you need to change a released version of a product offer, create a new version and apply your changes to it. - View Version History and Compare Versions
To see how products and offerings have changed, you can view their version history and compare versions for additions, modifications, and deletions. - Export a Product Version Report
You can create a PDF report that lists all the related objects for a specific version of a product specification or offer. The newer version clones or inherits these related objects. Use this report to review and approve changes for new versions. - DataPacks and Data Migration with Versioning
With the introduction of product versioning, the related objects of a product are classified into two categories: cloned (version dependent) and reused (version agnostic). Both types of objects are migrated, and all versions of a product are migrated.
