Modifying Family Table Attributes in Windchill
The attributes of generic or instance Creo Parametric Family Table members can be added or modified using the Edit Attributes page. However, because of their interdependency, additional members of the Family Table may need to be checked out in addition to any whose attributes you want to modify.
The following information is provided to review the classification of Family Table attributes, and describes the requirements for, and results of, attribute modification.
There are three classifications of attributes for Family Table objects, as described in the following table.
|
Attribute Class
|
Description
|
|
Generic-driven
|
An attribute (parameter) that has been designated in the generic model, but not added as a column to the Family Table. All instances reflect the same value as the generic for this attribute.
|
|
Inherited Table-driven
|
An attribute (parameter) that has been designated in the generic and has been added as a column to the Family Table, without assigning a unique value to the instance. The Family Table editor in Creo Parametric displays an asterisk (*) for the value for the instances. In Windchill, the value displayed for the instance is the same as is displayed for the generic.
|
|
Independent Table-driven
|
An attribute (parameter) that has been added to the Family Table and a unique value has been given to the attribute either via the Family Table editor or the WindchillEdit Attributes page.
|
When adding or modifying the value of generic-driven attributes, all Family Table members must be checked-out. If your initial selection of objects did not include all members, upon clicking OK on the Edit Attributes page, the Confirm window opens, listing the additional instances that need to be checked out. Clicking OK checks out the additional instances to allow the Family Table to be modified. Clicking Cancel returns you to the Edit Attributes page without modifying the Family Table.
When you modify an inherited table-driven attribute at the instance level, it becomes independent. That is, its value is no longer driven by the value of the generic. Therefore, only an instance whose value is being modified requires a checkout.
Modifying an independent table-driven attribute requires only that the instance is checked-out.