The method (or, by your words, "hack") you describe is how I do it, i.e.
1. The Save button does a straightforward submit.
2. WebQuerySave agent validates the submitted form.
3. If validation fails, the document is saved with the relevant error messages and a different form. The user is then re-directed to edit this document, which displays all their data and the error messages.
4. If the document validates OK, it's saved with the appropriate form.
A scheduled agent mops up the 'error' documents.
If the user has JS enabled, they get client-side validation (yes, that's duplication - but for their benefit).
Like everyone said earlier in this thread, if Domino gave you access to the session, you wouldn't have to do this.
Oh and it's possible to write the validation so the JS shares error messages with the server-side validation.
@Bernie
Accessibility means accessible by anything and anybody: could be someone using a screen reader, someone using a mobile phone or a search engine. That's not "someone using a search engine" but a search engine robot.
Jake,
The method (or, by your words, "hack") you describe is how I do it, i.e.
1. The Save button does a straightforward submit.
2. WebQuerySave agent validates the submitted form.
3. If validation fails, the document is saved with the relevant error messages and a different form. The user is then re-directed to edit this document, which displays all their data and the error messages.
4. If the document validates OK, it's saved with the appropriate form.
A scheduled agent mops up the 'error' documents.
If the user has JS enabled, they get client-side validation (yes, that's duplication - but for their benefit).
Like everyone said earlier in this thread, if Domino gave you access to the session, you wouldn't have to do this.
Oh and it's possible to write the validation so the JS shares error messages with the server-side validation.
@Bernie
Accessibility means accessible by anything and anybody: could be someone using a screen reader, someone using a mobile phone or a search engine. That's not "someone using a search engine" but a search engine robot.