About Dependency Processing
Dependency processing refers to the tracing of object-to-object relationships among the objects considered for inclusion in the configuration you specify for any of the various PDM actions. A key distinction is made between part-centric and document-centric dependency processing.
Part-centric processing traces a product structure for dependencies while document-centric processing traces a CAD document model structure. Either method can be selected, regardless of whether the initially selected object is a part or a CAD document, as long as there is an active association between the part and CAD document.
For example, for part-centric processing of an initially selected CAD document:
The CAD document remains in the object list
The associated part object is included in the object list
The associated part becomes the "root" object for:
Setting configuration (latest, managed baseline names, view, effectivity)
Collecting dependents (all, none)
For example, if:
configuration = managed baseline
dependents = all
Then only the part dependents that are also part of the managed baseline are included in the object list.
The possible related objects to be included (CAD documents, documents):
CAD documents are the version (revision/iteration) that is peer to the gathered part version.
If a managed baseline for parts is selected, the CAD documents do not need to be part of the baseline.
When a workspace specification has dependency processing set to part centric, a CAD document is considered out-of-date if the version in the workspace does not have an active associate link to the part version included in the specified baseline for parts.
Was this helpful?