Open deepankar-sajwan opened 2 years ago
@deepankar-sajwan What is the purpose of these rules. I think different organizations use this functionality. So why does the organization is used these special characters in the name if they don't need them?
@deepankar-sajwan What is the purpose of these rules. I think different organizations use this functionality. So why does the organization is used these special characters in the name if they don't need them?
Hi @Shivam-Samant there are many companies around the world, that use different special character in their name. Since our clients are across the world, hence we need to allow special character in validation of client name. So that if we create, client with special character the system allows us to create client. But we have to decide what special characters are to be allowed, and how many times it can occur in client name. We cant allow client name like adoc@@@@@tech adobe### tech to be available as client name.
Is your feature request related to a problem? Please describe. Cuurently there is no validation for client name and project name. For instance client name can be @@ahsds##$$, simillarly project name can also be *%%6^&&ASAS**, hence these name look ambigous. Therefore a validation on naming covention for client name and project name is required.
Describe the solution you'd like Following are the some rules that can be applied for validation
Open for discussion related to validation rules
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
Additional context Add any other context or screenshots about the feature request here.