I am looking for the best way to validate fields before a save, i could care less about what they are before i save, like in partial refreshes messing up because a field is empty.
I discovered that simple action groups are conditional, that gave me the thought to use them to validate the form before a save, not only could i validate whether 
Is there a better way to do this? I know you could do it client side, but then how do you stop your serverside script from running?
3 comments:
You might want to read this on validation: http://www-10.lotus.com/ldd/ddwiki.nsf/dx/server-side-versus-client-side-validation-on-an-xpage.htm
The thing for you to note is switching off Client side validation.
Then if I am understanding your question correctly you are looking at using the "validation" options at field level. Look for section "validation" within each control (field etc).
This covers basic validation and you use in tandem with the error message controls (and occurs serverside but before save - when client side is switched off).
For more advanced validation, like looking up values in a table then you would add you own "custom validator" - under "All Properties" - "validators".
For an example download the xpages wiki from openntf.org - look at custom control "prtContent" and field "subject".
If the client side script returns 'false' then the server side script will not run. This allows for client side logic to be evaluated before the server-side script runs.
Thanks for the comments, one of the problems with your suggestion Steve is that type ahead fields try to validate after every keystoke, so it makes it impossible.
Post a Comment