Collection Configuration
Most PDM actions involve collecting groups of objects for you to act upon. Typically, you initially select one or more key objects and then gather a larger set of dependent objects that you want to include in the action, based on their relationship to the initially selected object. The system chooses a default group of objects that you can then modify to suit your intended task. The particular set of object types and iterations you gather is the configuration applicable for the action.
The configuration controls need to be accessed whenever you want to change the configuration rule for collecting objects. A configuration may be identified for each object selected for a particular action.
When specifying a configuration, you first identify whether the configuration is based on an enterprise part, end object, product, or serial numbered part (a Product Structure, specifying part-centric processing), or on a CAD document (a Model Structure, specifying document-centric processing). This choice determines the set of configuration options (latest, managed baselines; as stored configurations; per workspace configuration specification; or based on part effectivity) available for selection, as follows:
• For Model Structure -- Latest, as stored configurations, promotion requests, per workspace configuration, and managed baselines that include the iteration of the single initially selected CAD documents or the CAD documents actively associated to the initially selected parts in the object list.
• For Product Structure -- Latest, per effective date, managed baselines, per workspace configuration, and promotion requests that include the iteration of the initially selected parts or the parts actively associated to the initially selected CAD documents in the object list.
If the initially selected object has an active association to a peer object (for example, a CAD document has an active association to a part, or vice versa) you can collect iterations of dependents based on a configuration specification for the peer object.
You may change the rule for collecting dependents.
You may change the configuration of the objects to be collected.
If the action is initiated from a workspace, or results in objects being added to a workspace, configuration changes may be written to the workspace configuration specification (when the configuration is committed).
When you commit the selections you make in the configuration tool, your changes are applied to the object list.
|
|
Configuration changes have effects if you have already collected related drawings, parts, CAD documents, or instances, or edited the list in any other way (for example, using exclude). Upon changing a configuration, the collected objects that are related to the new configuration remain in the list. However, if the property.core.collection.collectall is set to false in wt.properties, all of the collected related objects are removed from the list upon changing the configuration.
|
Changes to configuration settings never remove initially selected objects from the object list.
Changes to configuration settings can change the iterations of dependent objects added to the action list; configuration settings never change the iteration of initially selected objects in the object list.
For the Update action, the iteration of the initially selected object is the up-to-date iteration, not the iteration that was initially selected. When using effectivity for Product Structures, the iteration of the initially selected objects is the effective one per the date specified, which may be different from the iteration that was initially selected.
