HYPERLINK "http://www.steris.com/" \n Robert M. Priest, PE, PMP Lead Engineer / PLM Program Manager Phone: +1 440 392 7740 Email: HYPERLINK "mailto:-"- --- You are currently subscribed to solutions. To unsubscribe send a blank e-mail to -. For assistance, email us at - or find other contacts at www.ptcuser.org/org/contacts.html. PTC/USER and the PTC/USER logo are registered trademarks of PTC/USER, Inc. Pro/ENGINEER is a registered trademark of PTC. Message authors are solely responsible for the content of their posts.
-- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.17.19/663 - Release Date: 01/02/2007 14:28
-- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.17.19/663 - Release Date: 01/02/2007 14:28
I was able to test this. It works for "Associate Document" from the details page. The user is prompted first what to choose. However, the documentation tab in PIM does not ask and they are all describe by links. My team will have to consider the impact of this functionality. The problem I have is what it implies. We use related documents to indicate that a part or assembly should adhere to some spec or requirement document. It could be an industry spec like J-STD-001 or MilSpec. With describe by links, it is clear that this version of the part adheres to this version of the document. However, a reference link would imply that it should adhere to any and all future versions of that document. On the one hand, you are ensuring that any change to the spec is reviewed and design changes are made. On the other hand, you have to potentially revise the part with each document revision.