dhis2-devs team mailing list archive

["Elmarie Claasen" <elmarie@xxxxxxxx>]

Hi Markus,

 

Thanks for that info will look into it. 

Yes I want to add a rule preventing capturing ie before 2015/04/01 and when a user select a date before Error message appears forcing them to choose a correct date. 

But every year I need to move the date on by 1 year.

 

Regards,

 

Elmarie Claasen

Hisp logo

Project Manager

Health Information Systems Program

Tel:      041-367 1027

Cell:     082 374 2209

E-mail:  <mailto:elmarie@xxxxxxxx> elmarie@xxxxxxxx

Skype:  elmarie.claasen52 

 

 

This message and any attachments are subject to a disclaimer published at  <http://www.hisp.org/policies.html#comms_disclaimer> http://www.hisp.org/policies.html#comms_disclaimer .   Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission. 
If you cannot access the disclaimer, kindly send an email to  <mailto:disclaimer@xxxxxxxx> disclaimer@xxxxxxxx and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer. 

 

From: Markus Bekken [mailto:markus.bekken@xxxxxxxxx] 
Sent: 05 February 2016 02:52 PM
To: Elmarie Claasen
Cc: dhis2-devs@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Dhis2-devs] Question on tracker dates and effecting limits on dates for which data may be captured

 

Hi Elmarie!

 

Interesting! 

 

The mentioned incident and enrollment dates is available in the program rules, with the syntax V{enrollment_date}, V{incident_date} and V{current_date}. See table 30.3 for the full list of supported "variables": http://dhis2.github.io/dhis2-docs/master/en/user/html/dhis2_user_manual_en_full.html

 

You want this rule to run on the TEI registration page, preventing the enrollment where there is a sufficiently big gap?

 

Best regards,

Markus

 

5. feb. 2016 kl. 12.12 skrev Elmarie Claasen <elmarie@xxxxxxxx>:

 

Hi Devs,

 

I hope that someone will be able to assist with an issues around tracker. 

 

We want to limit users on the dates for which they can capture tracker/event data both on the program event/incident date.

DHIS 2 allows a setting to allow future dates but no limit on limiting past dates. 

For a few of our use cases it would be very useful to limit the data on a program between 2 dates. The dates specified should have some fluidity to it (can be adjusted) as time progress e.g. I would like to specify that users may only enter data for the financial year between 1 April – 31 March of a specific year and next year adjust those dates to the current year. No of periods to allow would not really make sense because that depends on where you are in the year. 

The implication of leaving these types of dates open to select/enter anything really allows users to capture data for the 1st Century or for 2 years ago and you already concluded an annual report on the data captured for that period which is now being altered by the user selecting an incorrect date. One is not likely to run reports and unless you look for such data in the backend you would never find it.

I tried to set up a program rule to limit the date which a user can capture to after a specific date but I see that it is only the data elements that is exposed in the programrules. 

Would it be possible to include the Enrollment date and Incident dates?

 

Regards,

 

Elmarie Claasen

<image001.png>

Project Manager

Health Information Systems Program

Tel:      041-367 1027

Cell:     082 374 2209

E-mail:  <mailto:elmarie@xxxxxxxx> elmarie@xxxxxxxx

Skype:  elmarie.claasen52 

 

 

This message and any attachments are subject to a disclaimer published at  <http://www.hisp.org/policies.html#comms_disclaimer> http://www.hisp.org/policies.html#comms_disclaimer .   Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission. 
If you cannot access the disclaimer, kindly send an email to  <mailto:disclaimer@xxxxxxxx> disclaimer@xxxxxxxx and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer. 

 





This message and any attachments are subject to a disclaimer published at  <http://www.hisp.org/policies.html#comms_disclaimer> http://www.hisp.org/policies.html#comms_disclaimer.  Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission.  If you cannot access the disclaimer, kindly send an email to  <mailto:disclaimer@xxxxxxxx> disclaimer@xxxxxxxx and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer.

_______________________________________________
Mailing list:  <https://launchpad.net/~dhis2-devs> https://launchpad.net/~dhis2-devs
Post to     :  <mailto:dhis2-devs@xxxxxxxxxxxxxxxxxxx> 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

 


-- 


*This message and any attachments are subject to a disclaimer published at 
http://www.hisp.org/policies.html#comms_disclaimer 
<http://www.hisp.org/policies.html#comms_disclaimer>.  Please read the 
disclaimer before opening any attachment or taking any other action in 
terms of this electronic transmission.  If you cannot access the 
disclaimer, kindly send an email to disclaimer@xxxxxxxx 
<disclaimer@xxxxxxxx> and a copy will be provided to you. By replying to 
this e-mail or opening any attachment you agree to be bound by the 
provisions of the disclaimer.*