Uppercase/lowercase template and management

Hello,

Thank you for the suggestion. I would like a few clarifications so we're sure to implement it in a way that would work for you.

• When you say to make it available for templates, do you mean to have a way to enforce this for the templates, or to have the setting available in templates so that when users create an entry based on the template, it will use that setting? This is also related to the next question.
• The way you see it, is your goal to enforce it per entry type (for example, all RDPs should have X format, all folders Y format), or do you think there should be the possibility to have exceptions within the same entry type? If it's a setting configurable in the entry itself then it would also be possible for a user to change this setting if they already have the right to edit the entry.

Basically I would like to make sure I understand the 'scope' of the request and the level of granularity required to make this really useful for you.

Regards,

Hello,

When you say to make it available for templates, do you mean to have a way to enforce this for the templates, or to have the setting available in templates so that when users create an entry based on the template, it will use that setting? This is also related to the next question.

If someone use a template to create an entry, this entry should follow the defined setting for it's entry type.
Example: If I defined all RDP have to be lowercase, if someone use a template to create an RDP object, the name will be lowercase.

The way you see it, is your goal to enforce it per entry type (for example, all RDPs should have X format, all folders Y format), or do you think there should be the possibility to have exceptions within the same entry type? If it's a setting configurable in the entry itself then it would also be possible for a user to change this setting if they already have the right to edit the entry.

Yes, my goal is to enforce it per entry type. No need for exceptions, I think it could be too complicated to develop and manage.
But people shouldn't modify it even with read/right on the object or it will be useless, so maybe this request is more for DVLS side than RDM?
As an example: it's possible to give read/write on something without the rights to modify permissions, that's the same idea.


Here is a usecase:
We (DVLS admins) maintain the directory and the structure for our company (MSP) and create directories/subdirectories for our customers following our naming convention that isn't all uppercase or all lowercase but that's not an issue because we know what we do.
In these subdirectories, users can create the objects they need (RDP, SSH etc). Some prefer lowercase, some prefer uppercase, some mix everything.. So we would like to enforce lowercase on it.

I hope I've explained it better this time, let me know if you need more informations.

Best regards

Hello,

Thank you for the information, I think this answers the questions I had about how it should work in RDM. I have opened a ticket. If we have any additional questions or an update on the progress of the request, we will post back in this thread.

Regards,

Hi,
Any news on this request please ?

Hello,

Nothing new for now but I will raise the priority.

Regards,