Additional published file types naming convention

[mbakke]

Have the ability to add more than a static prefix or suffix to the additional published file types. Revision or Version would be most beneficial in our case but even other attributes would be nice. The number and the extension should already make it unique.

[jcremillieux]

Besides, publish rule xml fails to upload if "output-prefix" element is not added in publish rules XML for Additional File Types generation. I don't understand this requirement because the file type is already specified by the extension. In this case, the prefix is useless.

Example : dwg_cuk__533u2926_drw.dwg. The prefix "dwg_" is useless because we know the file type with the extension ".dwg". The file name should be : cuk__533u2926_drw.dwg.

It should be also better if we can add the revision or version in the file name : cuk__533u2926_drw_A5.dwg

[TomU]

I completely agree!  I went round and round with PTC to try to find a workaround or customization.  It went nowhere.  I finally paid a 3rd party solutions provider to create a customization for us.  Now all additional files have their file extension stripped off and the revision letter appended (at download).  Much, much nicer!

[mbakke]

Tom,

If you're willing to share, which 3rd party did you use?

Thanks!

[TomU]

Wincom Consulting in Spain.  The above picture is from their Flexible Light Search product.

[mbakke]

Here is a solution I stumbled upon if anyone is interested. Now if it were just a little more configurable without knowing Java.

https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS216668