← Back to team overview

dhis2-devs team mailing list archive

Re: [Dhis2-users] Program rule does not seem to be working

 

Hi David!
As you probably know, the program rules has their own chapter in the user documentation.
https://www.dhis2.org/doc/snapshot/en/user/html/dhis2_user_manual_en_full.html#d5e7293
But you have probably also noticed that the doc is pretty thin still. There will be more doc added in next release.

As for your question, for the "Yes only" and "Yes/No" datapoints you will have to use #{yesNoValue}==true, or just #{yesNoValue}

If you on the other hand had created an optionset with the values "Yes", "No" and "Unkown", you would have to use the name in your expression:
#{yesNoUnknownOptionSet} = 'Yes'

Markus

> 1. okt. 2015 kl. 14.25 skrev David Muturi <dnmuturi@xxxxxxxxx>:
> 
> Hi Markus and team,
> I am writing a program rule that evaluates a yes only value and hides another field I am wondering which response to use i.e. ==true or =='yes'. Is there anywhere these rules are documented for each of the data values?
> 
> rgds
> David
>  
> 
> 2015-09-23 9:46 GMT+03:00 Markus Bekken <markus.bekken@xxxxxxxxx <mailto:markus.bekken@xxxxxxxxx>>:
> Hi Ese, there is no limit to the number of rules. I have one usecase with about 150 rules running on a program
> What does you second rule look like? There is probably something that prevents the second rule from working correctly.
> 
>> 23. sep. 2015 kl. 08.39 skrev Ese Egerega <ese@xxxxxxxxxx <mailto:ese@xxxxxxxxxx>>:
>> 
>> Hello,
>> 
>> Please is there a limit to the number of rules I can have on a single form? For example, I have a rule which hides some fields based on if the patient is HIV positive. I created a second rule which is meant to hide other fields based on if the patients HIV status is previously known. Only the first rule seem to be working in Tracker Capture.
>> 
>> Thanks,
>> Ese
>> 
>> On Tue, Sep 22, 2015 at 2:59 PM, David Muturi <dnmuturi@xxxxxxxxx <mailto:dnmuturi@xxxxxxxxx>> wrote:
>> Thanks team  !#{location} or #{location} == false works for boolean questions.
>> rgds
>> David
>> 
>> 2015-09-22 16:09 GMT+03:00 Abyot Gizaw <abyota@xxxxxxxxx <mailto:abyota@xxxxxxxxx>>:
>> oh yes, thanks Markus. I mixed up :(
>> 
>> 
>> ---
>> Thank you,
>> Abyot.
>> 
>> On Tue, Sep 22, 2015 at 2:53 PM, Markus Bekken <markus.bekken@xxxxxxxxx <mailto:markus.bekken@xxxxxxxxx>> wrote:
>> Hi guys,
>> Try !#{location} or #{location} == false
>> 
>> Best regards,
>> Markus
>> 
>>> 22. sep. 2015 kl. 14.49 skrev Abyot Gizaw <abyota@xxxxxxxxx <mailto:abyota@xxxxxxxxx>>:
>>> 
>>> Hi David,
>>> 
>>> If value "No" is type boolean, then try 'true' instead of no. It should work. That is something we planned to address.
>>> 
>>> 
>>> ---
>>> Thank you,
>>> Abyot.
>>> 
>>> On Tue, Sep 22, 2015 at 2:45 PM, David Muturi <dnmuturi@xxxxxxxxx <mailto:dnmuturi@xxxxxxxxx>> wrote:
>>> Hi Abyot,
>>> I have placed a rule see attachment but it doesn't work under data entry when value no is selected.
>>> rgds
>>> David
>>> 
>>> 2015-09-22 14:49 GMT+03:00 Abyot Gizaw <abyota@xxxxxxxxx <mailto:abyota@xxxxxxxxx>>:
>>> Hi David,
>>> 
>>> In 2.20 we have hiding only for data elements (during data entry).
>>> 
>>> Hiding attributes (during registration) is available only in trunk.
>>> 
>>> ---
>>> Thank you,
>>> Abyot.
>>> 
>>> On Tue, Sep 22, 2015 at 1:47 PM, David Muturi <dnmuturi@xxxxxxxxx <mailto:dnmuturi@xxxxxxxxx>> wrote:
>>> Hi Abyot
>>> Tracker Capture, I am using version 2.20 build 19884. I upgraded after seeing the online demo working on event capture. I have cleared the Cache.
>>> rgds
>>> David 
>>> 
>>> 2015-09-22 14:42 GMT+03:00 Abyot Gizaw <abyota@xxxxxxxxx <mailto:abyota@xxxxxxxxx>>:
>>> Hi,
>>> 
>>> Some questions for pin-point the problem:
>>> Is this on event or tracker capture app? 
>>> Which version of DHIS 2 are you using - both version and revision number? 
>>> Have you tried this after clearing your browser cache?
>>> 
>>> ---
>>> Thank you,
>>> Abyot.
>>> 
>>> On Tue, Sep 22, 2015 at 1:38 PM, David Muturi <dnmuturi@xxxxxxxxx <mailto:dnmuturi@xxxxxxxxx>> wrote:
>>> Same here, I have put a rule that hides a question based on an answer to a different one i.e {location}=='No'  and it doesn't seem to be working. 
>>> rgds
>>> David
>>> 
>>> 2015-09-22 5:53 GMT+03:00 Pramil Liyanage <pramilcl@xxxxxxxxx <mailto:pramilcl@xxxxxxxxx>>:
>>> You are welcome. Same thing happened in an earlier build and I replaced with the latest at that time which was 19876 and worked for me. Did not try 19884. May be the same issue repeating.
>>> 
>>> Pramil
>>> 
>>> On Mon, Sep 21, 2015 at 9:01 PM, Ese Egerega <ese@xxxxxxxxxx <mailto:ese@xxxxxxxxxx>> wrote:
>>> Thanks Pramil,
>>> 
>>> Using single quotes and clearing my cache fixed the problem for me. 
>>> 
>>> However, it appears that the very latest build version 19884 has a problem with program rules. When you create and add a rule, it disappears. I tested this on dhis2 demo site and got the same result. I have copied the developers list in case this is a bug that needs to be fixed.
>>> 
>>> Thanks again,
>>> 
>>> -Ese  
>>> 
>>> On Mon, Sep 21, 2015 at 4:06 AM, Ese Egerega <ese@xxxxxxxxxx <mailto:ese@xxxxxxxxxx>> wrote:
>>> Thanks so much Pramil. I will try that now.
>>> 
>>> -Ese
>>> 
>>> On Mon, Sep 21, 2015 at 3:45 AM, Pramil Liyanage <pramilcl@xxxxxxxxx <mailto:pramilcl@xxxxxxxxx>> wrote:
>>> Dear Ese,
>>> 
>>> Try with single quotations 'Female' and clear the cache and try.
>>> If not working, get the latest build and try. I also had a similar issue with an older build, but when I replaced with the latest, worked fine.
>>> 
>>> Regards
>>> Pramil
>>> 
>>> On Mon, Sep 21, 2015 at 8:00 AM, Ese Egerega <ese@xxxxxxxxxx <mailto:ese@xxxxxxxxxx>> wrote:
>>> Dear all,
>>> 
>>> The Program Rule feature does not seem to be working for me. I am trying to hide a section in the tracker based on if the Gender selected during program registration is Female. 
>>> 
>>> To achieve this, I created a program rule that should hide the section but nothing seem to happen in Tracker Capture. The section is still displayed as if there is no rule set.
>>> 
>>> In program rule I entered Gender as source field and used the following as my expression:
>>> 
>>> A{Gender} == "Female"
>>> 
>>> I will appreciate any assistance.
>>> 
>>> Thanks,
>>> Ese
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~dhis2-users <https://launchpad.net/~dhis2-users>
>>> Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx <mailto:dhis2-users@xxxxxxxxxxxxxxxxxxx>
>>> Unsubscribe : https://launchpad.net/~dhis2-users <https://launchpad.net/~dhis2-users>
>>> More help   : https://help.launchpad.net/ListHelp <https://help.launchpad.net/ListHelp>
>>> 
>>> 
>>> 
>>> 
>>> -- 
>>>  <http://hissl.lk/index.php/2015-conference>
>>> 
>>> 
>>> 
>>> 
>>> 
>>> -- 
>>>  <http://hissl.lk/index.php/2015-conference>
>>> 
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~dhis2-devs <https://launchpad.net/~dhis2-devs>
>>> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx <mailto:dhis2-devs@xxxxxxxxxxxxxxxxxxx>
>>> Unsubscribe : https://launchpad.net/~dhis2-devs <https://launchpad.net/~dhis2-devs>
>>> More help   : https://help.launchpad.net/ListHelp <https://help.launchpad.net/ListHelp>
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~dhis2-devs <https://launchpad.net/~dhis2-devs>
>>> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx <mailto:dhis2-devs@xxxxxxxxxxxxxxxxxxx>
>>> Unsubscribe : https://launchpad.net/~dhis2-devs <https://launchpad.net/~dhis2-devs>
>>> More help   : https://help.launchpad.net/ListHelp <https://help.launchpad.net/ListHelp>
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~dhis2-devs <https://launchpad.net/~dhis2-devs>
>>> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx <mailto:dhis2-devs@xxxxxxxxxxxxxxxxxxx>
>>> Unsubscribe : https://launchpad.net/~dhis2-devs <https://launchpad.net/~dhis2-devs>
>>> More help   : https://help.launchpad.net/ListHelp <https://help.launchpad.net/ListHelp>
>> 
>> 
>> 
>> 
> 
> 


Follow ups

References