All implementations of Windchill that use WTParts and EPMDocuments will also use WTDocuments, there is a lot of inconsistency in the product here and much confusion for users. "But its a document too, why is it different?". Some more specific examples.
My suggestion is to combine all the document object relationships into a single table, with a common toolset for managing the relationships to WTParts. This would include some new and clear functionality around what the various build rules do, as well as the ability to pass additional information from WTDocuments. The attached screenshot mock up hopefully illustrates the kind of thing I am imagining.
This idea relies on some other product ideas I had submitted previously:
Referenced By link between WTPart and CAD Document
Pass representations to WTParts from describing WTDocuments
Association toolset to provide individual controls over build behaviour and a preview
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.