Stian,
We will write a JIRA issue for this - but let me just point out immediately:
1. Normal users cannot be expected to understand/use the API, so with a UI
interface to do some kind of validation reporting, this feature is much
less useful that what it could be.
2. The idea of NOT storing
Hi Calle,
I see your points. Although persist is a techie-term, I think store and
save might also cause some confusion in this context, so maybe we should
add a short description in addition to clarify. It's hard to try and
explain it completely, but an example would be:
"Store any violations
Hi Jasper,
Could you create an issue here: https://jira.dhis2.org ?
Regards,
Knut
On Fri, Feb 2, 2018 at 12:45 PM, Jasper Timm wrote:
> Hi devs,
>
> I think I've spotted a couple of issues with completing data sets in Data
> Entry.
>
> There's a couple of uses
Hi devs,
I think I've spotted a couple of issues with completing data sets in Data
Entry.
There's a couple of uses of the completeDataSetRegistrations endpoint with
ds,pe, e.t.c. params but it looks like it's expecting dataSet, period e.t.c.
Hi
Version 2.28 had a new optional feature for Data Validation called "Persist
new result". Many users do not understand/know how this is supposed to be
used - partially because they are not familiar with IT techie terms like
"Persist" ("Store" or "Save" would be more user-friendly), but mainly
Hi DHIS Team,
We are awaiting response for this issue.
Thanks
Preeti
On Thu, Feb 1, 2018 at 3:33 PM, Kumar Shahdeo
wrote:
> Hi DHIS Team,
>
> Could you please give some update on this.
>
> Thanks
> Gaurav
>
>
> On Wed, Jan 31, 2018 at 7:11 PM, Kumar Shahdeo
6 matches
Mail list logo