Data Sets have a property called Expiry Days, which determines when reporting is locked after the end of the period.
This can be overridden by a supervisor who creates a “lock exception” to allow later reporting.
Is it only in these cases that a report becomes registered as being “not on time”?
Knut
If I remember correctly, all timeliness is based on the system setting for reporting timeliness, not on the Expiry dates.
If I remember correctly (again), different timeliness dates for different datasets is on the roadmap for a future release.
Data Sets have a property called Expiry Days, which determines when reporting is locked after the end of the period.
This can be overridden by a supervisor who creates a “lock exception” to allow later reporting.
Is it only in these cases that a report becomes registered as being “not on time”?
Knut
–
Knut Staring
Dept. of Informatics, University of Oslo
+4791880522
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp