dhis2-devs team mailing list archive

[Lars Helge Øverland <larshelge@xxxxxxxxx>]

Hi Andrew,

thanks for your suggestion. At the moment we are using compulsory data
elements only for reporting rate statistics, as one often would like
to define them for data elements that in most cases should be filled,
but not necessarily, and it would not be an error to leave them blank.
But I can see that it could make sense to have this as a setting per
data set, like "Compulsory data elements should raise validation
error" or similar. Let's see what we can do.

Lars


On Mon, Oct 15, 2012 at 9:49 AM, Muhire Andrew <muhireandrew@xxxxxxxxx> wrote:
> Hi,
>
> In reporting rate summary if someone selects an option says: Based on
> compulsory data elements, and in custom forms we have data element with
> category A & B and B is disabled, If we run reporting rate summary will it
> not count this B and displays o% score, or the system counts only data
> elements that is linked to the form? Or its best in section forms?
>
> Suggestion :
>
> 1.What if we make it optional and  put another button that we can select so
> that if a user puts nothing to the compulsory data element the system`s
> complete button refuses to validate as complete till these selected data
> elements are filled. (we make it optional).
>
> 2.Making it optional to validation rules also.
>
>
> The reason for this is that some of the users can click on complete and
> submit blank sections, so if we make it compulsory with options it can be
> good.
>
>
>
>
> thanks!
>
>
>
>
> ________________________________
>
>
> Muhire Andrew
> HMIS/Ministry of Health
> First say to yourself what you would be; and then do what you have to do..
>
>
> _______________________________________________
> 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
>