Variant Part Step: Generating a Variant
The final step of the part configuration process allows you to generate a module variant or a product variant. In this step you can reuse, update, or revise an existing matching variant part found by the system, or create a new variant part.
* 
Alternatively, you can request to generate a variant from the information page of a variant specification by choosing Request Deliverables from the Actions menu.
1. Review the Module Variants table for existing variants that may be appropriate to reuse, update or revise. If a variant is appropriate, select one of these actions on the variant part:
Use Selected Module Variant—Available for matching variants; select this option to reuse that variant part and associate it to the variant specification.
Update Selected Module Variant—Available for variants checked out to you; select this option to regenerate the variant part and associate it to the variant specification.
Revise Selected Module Variant—Available for checked in variants; select this option to revise the selected variant, generate the variant part and associate it to the variant specification.
* 
Revise Selected Module Variant is not available when the property wt.generic.variantLinkBehaviorOnRevise is set to nocopy. The preference Allow revise of non-latest revisions determines the revisions available for revision.
When none of the existing variants are appropriate, select the following action to generate a new variant.
Create New Module Variant—Create a module variant if the variant specification does not have an associated variant part or the associated variants are not appropriate.
2. To complete the configuration process, click Finish.
* 
To learn how to carry over custom modeled attributes defined for the configurable module to the variant generated from it, see documentation on Windchill customization.
Controlling the Ability to Create Variant Parts
The Variant Requestor set to Generic User preference allows an administrator to control who can create deliverables (variant parts) for a selected structure. If the preference is set to yes, then the creator of the variant part is determined by the value of the com.ptc.dto.delivery.guy property located in codebase\com\ptc\wpcfg\wpcfg.properties file. If the preference is set to no, then the current user who requested the deliverables is the variant part creator.
Enabling Email Notification
You can enable email notification to the user who requested a deliverable when the deliverable is successfully generated. To do this, log in as a site administrator, add the property com.ptc.dto.deliverables.email.notification.enabled to the wpcfg.properties file, and set it to “true”.
Isto foi útil?