Using Revise with Configurable Modules and Variants
Produce variants represent a specific configuration, as captured by a variant specification, of a configurable product structure. This section describes the additional consideration on how the association between them is managed when either the variant specification or the variant is revised.
 |
• The roles (configurable module or variant part) can be revised in any order or as a part of a single change notice.
• The association between a configurable module and a variant is not copied to the resulting new copy after using the Copy or Save As action.
|
To control the propagation of a generic part (configurable module) to variant links, the following properties can be configured in the wt.properties file:
• wt.generic.variantLinkBehaviorOnRevise (String property)
• com.ptc.wpcfg.variants.move.latest.revision.link (Boolean property)
Revising Configurable Modules
When a configurable module is revised and the default configuration is used, the new revision is associated with the same variants as the previous revision of the configurable module.
An optional configuration allows only the latest revision of the variant to be carried forward to the new revision of the configurable module when the configurable module is revised. For example, revision A of the configurable module has one variant having both revisions A and B. When the configurable module is revised to revision B, then it is associated with only revision B of the variant as it is the latest revision.
The com.ptc.wpcfg.variants.move.latest.revision.link property controls this configuration. When the property is not set or is set to false, the default behavior is provided. When the property is set to true, the optional behavior is provided.
This property is also used when revising the variant. For additional information, see the “Revising Variants” section below.
Revising Variants
When revising variants, the outcome is influenced by two separate configuration settings. One setting controls whether the associations are moved, copied, or not carried forward to the new revision, while the other setting controls whether associations moved or copied are limited to the latest. The property controlling the operation to copy, move, or ignore the association to the configurable module is evaluated first, followed by the property limiting the operation to the latest is evaluated.
The property wt.generic.variantLinkBehaviorOnRevise, in the wt.properties file, can be configured using any of the following values:
• copy: When this value is specified or the property is not set, the new revision of the variant is associated to the same configurable module as its predecessor revision and the processor revision retains its associations.
◦ When com.ptc.wpcfg.variants.move.latest.revision.link is set to false or the property is not defined, the new variant revision will be associated to all the same revisions of the configurable module as its predecessor revision, the processor revision retains its associations.
◦ When com.ptc.wpcfg.variants.move.latest.revision.link is set to try, the new variant revision will be associated to only the latest revision of the configuration module from its processor revision, the processor revision retains its associations.
• move: When this value is specified, the new revision of the variant is associated to the same configurable module as its predecessor revision, but the predecessor revision no longer retains these associations.
◦ When com.ptc.wpcfg.variants.move.latest.revision.link is set to false or the property is not defined, the new variant revision will be associated to all the same revisions of the configurable module as its predecessor revision, the processor revision does not retain its associations.
◦ When com.ptc.wpcfg.variants.move.latest.revision.link is set to try, the new variant revision will be associated to only the latest revision of the configuration module from its processor revision, the processor revision does not retain its associations.
• nocopy: When this value is specified, the new revision of the variant is not associated to the configurable module. The com.ptc.wpcfg.variants.move.latest.revision.link property does not apply when nocopy is used.