Standalone Variant Specification Associated with a Configurable Module
This variant specification is used to manage a fully-defined filter applied to a specific view version to define, and optionally to generate, a variant solution or a configuration context. It can be created using the Configure process or programmatically loaded. It can be updated through the Reconfigure process or programmatically loaded. Unique to XML loading, rules processing is not applied and any selected choices in the Option Filter are considered user selected.
• Requires Name and Location for creating or Number for updating the variant specification.
• Requires a configurable module part version with the optional ability to include the organization to uniquely identify the part and define the view-specific version.
• Is not directly associated with an option set since it is indirectly related to the Option Set assigned through the configurable module.
• Requires a part configuration specification, but provides the following defaults:
◦ When no part configuration specification is specified, a latest configuration specification is used without a lifecycle state for the view specified for the configurable module.
◦ When a part configuration specification is specified without a definition, a latest configuration specification is used without a life cyclestate for the view specified for the configurable module.
• Requires a value for applying the configuration specification to the top level but provides false value when a value is not specified.
• Optionally provides support for variant generation. When no value is specified, false value is used.
• Has the ability to refer to options and choices by Number or Name.
• Requires configuration specification for the Option Filter. When no value is provided, a latest configuration specification is used without a lifecycle state.
XML Format
<csvVariantSpec csvbatchInputFilePath="com.ptc.wpcfg.load.LoadHelper.createVariantSpec"> <csvbatchInputFilePath><PATH_FOR_VSDETAIL FILE></csvbatchInputFilePath>
<csvdescription>TEST DESCRIPTION</csvdescription>
<csvfolder>/Default</csvfolder>
<csvlifecycle/>
<csvlifecyclestate/>
<csvparentContainerPath></csvparentContainerPath>
<csvnavcriteria>NAV_CRITERIA_1</csvnavcriteria>
<csvcreatevariants>true</csvcreatevariants-->
<csvtypedef>com.ptc.wpcfg.CustomVariantSpec</csvtypedef>
</csvVariantSpec>
<csvdescription>TEST DESCRIPTION</csvdescription>
<csvfolder>/Default</csvfolder>
<csvlifecycle/>
<csvlifecyclestate/>
<csvparentContainerPath></csvparentContainerPath>
<csvnavcriteria>NAV_CRITERIA_1</csvnavcriteria>
<csvcreatevariants>true</csvcreatevariants-->
<csvtypedef>com.ptc.wpcfg.CustomVariantSpec</csvtypedef>
</csvVariantSpec>
The PATH_FOR_VSDETAIL FILE is the absolute path for another .xml file that contains information about variant specification, configurable module, and parameters.
|
Attribute
|
Description
|
Required or Optional?
|
|---|---|---|
|
csvbatchInputFilePath
|
Path of input file where variant specification details are mentioned. Details mentioned below.
|
Required
|
|
Csvdescription
|
Description for variant specification.
|
Optional
|
|
Csvfolder
|
Folder location for variant specification.
|
Optional
|
|
Csvlifecycle
|
Life cycle template for variant specification.
|
Required
|
|
Csvlifecyclestate
|
Life cycle state for variant specification.
|
Required
|
|
csvparentContainerPath
|
Container path where the variant specification must reside.
|
Required
|
|
Csvnavcriteria
|
Navigation criteria name that is mentioned in a separate section of the navigation criteria.
|
Optional
|
|
Csvcreatevariants
|
Indicator to identify whether variants must be generated for this variant specification.
|
Optional
|
|
Csvtypedef
|
Type definition for loading the variant specification.
|
Optional
|
The format for the variant specification details file is:
<specinput>
<spec name="VariantSpecification1" />
<part number="Milkshake" version="A" iteration="1" view="Design" organization="Demo Organization"/>
</specinput>
<spec name="VariantSpecification1" />
<part number="Milkshake" version="A" iteration="1" view="Design" organization="Demo Organization"/>
</specinput>
Attributes for the Standalone Variant Specification
|
Attribute
|
Description
|
Required or Optional?
|
|---|---|---|
|
Spec
|
Details about the variant specification.
|
Required
|
|
Name
|
Description of the variant specification.
|
Required
|
|
Number
|
Folder location for the variant specification.
|
Optional
|
|
Part
|
Details about the configurable part.
|
Required
|
|
Number
|
Configurable part number.
|
Required
|
|
Version
|
Configurable part version.
|
Optional
|
|
Iteration
|
Configurable part iteration.
|
Optional
|
|
View
|
Configurable part view.
|
Optional
|
|
Organization
|
Configurable part organization.
|
Optional
|
|
Parameter
|
Details about parameters.
|
Optional
|
|
Name
|
Name of the parameter.
|
Required
|
|
Value
|
Value of the parameter.
|
Required
|
 |
If you want to load a large number of variant specifications, you must enclose them between the csvBeginBulkVariantSpecification and csvEndBulkVariantSpecification tags. However, you must use these tags only when loading variant specifications that are associated with the same part and the same configuration specification information to avoid increase in memory consumption.
|
Example
<pcfg.load.LoadHelper.createVariantSpec">
<csvbatchInputFilePath>/vagrant/WindowsShareNew/EnhancedLoader/VSDetail.xml</csvbatchInputFilePath>
<csvdescription>MBT Bike Variant Specification</csvdescription>
<csvfolder>/Default</csvfolder>
<csvlifecycle/>
<csvlifecyclestate/>
<csvparentContainerPath></csvparentContainerPath>
<csvnavcriteria>NavCriteria_1</csvnavcriteria>
<csvcreatevariants>false</csvcreatevariants>
<csvtypedef>com.ptc.wpcfg.CustomVariantSpec</csvtypedef>
</csvVariantSpec>
<csvbatchInputFilePath>/vagrant/WindowsShareNew/EnhancedLoader/VSDetail.xml</csvbatchInputFilePath>
<csvdescription>MBT Bike Variant Specification</csvdescription>
<csvfolder>/Default</csvfolder>
<csvlifecycle/>
<csvlifecyclestate/>
<csvparentContainerPath></csvparentContainerPath>
<csvnavcriteria>NavCriteria_1</csvnavcriteria>
<csvcreatevariants>false</csvcreatevariants>
<csvtypedef>com.ptc.wpcfg.CustomVariantSpec</csvtypedef>
</csvVariantSpec>