Requesting a PTC Enhancement: Effectivity Propagation Preference to allow multiple states.
Summary: Submit PTC Enhancement to Effectivity Propagation Preference to allow multiple states.
Gap: Please submit an Enhancement Request to PTC, requesting that the Effectivity Propagation preference settings allow effectivity propagation to multiple lifecycle states, instead of just the one lifecycle state that is allowed now.
Background: For a Windchill implementation, where WT Part structures utilize “Released” for Client-created parts, but use the “Vendor Released” state for common-standard parts in the Library, we could only specify one lifecycle state in the effectivity propagation preference. But we apply effectivity to both Released and Vendor Released WT Parts in the part structure, to ensure retention of the part structure usage information (e.g., Find Numbers, quantities) when an Effectivity configuration filter is used. If both Released and Vendor Released States could be specified in the Effectivity Propagation Preference, this would allow propagation to all the parts in the released structure.
Consequences if Not Implemented: If multiple States (at least 2) for the effectivity propagation preference is not provided, there will still be manual activity required to collect all the "Released" state objects in the structure, add them to the Change Task (CT) Resulting Objects, and apply Planned Effectivity applied to those WT Parts, so that effectivity will also be applied to them and propagation will occur to the Vendor Released state objects in their individual part structures.
User communities affected by this proposed change:
CM, or other users, when creating Change Notices (CN)/Change Tasks (CT) and adding WT Parts to the CT Resulting Objects and applying Planned Effectivity prior to release to enable effectivity application and propagation.
11 Comments
