Creating Multiple New Parts
A part in Windchill is a logical database representation of a physical item used to build a product. Physical components can include packaging, product manuals, and software as well as electronic and mechanical components. For more information about parts and their role in configuration management, see Parts and Part Versions.
Multiple new parts can be created in a folder browser or created and inserted into a product structure in a single operation. Use the following procedure to create multiple parts in a single operation:
 |
If your site has security labels enabled, you may see the Set Security Labels step. For more information about setting security labels, see Setting Security Labels while Creating an Object.
|
Creating Multiple Parts in a Folder
1. Select > in the Actions menu at the top of the Folder Contents table.
2. In the Define Part step, select the part Type from the drop-down list. The window is refreshed to display attributes that are unique to the part type.
|
|
For descriptions of part attributes, see Part Attributes.
|
3. Provide values for the displayed attributes. Click Next to continue.
|
|
You must choose to create all parts as either end items or regular parts due to differences in attributes such as number.
|
4. The table in the Set Identity Attributes step provides the ability to specify how many new parts will be created and enter attribute information. The icons at the top of this table provides the following additional actions:
|
Action
|
Description
|
|---|---|
 Add Row |
Adds a single blank part creation row to the bottom of the table.
|
 Add 5 Rows |
Adds 5 blank part creation rows to the bottom of the table.
|
 Remove Selected Row |
Removes the selected part creation row from the table.
|
 Edit Attribute Value |
Edits the attributes of a group of selected rows in the table. The changes apply to all selected parts.
For more information on setting cascading attribute values from the Edit Attribute Value window, see the “Setting Cascading Attribute Values” section in the topic.
|
 Set Classification Attributes |
Click this icon to classify the newly created parts using the Set Classification window. All parts receive the same classification.
This action is only available if Windchill Classification is installed. For more information, see Working With Classification Administration.
|
5. Click Finish to create all the parts in the table. The Folder Contents table is refreshed to show the new parts.
|
|
If you have omitted the values for any of the following attributes, an error message is displayed to inform you that valid information is missing for one or more required attributes:
• Modeled attributes with Required set as true. These attributes are indicated with an asterisk (*).
• Attributes with the Required constraint rule enabled. These attributes are indicated with an asterisk (*).
• Driven attributes with the Is Required constraint defined in the cascading attribute rules for the selected driver attribute values. However, the required driven attributes are not indicated with an asterisk (*).
|
Create and Insert Multiple Parts in a Product Structure
It is possible to create multiple new parts and insert them as children of another parent part from the Structure tab on a part information page. Select the parent part and then select 
Insert Multiple New from the Insert New menu in the Editing group on the Structure toolbar or > in the right mouse button menu. You can also click the “Insert multiple new” icon in the toolbar on the Uses tab. The steps are the same as those described above for creating multiple parts in a folder.
Insert Multiple New from the Insert New menu in the Editing group on the Structure toolbar or > in the right mouse button menu. You can also click the “Insert multiple new” icon in the toolbar on the Uses tab. The steps are the same as those described above for creating multiple parts in a folder.| | The parent part under which the new parts are inserted must be checked out to define the usage relationship. The parent part remains checked out after the operation is complete. |
Setting Cascading Attribute Values
Consider an object type with cascading attribute rules defined for its driver attributes (list type) and driven attributes (list, radio button, and Boolean type).
When you select an object and a driver attribute in the “New Multiple <Objects>” window, then in the Edit Attribute Value window, the To field displays all available values for the editable driven attribute that is selected in the Set list.
Consider that you have selected a subset of objects and their driver attributes in the “New Multiple <Objects>” window with cascading rules defined for the driver and driven attributes.
Subsequently, in the Edit Attribute Value window, when you select an editable driven attribute in the Set list, the To field displays values based on the following conditions:
• If a driven attribute is defined as “hidden” for one of the selected driver attributes, then the To field displays only the values for the selected driven attribute that are common to all the editable driven attributes.
• If the editable driven attributes do not have common values between them, the To field is displayed as empty for the selected driven attribute. A message is displayed informing you that the selected objects do not have the values available that are valid for all of them.
• If a driven attribute is hidden for all the selected driver attributes, the To field is displayed as empty for the selected driven attribute.
| | The To field displays values for a selected driven attribute appearing only in the first row in the “New Multiple <Objects>” window when you: • Select a first-row object along with an object from any other row. • Define a driven attribute as “hidden” for the driver attribute selected in the other row. |
• A Boolean attribute has three states, Undefined, Yes, or No. If you have a “Boolean driven attribute” that is defined with the Is Required constraint for any one of the selected driver attribute values, the “Undefined” state does not appear in the common values that are displayed in the To field for any “Boolean driven attribute” selected in the Set list.
Only when the Is Required constraint is not defined for any of the “Boolean driven attributes”, the “Undefined” state appears in the common values that are displayed in the To field for any “Boolean driven attribute” selected in the Set list.
The “Yes” or “No” values appear in the To list depending on the cascading rules.
You can also set a default value for the driven attribute instances using the Set Default button available in the Edit Attribute Value window. A default value defined for a driven attribute always appears in the To list that displays the values common to the editable driven attributes. The Set Default action is disabled when a default value is:
• Not defined for any of the driven attribute instances.
• Defined for one or more driven attribute instances, but that default does not appear in the common values that are displayed in the To list.
• Defined for the same driven attribute in more than one instance, but the default is not identical.
The Set Default action is enabled when the following three conditions are satisfied:
• A default value is defined for any one of the editable driven attribute instances.
• The default value is identical across all the editable driven attribute instances, which have a default value.
• The default value defined for all instances of an editable driven attribute appears in the common values that are displayed in the To field.
When you select a valid driven attribute value and click Apply or OK, the value is applied to the selected objects depending on the cascading attribute rules.
| | • Click Apply to set the value and keep the Edit Attribute Value window open. • Click OK to exit the Edit Attribute Value window and return to the “New Multiple <Objects>” window where the newly set value is displayed. |