Working with bundle and kit versions
The Category Manager or Product Manager can manage versions of bundles and kits.
When you create
a bundle or kit version, the following parts of the bundle or kit
are saved in the version repository:
- Code
- Name
- Short description
- Long description
- Keyword
- Manufacturer
- Manufacturer part number
- URL
- Parent category (Reference to the parent category)
- Recurring order item
- For purchase
- On special
- Announcement date
- Withdrawal date
- Display to customers
- Thumbnail (Reference to the image but not the image itself)
- Full image (Reference to the image but not the image itself)
- Custom fields (Field 1, Field 2, Field 3, Field 4, Field 5)
- Descriptive attributes
- Associated assets (References to the assets. For example, if you modify the assets, the changes are reflected in the version)
The following part is only saved in the version repository for bundles and kits:
- Components (References to the components. For example, if you modify the component, the changes are reflected in the version)
The following parts are only saved in
the version repository of dynamic kits when WebSphere Commerce is
integrating with Sterling Configurator:
- Model
- Preconfiguration (References to the preconfiguration components. For example, if you create, replace or delete the preconfiguration, the changes are reflected in the version.)
The following part is only saved in the version repository of kits:
- List price (only if pricing is managed within the Catalogs tool)