I am using DHIS version 2.20 build revision 19691.
I am having a doubt in Program rules.
We have a case where
Data element ‘Age Type’ has options i.e. Hours/Days/Weeks/Months/Years
Now if the user is selecting ‘Age type’ as Hours then another data element ‘Age’ should accept value between 0 to 23, application should not accept any value more that 23 in case of Hours ‘Age type’.
Similarly, If ‘Age type’ is **Days **then it should not accept more that 6 for ‘Age’ data element.
This kind of cross validation rules is half way supported already, and the full support is right around the corner. The program rule can be created in the editor, it is being run - but how to display the error message in the UI is still under discussion. Keep an eye out in release notes 2.21!
To construct the cross validation you want you would have to make one rule for each of your options. For ex. one rule that validates that if ‘Hours’ is selected, age must be below 24, and another for ‘Days’.
Hi Neeraj.
This kind of cross validation rules is half way supported already, and the full support is right around the corner. The program rule can be created in the editor, it is being run - but how to display the error message in the UI is still under discussion. Keep an eye out in release notes 2.21!
To construct the cross validation you want you would have to make one rule for each of your options. For ex. one rule that validates that if ‘Hours’ is selected, age must be below 24, and another for ‘Days’.
I am using DHIS version 2.20 build revision 19691.
I am having a doubt in Program rules.
We have a case where
Data element ‘Age Type’ has options i.e. Hours/Days/Weeks/Months/Years
Now if the user is selecting ‘Age type’ as Hours then another data element ‘Age’ should accept value between 0 to 23, application should not accept any value more that 23 in case of Hours ‘Age type’.
Similarly, If ‘Age type’ is **Days **then it should not accept more that 6 for ‘Age’ data element.
Hi Neeraj.
This kind of cross validation rules is half way supported already, and the full support is right around the corner. The program rule can be created in the editor, it is being run - but how to display the error message in the UI is still under discussion. Keep an eye out in release notes 2.21!
To construct the cross validation you want you would have to make one rule for each of your options. For ex. one rule that validates that if ‘Hours’ is selected, age must be below 24, and another for ‘Days’.
I am using DHIS version 2.20 build revision 19691.
I am having a doubt in Program rules.
We have a case where
Data element ‘Age Type’ has options i.e. Hours/Days/Weeks/Months/Years
Now if the user is selecting ‘Age type’ as Hours then another data element ‘Age’ should accept value between 0 to 23, application should not accept any value more that 23 in case of Hours ‘Age type’.
Similarly, If ‘Age type’ is **Days **then it should not accept more that 6 for ‘Age’ data element.
When the expression is true, action taken is to show an error message. You can say that the expression is not defining a “valid range” - rather the opposite; it is defining what would be concidered invalid. So if you have selected ‘Hours’ as the type, and put a number higher than 23 - we should display the error message provided.
Hi Neeraj.
This kind of cross validation rules is half way supported already, and the full support is right around the corner. The program rule can be created in the editor, it is being run - but how to display the error message in the UI is still under discussion. Keep an eye out in release notes 2.21!
To construct the cross validation you want you would have to make one rule for each of your options. For ex. one rule that validates that if ‘Hours’ is selected, age must be below 24, and another for ‘Days’.
I am using DHIS version 2.20 build revision 19691.
I am having a doubt in Program rules.
We have a case where
Data element ‘Age Type’ has options i.e. Hours/Days/Weeks/Months/Years
Now if the user is selecting ‘Age type’ as Hours then another data element ‘Age’ should accept value between 0 to 23, application should not accept any value more that 23 in case of Hours ‘Age type’.
Similarly, If ‘Age type’ is **Days **then it should not accept more that 6 for ‘Age’ data element.