I am wondering what everyone is doing for associating WTParts to WTDocuments...
For example, I am specifically interested in the following use case:
We have a set of WTDocuments that are engineering specifications. They cover internal standards for painting, plating, etc... Each one of those WTDocs could potentially be associated to hundreds or thousands of WTParts. Which seems like it will quickly get clunky and hard to manage...
Questions I have:
- Do you currently make associations in the above case?
- If so, what permissions are you giving users to be able to associate WTParts to the WTDocument? The document is at released and we don't want everybody making changes to it...
- Okay, I did some testing with my regular user account and was able to associate the WTPart to the WTDocument at Release. So this may not be an issue.
- Do you have an alternate practice instead of associations?
System is Windchill 10.1 m040
-marc
TriMark Corporation
CAD / PLM Systems Manager