cancel
Showing results for 
Search instead for 
Did you mean: 

Authoring Client Field Validation/Restriction?

scottf
Champ on-the-rise
Champ on-the-rise
Hi,
Is there anyway to validate and restrict what can be entered in certain fields in the web client?
I am using labs3c including WCM and would like to be able to add some restrictions to the 'create web content' wizard.

For example, in the first screen of the 'create web content' wizard I would like to restrict the user to entering only lowercase letters of the alphabet.
Is this possible without having to get the source from SVN and building locally? and without having to write webscripts etc? is this configurable in a properites or xml file somewhere?

I know how to restrict and validate fields on my web forms no problem but it is the wizard I am stumped on.

Any ideas?
3 REPLIES 3

scottf
Champ on-the-rise
Champ on-the-rise
Anyone here?

tommorris
Champ in-the-making
Champ in-the-making
Hi there,

I think the value that you're talking about is (often) destined to become the name of the XMl node (cm:name).
The ultimate decision as to what the node is called is deterimed through the output path expression.
This expression is a freemarker expression, and so you could have something like:

/${webapp}/mypath/${name?lower_case}.xml

It doesn't prevent the user from entering uppercase characters, but it does ignore them.

Tom
http://www.ixxus.com

scottf
Champ on-the-rise
Champ on-the-rise
Thanks for the reply Tom, and yes you are correct in what I am referring to.

Your idea is interesting, however it is not sufficient as I really wanted to restrict the user from entering uppercase characters for example in the first place, not ignore them after the fact.

Hopefully an alfresco engineer may be browsing these forums and can answer this question Smiley Happy

Thanks again.



Hi there,

I think the value that you're talking about is (often) destined to become the name of the XMl node (cm:name).
The ultimate decision as to what the node is called is deterimed through the output path expression.
This expression is a freemarker expression, and so you could have something like:

/${webapp}/mypath/${name?lower_case}.xml

It doesn't prevent the user from entering uppercase characters, but it does ignore them.

Tom
http://www.ixxus.com