I’m not 100% sure, but I was under the impression that the new program rules feature would replace the validation rules in Tracker (event and tracker capture).
I see they are still both there, also in trunk, but I would guess program rules are both more powerful and better supported, and should be a good match for this use case.
Hi there. We have designed an inpatient discharge event capture program
modeled on the “Inpatient morbidity and mortality” program on the demo site.
We have defined a validation rule that the discharge date should be greater than the Admission date <= Discharge date.
When ever we attempt to register an event, the rule immediately fires (even though both values are NULL at this point). This does not seem like desired behavior.
This does not seem to happen on the demo. I am not sure if this is a difference in version (2.21 versus 2.22) or a difference in the operator (< in the demo or <= on our rule).
If I am understanding you correctly, the plan is to completely deprecate the validation rules in favor of program rules for tracker/events?
Regards,
Jason
···
On Fri, Apr 8, 2016 at 1:24 AM, Ola Hodne Titlestad olatitle@gmail.com wrote:
Hi Jason,
I’m not 100% sure, but I was under the impression that the new program rules feature would replace the validation rules in Tracker (event and tracker capture).
I see they are still both there, also in trunk, but I would guess program rules are both more powerful and better supported, and should be a good match for this use case.
Hi there. We have designed an inpatient discharge event capture program
modeled on the “Inpatient morbidity and mortality” program on the demo site.
We have defined a validation rule that the discharge date should be greater than the Admission date <= Discharge date.
When ever we attempt to register an event, the rule immediately fires (even though both values are NULL at this point). This does not seem like desired behavior.
This does not seem to happen on the demo. I am not sure if this is a difference in version (2.21 versus 2.22) or a difference in the operator (< in the demo or <= on our rule).