dhis2-users team mailing list archive

[Lars Helge Øverland <lars@xxxxxxxxx>]

Hi Eric,

I understand your question. We do not plan to add additional enum options
though which are not used by DHIS 2 internally as it will cause confusion
for developers.

For app development purposes I would recommend that you instead create a
data element which could be called "Validated", have a particular code
(e.g. "VALIDATION_STATUS") and be of value type Yes/No (boolean). You can
then in your app set a corresponding data value through the regular events
resource of true or false, and then use this to keep the validation state.
This of course creates a dependency on the configuration which should be
documented.

regards,

Lars







On Fri, May 20, 2016 at 12:25 PM, eric mourin <ericmourin@xxxxxxxxxxx>
wrote:

> Hi everyone,
>
> We are developing an application that needs to know if some events
> (captured via event capture) were validated by an authorized user or not.
> I've seen that events have an "status" field  which can have the values
> "ACTIVE, COMPLETED, VISITED, OVERDUE, SKIPPED" but I couldn't get much
> information about what meant each field from the documentation so I was
> wondering if its possible to create a "VALIDATED" status for the events and
> then make a put with the status changed. If this is not possible (not
> accepted via Update by the web api) or can bring future problems with newer
> versions, would it be possible to reuse one of the status already listed
> there? I've seen the ACTIVE and COMPLETED status but I've never seen the
> rest used.
>
> Thanks for your time
> Eric
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-users
> Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
lars@xxxxxxxxx
http://www.dhis2.org <https://www.dhis2.org/>