Thanks Matt,
Your point regarding the multiple filename problem is understood.
We'll find a good solution given the tools we have to work with. The fun comes from trying to master such tools without blowing them up in the process. :)
Your advice is Much Appreciated!
W
Thank you for your reply, Matt.
I can appreciate the intent to have only the latest revision data set in the project tree. Only, It seems intuitive and logical for the vault to apply the same rule to access all revisions in the lifecycle... for instance, in this example showing lifecycle...
Greetings SolidWorks and PDMWorks Gurus,
In the Workgroup PDMWorks Vault, the project tree lists only the latest documents by default. If I would like to see an archived revision of a part, I can right click on the data set, call up the Document Information dialog, and pull down from Revision...
Thanks for the reply, Drawoh,
I do agree with you entirely with regard to the 'not changing fit, form or function concept'. This would solve many problems in our product lifecycle. Great concept to implement someday.
Most of our development designs consist of many configured, composite SW parts...
Or... Is it possible for SW to append the 'Revision' attribute to the 'filename' attribute only during check-out from PDMWorks, and then un-append during check-in. - as to not affect the way PDM handles predecessors and hierarchy. I have a need for the rev succeeding the SW filenames outside of...
Is it possible to append the SW 'Revision' attribute to the SW 'Filename' attribute? So, when you 'Bump the Rev' in the vault, the filename updates as well.
