Vocabulary - Catalogue Data
Additional Product
A Product can have sub products. They can either be permanently attached to their parent product, or part of a Product Configuration. When being part of a Product Configuration it will be loading depending on the Feature/Option it belongs to being selected or deselected.
An Additional Product can also be optional in itself. It will then be possible to select or deselect it without use of Feature/Option. Optional Additional Products are by default deselected at load.
Additional Products can be recursively defined, that is, an Additional Product can have Additional Products itself. However, loops are not valid.
ApplicationAreas
For each Catalogue there can be a number of default Material Mappings. The name ApplicationAreas can be a bit misleading, as for the context of the Web Configurator it is only used for Material Mapping.
Catalogue
Vendor / PrdCat / PrdCatVersion / PriceList
A Catalogue is a collection of Products. The Products in the catalogues are viewed through a filter of Vendor, PriceList and PrdCatVersion. These parameters can affect what products are shown in the Catalogue and aspects of the Products such as their price. While Vendor and PriceList are parameters that can be user selected PrdCatVersion is set by the Catalogue administrator and exists to guarantee that the right version is loaded.
Catalogue Stretch
It is not uncommon for Products to be orderable in custom sizes. Like the width and depth of a table, or the height of legs. Catalogue Stretch allows content creators to create Products where one Model can be stretched, driven by how the end user configures the product (Product Configuration).
CmSym
CmSym is the most recent Model format used by Configura. CmSym is build on to of the Dex-file-format. It can beside geometry also contain other data, such as Materials.
If you use babylon-view or babylon-view-react to view your Products the format is handled in the background. If you build your own viewer we strongly recommend you use our package web-core to read it.
Enterprise
The highest level of grouping in the Catalogues system.
Exerciser
Allows you to loop through viewing a number of Products and Catalogues to test them. Used by the test-app.
Model
A Model contains geometry, with some added data. Models can and is often reused between Products. If you have multiple Products using the same base it would be appropriate to use the same Model in all of them. Due to browser caching this will also help performance in the user end.
What Materials should be applied where is outlined using tags in the Models. Models are hierarchical tree-structures. How they are organized is depending on what tool generated them.
Portfolio
A Portfolio is a collection of Catalogues.
The ID of a Portfolio is for legacy reasons called a 'CID'. The ID of a Catalogue is in turn called 'prdCat'.
Product
A Product is an item in a Catalogue. It consists of Models outlining the geometry, Materials defining the surface look, configuration (Product Configuration) selecting what Models and Materials will be used and Features outlining what Models and Materials can be chosen.