by John Brinkman
To put the flexibility back in the hands of the form author, XFA 3.0 has a new configuration setting to control how errors are handled:
Don’t worry about remembering the syntax or where it goes — Designer will have a UI for setting this option.
The impact of this setting is pretty self-explanatory — but I’ll explain anyway:
noMessages – Acrobat/Reader will not emit any messages for invalid fields. It will be up to the form author to notify the user in some way — likely by changing the appearance of the invalid fields.
firstMessageOnly – When there are multiple errors on the form, Acrobat/Reader will display a message box for the first error and will suppress messages for all subsequent errors. This prevents the user from being inundated with a long series of messages — one from each invalid field.
allMessagesIndividually — (default) This corresponds to today’s behaviour. Well, not quite. There are instances today where we combine messages — for example messages for missing mandatory fields. But combined messages don’t happen as much as you might like.
allMessagesTogether — Aggregate all the messages from all invalid fields and emit a single dialog with all messages combined.