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

Add the Description to the WTPart

Add the Description to the WTPart

I have never seen an ERP system that does not have a description for a component part. I cannot therefore understand why the WTPart does not have one as well. EPMDocuments have an out of the box description, as do many other objects in the system, but WTParts do not. If you are using associations between CAD and Parts, there is then no way to transfer the description to the WTPart. Work arounds like creating an IBA on both object types and linking them instead creates a giant mess because all the table views now show the OOTB description, not your new one. If you attempt to change the table views you find that there are always other objects types that still have an OOTB description, so you either have to display both, or not show some data.  There are also some places where you cannot edit the view to choose.

2 Comments
JørnAHansen
Guest

‌I'm curious: By "description" do you mean you want a multiline description field or just a single line description suitable for display in a Bill of Material? We use the Name field on WTParts for that.

In our current Windchill setup we have the name/textual description in an IBA for CAD objects and it maps to Name field on WTParts. It works great UI wise for our WTParts and with the problems you mention for our CAD objects where we currently have name=number mapped across Creo and Windchill.

cmilligan
Visitor

The Name appears to be designed for a short title/noun/description that states what the item is. The description needs to contain the full definition of the item and therefore must be longer. The Name is limited to 60 characters if I recall correctly which prevented us from using it as the description. I think that is fine too, as there needs to be a short descriptor for things like balloon callouts or customer BOMs, and a longer one for more information. We have drawing descriptions that regularly pass over 160 characters, and WTPart descriptions that might exceed 300 characters. We basically use it as a text based classification system, and intend WC classification to generate it someday.