From da5acacf5a500906c1b0094e85fbab56804b02df Mon Sep 17 00:00:00 2001 From: Jan Bernitt Date: Thu, 22 Feb 2024 16:59:15 +0100 Subject: [PATCH] docs: data integrity slow and programmatic filters [DHIS2-16223] --- src/developer/web-api/data-validation.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/developer/web-api/data-validation.md b/src/developer/web-api/data-validation.md index 321aa995d..62acb0203 100644 --- a/src/developer/web-api/data-validation.md +++ b/src/developer/web-api/data-validation.md @@ -546,6 +546,18 @@ Additional results can be filtered using a `section` parameter. The `section` filter will return all exact matches which have the specified section. +Furthermore, to filter (select) only checks marked as `isSlow` use `slow=true`, + + GET /api/dataIntegrity?slow=true + +or to filter (select) only checks that are not performed via database query +(programmed checks) use `programmatic=true`: + + GET /api/dataIntegrity?programmatic=true + +The `slow`, `programmatic` and `section` filters can be combined in which case +all conditions must be met. + ### Running data integrity summaries { #webapi_data_integrity_run_summary } Since version 2.38, data integrity checks have two levels of specificity: