Sounds good to me as well and think it will be very useful.
Another feature we should probably think about as well, is extending this
type of thing to indicators. We have forms where we need these validation
rules, but also it would be neat to have indicators be also able to be
defined by the patt
>
> I also like the simpler option better (surprise).
>
WITYWS.
> If the default option clearly states that there is no change then we are
> not forcing the users who do not need this feature to even understand it.
>
Good. I think this will be a neat feature. The only challenges will be the
use
Hi Jim,
I also like the simpler option better (surprise). If the default option
clearly states that there is no change then we are not forcing the users
who do not need this feature to even understand it.
regards,
Lars
On Fri, May 23, 2014 at 11:05 PM, Jim Grace wrote:
> I'm liking the sim
I'm liking the simpler option of just adding one dropdown with category
combinations, called something like "Repeat validation rule using". The
default dropdown selection could be something like "[ Use validation rule
as is ]" or "[ Don't repeat rule ]". The following choices are the option
combos:
Hi Jason,
Here's my idea: Add one extra field to ValidationRule, a reference to
DataElementCategoryCombo. If this is null, it means no change from the
current validation rule. If it's not null, it means that the validation
rule should be applied to all option combos within the category combo, for
Hi Jim
Yes, I think I agree with you, but a still a bit fuzzy how it could happen
with the current UI. I think the user would have an option like "Apply
this rule to common category combo options", and they would then select a
left side, and the right side would only show data elements with the sa
I like it. A couple of ideas:
- I suggest that this be a new property of validation rules, rather than a
third type in addition to "Validation" and "Surveillance". It could be
potentially useful for either of these two rule types.
- When selecting this option, the user could choose from a list of
Hi Lars,
Finally got around to creating the blueprint here
https://blueprints.launchpad.net/dhis2/+spec/atomic-validation-rules
Regards,
Jason
On Wed, Jan 15, 2014 at 6:36 PM, Lars Helge Øverland wrote:
> Hi Jason,
>
> yes I think this makes sense. One could make a special kind of validation
Hi Jason,
yes I think this makes sense. One could make a special kind of validation
rule, with a constraint that all data elements on the left and right side
expressions share the same category combination, and then tell the system
to validate each and every category option combination. Feel free
Hi Devs,
I came up against an issue today when looking at implementing a legacy
database in DHIS2. In the old system, there are about 75 rules. The rules
in the past have been applied at the atomic level, meaning that each and
every data element category combination value is compared with a counter
10 matches
Mail list logo
