dabbling with ways to run validation rules, we might discuss where it is best to run the rules and show the error messages. One option could be to run the validations while the user types data, and show an error message next to the field with an error immediately after the value is entered. Another would be to run validations at a fixed time, for example when completing the event, and show a summary of errors. Any opinions on this? Perhaps we need both?
Markus
···
On Mon, Mar 16, 2015 at 8:36 AM, Prosper BT ptb3000@gmail.com wrote:
Dear Team,
Much as we ca set validation rules for single event without registration, we have not means of running them.
Also you provide for validation criteria which is based on attributes and yet we dont have attributes in single event without registration.
The request to have all validation rules at entry has been coming up alot since its not yet supported in DHIS2 especially in aggregate reporting.
I think it should be an option and turned on when you require to run validation rules at entry or by clicking on button after entry.
For Individual records it makes sense to run during entry as sometimes it little data entered and logics need to be emphasised alot.
With also the coming of Apps like TTC, they dont accommodate validation running and would be better if they can be implemented at entry but should never restrict continuing with data entry just warnings.
dabbling with ways to run validation rules, we might discuss where it is best to run the rules and show the error messages. One option could be to run the validations while the user types data, and show an error message next to the field with an error immediately after the value is entered. Another would be to run validations at a fixed time, for example when completing the event, and show a summary of errors. Any opinions on this? Perhaps we need both?
I like the idea of having an option to either validate during data entry, or once the record is completed - each program will have different requirements.
Regarding stopping the completion of an event: this should probably also be an option. In some cases a warning is enough, in others you don’t want the entry to proceed/ complete.
dabbling with ways to run validation rules, we might discuss where it is best to run the rules and show the error messages. One option could be to run the validations while the user types data, and show an error message next to the field with an error immediately after the value is entered. Another would be to run validations at a fixed time, for example when completing the event, and show a summary of errors. Any opinions on this? Perhaps we need both?