cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

The PTC Community email address has changed to community-mailer@ptc.com. Learn more.

Combine Document Tables on WTPart Related Objects Tab

Combine Document Tables on WTPart Related Objects Tab

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.

  • WTDocument relationships are managed from the WTPart and require checking out the WTPart
  • EPMDocument relationships are managed from the EPMDocument, even though you have to checkout the WTPart to edit them
  • There is nothing to indicate if a build rule has been built or not.
  • The Association Types are unclear and confusing. An Image association does not pass a representation

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

5 Comments
slapha
15-Moonstone

Agreed.  Separate tables lose people all the time, and when they are on separate tabs it just makes it more difficult to find all the related information.

In our case a lot of people aren't as concerned with the data on the WTPart itself, they want the drawing, parts list, related documentation, etc.

The only concern I have is everyone being able to really determine what the associations are. We've had trouble with the terminology around "Built/Build", though we've had about the same amount of trouble with the term "Described by". "Reference" people understand well enough I think. "Content" is a little hazy to some.

LewisLawrence
11-Garnet

I understand your concerns, I am sure many people have spent a lot time explaining the difference between describes and references. I think that if the documents were all in one table and the "link" between the WTPart and the Document clearly showed its properties and the corresponding icon (master or version) this would actually help clear up a lot of confusion. If you could mouseover the link and get some verbage on what it does with a link to the relevant help document that could only help with understanding things.

LewisLawrence
11-Garnet

There is another Idea in this area, thought it would be worth adding a link here to help navigation.

https://community.ptc.com/t5/Windchill-Ideas/Changes-to-WTPart-Associations-Owner-Contributing-Image/idi-p/456428#comment-24668

 

Pekholm
10-Marble

Up to Windchill 9 you could see all documents in one table, which was clear for anyone. It´s only confusing to split up described by and referenced by documents in separate tables as from Windchill 10.

olivierlp
Community Manager
Status changed to: Archived

Hello,

We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.

You can always post a new idea with all the details required in the form.

Thank you for your participation.