Hey Cha!
You are doing some pretty advanced expressions here, but it seems you got the
syntax all correct. We are making better tools for syntax and integrity
checking in the coming DHIS2 versions, I can imagine you had to do some
counting to check that you got the right amount of parenthesis he
Calle
Yes, i did a refresh and a hard refresh and even more i deleted all the
browser cache :D
Yes, the stage appear if i remove the hide program stage rule.
Regards,
On Mon, Oct 8, 2018 at 11:18 PM Calle Hedberg
wrote:
> Hi
>
> agree - if the expression is false, no action is taken.
>
> maybe
Hi
agree - if the expression is false, no action is taken.
maybe it's a refresh thing - have you tried to refresh the page?
And does the stage appear if you remove the hide program stage action from
the Prog Rule?
Regards
calle
On Mon, 8 Oct 2018 at 22:08, Amjad Ata-Allah
wrote:
> Calle
>
>
Calle
Yes, but the programe stage should appear when the expression is false, which
is not happening. Even the warning message disappear when the expression is
false.
Sent from my iPhone
> On Oct 8, 2018, at 11:03 PM, Calle Hedberg wrote:
>
> Hi
>
> If the warning message appear when the da
Hi
If the warning message appear when the dagnosis value is something else
than meninges, then it means the expression correctly evaluated to TRUE.
So the expression is correct.
And the other action if expression is true, is to hide the meninges stage,
yes? and that stage correctly does not appe
Thanks Calle
I replaced the OR with AND.
I added another action to the rule "Show warning message" for testing, and
now the warning message appears but the program stage don't.
So the issue is with the program stage.
Any suggestions?
Regards,
On Mon, Oct 8, 2018 at 2:41 PM Calle Hedberg
wrote:
Dear Calle,
The case is that i have like 20 diagnosis, i need to hide the stage if the
diagnose is not one of those 3 diagnosis and show the stage if its one of
them.
I also tried the &&, but didn't work also.
After clearing the cache, i have this error:
TypeError: Cannot read property 'id' of u
Amjad,
That error is a data-related error (I had something similar last week, and
tracked it down to one single orgunit that had an erroneous attribute value
- but in your case the data error might be somewhere else, no idea where).
If you get that kind of error, it often results in other program
Hi
You only use the code if that has been specified in the option set
(tick-box).
Secondly, you are using OR and NOT in your expression:
#{aDiagnose} != 'Meningitis - Other Bacterial' || #{aDiagnose} !=
'Meningitis - Hemophillus Influenza' || #{aDiagnose} != 'Meningitis -
Meningococcal Meningiti
Dear Zubair,
Yes it is, and i tried both (name and code).
Regards,
Sent from my iPhone
> On Oct 8, 2018, at 9:47 AM, Zubair Asghar Raja wrote:
>
> Hi Amjad
> Is aDiagnose an option set? If it is then try using code instead of name.
>
>
> Zubair
>
> Den man. 8. okt. 2018, 6:50 a.m. skrev
Hi Amjad
Is aDiagnose an option set? If it is then try using code instead of name.
Zubair
Den man. 8. okt. 2018, 6:50 a.m. skrev Amjad Ata Allah <
ataallah.am...@gmail.com>:
> Hi Stephen
> Here is the condition expression:
> #{aDiagnose} != 'Meningitis - Other Bacterial' || #{aDiagnose} !=
> 'M
Hi Stephen
Here is the condition expression:
#{aDiagnose} != 'Meningitis - Other Bacterial' || #{aDiagnose} !=
'Meningitis - Hemophillus Influenza' || #{aDiagnose} != 'Meningitis -
Meningococcal Meningitis'
Thanks,
On Mon, Oct 8, 2018 at 12:41 AM Stephen Ocaya wrote:
> Hello Amjad M. Ata-Allah
Hi Calle,
Thanks a lot for your advice. However, the 1 (yes/true) and 0 (no/false) works
for Program Indicators but I doesn't work for a Program Rule.. I even tested
few minutes ago but i doesn't for program Rule.
Best Regards
Sele
On Wednesday, May 16, 2018, 11:48:03 AM GMT+3, Calle He
Hi
use 1 (yes/true) and 0 (no/false) instead
regards
calle
On 15 May 2018 at 16:35, Seleman Ally wrote:
> Dear Team,
>
> For a several versions of DHIS2 (Including 2.29), I have been struggling
> to create *responsive* Program Rule for attribute or data elements with
> Yes/No type. There is n
Hi Edouard Lavaud,
Thanks for your guide. Actually I want the system to show an error message
if user enters value < 5 for the input field.
It's very easy to check if we use value type is Number or Date (for Date of
birth). But I really want to use Age value type because it's nice feature
for Trac
Hi Em Le Hong,
If I well understand:
You capture the age at a different moment than you would like the
program rule to be executed?
If no, program rule executed on the same stage as you capture the age:
To be checked (never used the age value type so far), but age should
be an integer. S
Hello Markus,
I'm using Version: 2.27, Build revision: c5ef790, Build date: 2017-09-24
06:25.
I will raised this issue in Jira.
Thanks for your response.
Regards,
Rady
On Oct 16, 2017 12:54 PM, "Markus Bekken" wrote:
> Hi there Rady,
> Nicely spotted. Which version of DHIS are you running? Th
Hi there Rady,
Nicely spotted. Which version of DHIS are you running? This message is noise
from a runtime validation that is a bit too strict, and can be disregarded for
the purposes of the users. Log noise is still important to clean up, so it
would be great if you can submit a Jira with the d
Hi there,
thank you for the detailed report below.
This problem was fixed and released around the time of the original request,
but for some reason has not been included in the later 2.25 builds. I
redeployed and rebuilt the code now, please try again with the latest 2.25.
(https://github.com/dh
Hi!
Any feedback on this issue so far? In case it is of any help, I noticed the
following. When updating one dataelement in an event that was directly
added (sign + in the user interface of the Tracker Capture) the payload
generated was:
{"event":"donHXNZZSoH","orgUnit":"ElSpSqucvZg","program"
Hi!
Any feedback on this issue so far? In case it is of any help, I noticed the
following. When updating one dataelement in an event that was directly
added (sign + in the user interface of the Tracker Capture) the payload
generated was:
1.
{"event":"donHXNZZSoH","orgUnit":"ElSpSqucvZg","p
s2-devs-bounces+ditana
> <mailto:dhis2-devs-bounces%2Bditana>=hispna@lists.launchpad.net
> <mailto:hispna@lists.launchpad.net>] On Behalf Of Markus Bekken
> Sent: Tuesday, September 27, 2016 3:06 PM
> To: calle.hedb...@gmail.com <mailto:calle.hedb...@gmail.com>
> C
I am doing wrong?
Kind regards,
David
*From:* Dhis2-devs [mailto:dhis2-devs-bounces+ditana=
hispna@lists.launchpad.net] *On Behalf Of *Markus Bekken
*Sent:* Tuesday, September 27, 2016 3:06 PM
*To:* calle.hedb...@gmail.com
*Cc:* dhis2-devs
*Subject:* Re: [Dhis2-devs] Program
Hi again,
It seems saving a programrule for hiding tracked entity attributes works, but
there was a bug that prevented the tracked entity attributes from being visible
when reopening the rule.
This is now fixed in 2.24 and trunk, new builds running now. Older versions was
not affected.
Note:
Hi,
Thanks Markus.
With regard to not being able to edit or add program rules in SL demo, FYI:
it was a user rights issue. Logging in as system sorted that problem out -
it looks like the standard admin user don't have privileges to do anything
on program rules.
Regards
calle
On 27 September 20
Thanks for reporting, Calle. There was a related fix on trunk yesterday night
that seems to have fixed the below mentioned issue as well. Looking into fixing
the same in 2.24 now.
Markus
> 27. sep. 2016 kl. 12.16 skrev Calle Hedberg :
>
> Hi
>
> This increasingly looks like a significant bug
get the latest trunk. It was not working yesterday but is fine today.
Markus added a fix.
On Tue, Sep 27, 2016 at 12:16 PM, Calle Hedberg
wrote:
> Hi
>
> This increasingly looks like a significant bug - Elmarie just added a
> similar program rule (i.e. using a 'MALE' value in the Gender attribut
Hi
This increasingly looks like a significant bug - Elmarie just added a
similar program rule (i.e. using a 'MALE' value in the Gender attribute to
hide the Pregnant attribute) in another instance, and the result is the
same: the action field value is replaced by "None" and there are no
drop-down
28 matches
Mail list logo