Loading Variant Specifications
This section describes loading variant specifications in Windchill to create new and update existing variant specifications.
Creating and Updating Variant Specifications Using Loader Utility
|
|
This capability is available only to members of the Platform Structures group.
|
Companies can load variant specifications in Windchill to create new and update existing variant specifications using a command-line utility that can be run from a Windchill shell using a formatted spreadsheet as input.
You can also use this application to load a variant specification to create new variant part, structures, or update an existing variant part structure based on the updated variant specification.
The input data is provided in a spreadsheet specifying all the information required for creating variant specifications and variants, such as the configurable part and option set information, characteristics of part and rule configuration specification, and a set of initial choice selections for the Option Filter.
Alternatively, you can load variant specifications by calling an out-of-the-box API. For more information, see
Loading Variant Specifications Using an API.
Loading Appropriate Information for Different Types of Variant Specifications
As the loader supports default values for different types of variant specifications, ensure that the information to be loaded conforms as described for each type:
• Variant Specification managed in the context of a configurable module:
◦ 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.
◦ May not have an option set since it is indirectly related through the configurable module.
◦ Requires a part configuration specification. This column can be blank, however it defaults to the latest without consideration for the lifecycle state.
◦ Has an indicator whether the configuration specification is applied to the top level. The Apply to Top Level column must either have true or false value, but cannot be blank.
◦ As variant generation is supported, the Create Variants column can have true or false value, or can be blank (treated as false).
◦ Has the ability to refer to options and choices by Number or Name.
◦ Requires configuration specification for the Option Filter. This column can be blank, however it defaults to the latest configuration specification without consideration for the lifecycle state.
• Variant Specification that is associated with an option set:
◦ Requires Name and Location for creating and Number for updating the variant specification.
◦ Requires an option set version.
◦ May not have a configurable module since it is indirectly related through the assigned option set.
◦ As variant generation is not supported, the Create Variants column can have the false value or can be blank (treated as false), but cannot have the true value.
◦ Has an indicator whether the configuration specification is applied to the top level. The Apply to Top Level column must either have true or false value, but cannot be blank.
◦ Has a part configuration specification. This column can be blank, however it defaults to the latest without consideration for the lifecycle state.
◦ Has the ability to refer to options and choices by Number or Name.
◦ Requires configuration specification for the Option Filter. This column can be blank, however it defaults to the latest configuration specification without consideration for the lifecycle state.
• Managed Option Filter:
◦ Requires Name and Location for creating and Number for updating the variant specification.
◦ Requires an option set version.
◦ Does not have part information for the configurable module. May not have a configurable module since it is indirectly related through the assigned option set.
◦ As variant generation is not supported, the Create Variants column can have the false value or can be blank (treated as false), but cannot have the true value.
◦ As a part configuration specification is not supported, the Apply to Top Level column must be blank. Unlike other variant specifications, no default is implied)
◦ Has the ability to refer to options and choices by Number or Name.
◦ Requires configuration specification for the Option Filter. This column can be blank, however, it defaults to the latest configuration specification without consideration for the lifecycle state.
