What does component based mean in specifications?
- Customer Quasydoc
Component based means that data is inherited from an underlying component in the product structure. This underlying product is the same product in a different form (for example, different packaging). Thus, a packaged component based product can use data from the "bare product" using the component based specification technology.
Component based is only applicable to internal specifications and information specification providers.
Example:
Component based products | Peas packed 200g | Peas packed 300g | Peas packed 500g |
|---|---|---|---|
Naked product | Peas | ||
Component based is a setting that needs to be activated by Quasydoc before it is visible in the specifications.
What is a component based specification?
Component based specifications are specifications where the template indicates that the specification uses data from underlying components.
The data that is inherited from the component is component based. Regular fields can also be added in the specification that relate to the current product, for example, about packaging information.
Only fields that are designated as component based are considered so. By clicking on the edit icon of the field you can indicate whether the data is inherited from an underlying FOOD or NON FOOD component.
The following fields can be designated as component based:
Linked values
Product details
Product details supplier
Textual values
Table of input fields
Parameters
Parameter table
Entering a component based specification
To inherit component based data, an up-to-date specification must be present with the underlying component. This specification does not have to be a component based specification.
If fields are marked as component based in the specification template, the inherited fields cannot be modified in the specification.
Behind the component based fields is an info icon. This icon indicates the underlying specification from which the field has been filled.