dhis2-devs team mailing list archive
-
dhis2-devs team
-
Mailing list archive
-
Message #42864
Preventing capturing of events and tracker data backdated beyond a certain date
Hi all,
>From what I can see it is not possible to prevent a user to select an
Enrollment/Event date in either Tracker capture or Event capture beyond a
certain date back in time.
Use case is that users are selecting an incorrect date when capturing
tracker and event capture dates such as e.g. 2005/01/01 for current data
which affects the period against which such data is reported.
Question: Is there any such functionality where one can add a date in which
can be periodically changed to e.g. the start of the financial year to
prevent users capturing the incorrect date?
If not can I write a blueprint for it to the effect of either being able to
select a specific date e.g. 1 April 2015 or a number of periods back in time
e.g. 1 week/2 months etc and the system would then not allow backdated
capturing beyond this date specified?
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.
--
*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.*