Beta feature. Ask your implementation engineer for access.
How it works
1
Enable Evidence Checks on an event type
In Data Inputs > Input Settings, open the event type you want to configure. Each datapoint can have Evidence Check turned on or off individually (off by default).Datapoints with Evidence Check enabled show an icon in the Add Events form.
2
Create events: checks run automatically
After an event is created, Evidence Checks runs in the background on all enabled datapoints. Checks also re-run when:
- Evidence is added or removed from a datapoint
- A datapoint or its event is saved
3
Triage alerts
Click on an alert icon to open the alert detail panel, which shows the entered value alongside the value extracted from the evidence.From here you can:
- Dismiss the alert with a reason. See Dismissing an alert.
- Update to match, which changes the datapoint to the value found in the evidence, converted to the datapoint’s unit. It appears only when the two values disagree. For a datapoint with a fixed list of options, it appears only when the evidence value is one of them.
- Update the evidence to re-run the Evidence Check
- Re-run evidence check, from the right-click menu on a datapoint’s alert icon in event details, to check the attached evidence again. It reuses what was already read from the file, so it picks up new hints but won’t fix a poor scan. Attach a clearer copy for that.
How values are compared
A document checks only the datapoints it is attached to. Evidence attached to one datapoint is not used to check another datapoint on the same event.
If Mangrove reads a document with less than 70% confidence, every datapoint mapped to it gets an alert, including values that match. The alert shows the confidence it reached. Attach a clearer copy of the document.
A datapoint can have several documents. One matching document is enough: when one passes, alerts from the datapoint’s other documents clear. A document that disagrees stays silent once another one matches, so check each document yourself when it matters.
Dismissing an alert
Each alert offers one suggested reason, depending on what went wrong, plus Other, where you describe your own:
A dismissal on an alert about what a document says lasts only until that document is checked again. Saving any datapoint the document is attached to, or its event, adding or removing evidence, or Re-run evidence check all check it again, and a mismatch that is still there comes back as a new alert.
Where results appear
Evidence Check results are visible across the platform:- Events table: status icon column (same column as anomaly detection)
- Event details: on individual datapoints
- Batch tables: on the inputs tab
Improving future checks with hints
When you dismiss an alert with its suggested reason, you can optionally provide a hint to improve future extractions. For example, you might specify which table, row, or section in the evidence document contains the correct value. These hints are stored per datapoint type and incorporated into future checks, making checks progressively more accurate over time. Successful matches are also automatically recorded to reinforce correct field mappings.Supported evidence formats
Evidence Checks can extract and validate data from:Evidence that is provided as a URL or in an unsupported file format can’t be read, so it raises an alert saying the file type is not supported. Attach the document as a supported file, or dismiss the alert.