Meaningful / speaking file names for the documentation

DanielKremers · ‎Jun 23, 2020

Meaningful / speaking file names should be used for the documentation.

Current situation (example): 5C0593F1C8D041FF8378FA830B724AE0.pdf ((11.1 M020) Windchill Software Matrices)

Recommended: Windchill_Software_Matrices_11.1_M020_2020-04-09.pdf

So it is possible to store this documents hierarchical in the personal file-system (and find them again).

TomU · ‎Jun 23, 2020

I was just noticing the same thing yesterday. Very annoying to download all the documentation for a particular product and than have to manually go back through and rename all of it! I wonder if this would get more notice from PTC under the PTC eSupport Help Ideas section of the community...

PeterCase · ‎Jul 02, 2020

Hi @DanielKremers ,

We appreciate you letting us know about this issue. It was in fact something we resolved a while back, but which recently regressed due to a change on our web platform. I've added a change request to our next development cycle to investigate and address this, so you can expect normal behavior on refdoc downloads to return in the August timeframe.

Peter.

DanielKremers · ‎Jul 29, 2020

@PeterCase

THX Peter! Good to hear! And good to see that you are still at PTC 😉

Regards Daniel

PeterCase · ‎Sep 04, 2020

Hi @DanielKremers and @TomU. We pushed the change to address the problem in last week's web release. The fix is in production. "Save As" will now propose the original PDF filename.

Thanks again for reaching out to us about this.

Best regards,

Peter.

TomU · ‎Sep 04, 2020

Thank you!!!