| Marketing Name
|
The
marketing name of the product
configuration.
|
| Name
|
The name of the product configuration.
Click to open.
|
| Based On
|
The name of the model version or
logical feature on which this product
configuration is based.
|
| Model Version
Context
|
Shows in the list of all product
configurations only.
If the based-on object is a logical
feature, specifies which model version
uses that logical feature for this specific product configuration.
|
| Date Effectivity
|
The date on which this product
configuration is
effective.
|
| Description
|
Details about the configuration.
|
| State
|
Current state of the product configuration
in its lifecycle.
|
| Owner
|
Person responsible for the product
configuration.
|
| Completeness Status
|
Indicates how complete the product
configuration is:
- Partial: At least one "must
select" variant does not have a value, part of the model version definition is
missing—the resulting model version is partial.
- Complete: All "must select"
variants have a value and "single select" option groups have no more than one
option selected—the resulting model version is coherent and complete.
- Hybrid: At least one "single
select" option groups has multiple options selected, so the resulting model
version is a mix of several valid model version—it is hybrid.
|
| Rule Compliancy Status |
Indicates whether the product configuration
is compliant with
configuration rules:
- Valid: Selected configurations are
all compatible. No conflict was found.
- Invalid: Some selected
configurations are not compatible. They are in conflict with one or more rules
defined in the system.
- Unknown: No status was computed.
Rules are disabled.
|
| Sales Intent
|
Indicates how the configuration is intended
to be used to sell the model version:
- Standard Configuration: Can be
sold in the market and appears in a model version catalog.
- Custom Configuration: Created for
one customer and is not available in the model version catalog.
|
| Purpose
|
Indicates how the product configuration
will be used:
- Evaluation: For internal
engineering, for example, to test
configuration rules.
Note:
It is possible to create an invalid configuration for
evaluation purposes, and to generate a
BOM from an invalid configuration for
prototyping. If your company prefers that this be blocked, your Business
Administrator can hide the command action when the configuration is invalid.
- Order: For sale to customers.
- Accessory: For a product
configuration in the context of a logical feature, the purpose is
Accessory and cannot be changed.
|
 (Open in New Window) |
Click to open the product configuration in a new window. |
.
