← Back to team overview

dhis2-devs team mailing list archive

Re: Locking Data Values when Data Set is Complete


Hi Lars,

Yes, upon completion data fields should be disabled and reenabled on
clicking incomplete. Then assessing timely submissions will be more


On Wed, Mar 28, 2018, 1:04 PM Dennis Banga <dennisbanga@xxxxxxxxx> wrote:

> Hi Lars
> Referring to the same issue and some challenges we experience (jira issue),
> such a functionality will really help . It can be a data set configuration
> that supports the current behavior  and the suggested behavior. In
> addition, an audit trail for the completing and in-completing of data sets
> in data entry module will help in tracking changes within data sets as the
> available data value audit trail functionality.
> Ahsante.
> Dennis
> On 27 March 2018 at 12:52, Lars Helge Øverland <lars@xxxxxxxxx> wrote:
>> Hi Pamod,
>> thanks, to clarify, what you want is simply to disable the input fields
>> when the complete button is clicked, and the renable the input fields when
>> the incomplete button is clicked?
>> Lars
>> On 27 March 2018 at 08:26, Pamod Amarakoon <pamodm@xxxxxxxxx> wrote:
>>> Dear All,
>>> This is with reference to the previous discussion on similar issue in
>>> 2015 (link below)
>>> https://lists.launchpad.net/dhis2-devs-core/msg00377.html
>>> As I'm aware disabling editing of data values happens through locking
>>> mechanism which is mainly dependent on expiry date and data approval.
>>> We have a situation in Sri Lanka where we are already using expiry date
>>> and data approval in the data workflow. But due to practical reasons we
>>> cannot set a relatively short expiry date. We are assessing performance of
>>> facilities based on data set completion date. To achieve our objective we
>>> need to lock the data set after completion thereby if a user needs to edit
>>> data again then he first has to incomplete data set (so completeness date
>>> changes accordingly).
>>> Currently we are using a modified form.js in web-data entry folder to
>>> achieve this. Just wondering whether there are any plans to implement this
>>> feature in near future.
>>> Thank you.
>>> --
>>> Regards,
>>> Pamod Amarakoon
>>> MBBS (SL)
>>> MSc (Biomedical Informatics), EMSc (Health Admin), PGCert (MedEd), CEH
>>> HISP Sri Lanka
>>> Confidentiality Notice: the information contained in this email and any
>>> attachments may be legally privileged and confidential. If you are not an
>>> intended recipient, you are hereby notified that any dissemination,
>>> distribution, or copying of this e-mail is strictly prohibited. If you have
>>> received this e-mail in error, please notify the sender and permanently
>>> delete the e-mail and any attachments immediately. You should not retain,
>>> copy or use this e-mail or any attachments for any purpose, nor disclose
>>> all or any part of the contents to any other person.
>> --
>> Lars Helge Øverland
>> Technical lead, DHIS 2
>> University of Oslo
>> lars@xxxxxxxxx
>> https://www.dhis2.org
>> _______________________________________________
>> Mailing list: https://launchpad.net/~dhis2-devs
>> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~dhis2-devs
>> More help   : https://help.launchpad.net/ListHelp

Follow ups