How do I ban certain traits in the PDM?

Hello

I would like to prohibit the use of certain special characters in the naming of folders or documents, for the sake of uniformity. For example, our standard naming does not include the underscore, and recommends capitalizing everything.

However, some rebels persist in smearing my beautiful and tidy chest with their fanciful naming :grin:

Therefore, I am trying to legislate in a material way to block any desire for overflowing creativity!

Does anyone know if this option exists?

Hello

A condition can be set up on the state transition(s) to prohibit state change if a particular datamap variable/attribute has the special characters you want to banish.
Another way would be to write a script to run during a transition (or even archiving in the initial state) that removes the special characters and rewrites the values in uppercase.

Hello

Apart from providing them with a truncated and rigged keyboard, without special keys and with a forced capslock, " in a material way" this will not be possible. :upside_down_face:

1 Like

Yes, I had thought about that, I even started to put conditions everywhere, but it forces me to add in all the transitions concerned the new characters if I have to add more. That's why I'm looking for a more global method.
But that's clearly the path I'll follow if I can't find anything better

aaah I like that! Block their keys sneakily!! :grin:

Hello
Maybe a way to fiddle with dispatch scripts or settings related to file additions to exclude certain name formatting.
For dispatch unfortunately the string functions are quite limited so no possibility to my knowledge to check if the texts are capitalized or not.
On the other hand, monitoring all the special characters can be done.
After that, there are the macros integrated into SW which would allow you to intercept filenames and prohibit archiving in the process, but on the one hand you have to consider all possible cases (users are very inventive to do m...) and on the other hand you have to manage the update of the use cases following the renaming.
The last solution would be to make macros for PDM which would rename everything that is outside the framework of the naming " rules " when the files are archived so that the links between the different files are maintained.

1 Like