Understanding propagated attributes

The following table demonstrates attribute propagation. In this example, the user, while in Classification Admin, specifies the Test Assembly 1 class as an assembly class. Furthermore, in the assembly class, Attributes 1–5 have the Propagated Property option selected.

Note

For specific cases that include attributes at the upper levels of a structure that need to be propagated downward, see About reverse attribute propagation.

When Teamcenter propagates attributes, it begins at the propagation start point (PSP), and then travels upward through the parent levels looking for attributes to propagate. In the example, the first component it looks at is Component 4. The component contains Attribute 4, which is a propagated attribute, so Teamcenter propagates Attribute 4 to the resource assembly, Test Assembly 1. Teamcenter then looks at the parent of Component 4, which is Component 3, and finds two attributes to propagate. It then looks at the parent of Component 3, which is Component 1, and finds Attribute 2 to propagate. Component 1 also contains Attribute 1, but this value has already been populated by Component 3. When Teamcenter is finished with propagating attributes, the top-level resource assembly, Test Assembly 1, shows the following attribute values:

Attribute	Propagated from
Attribute 1	Component 3
Attribute 2	Component 1
Attribute 3	Component 3
Attribute 4	Component 4

Attribute 5 contains no value. Although there is a value assigned to this attribute in Component 2, Component 2 does not lie within the propagation path as it is not a parent or grandparent of Component 4, the PSP. Similarly, Components 6 and 7 do not lie within the propagation path.

A gray PSP indicates that this PSP is defined in the context of a subassembly. It is not taken into consideration in the current tool assembly. Subassemblies are highlighted with a colored background in Resource Manager.