Cases Configuration
Integrations
Review how case integrations exchange approved data with external systems, monitor sync history, and keep configuration details controlled by authorised administrators.
Data enrichment
Send data to a third party (state authorities / government) and get enriched data back. The History tab shows each request and status — Awaiting send, Sent, Awaiting manual reply, Matched, Failed, Timed out. From a request: apply to the case, reconcile from CSV, or open the case manually.
Connection setup
The operational flow is what matters: approved case data can be queued, exchanged with an external authority or provider, reconciled back to the originating case, and recorded in the integration history.
Schedules
Send hourly / every 4h / daily / weekly (advanced cadence in seconds, 60 s–7 days, blank = disabled), set inbox-poll frequency, and permitted send days (some authorities only accept certain weekdays; others defer).
CSV format
Administrators define the approved file structure, field mapping and code translation rules for each integration. Consistent files make it easier to reconcile case updates, provider responses and exported outcomes.
Third-party infringements
Confirmed cases can be exported to an approved third-party workflow when the organisation chooses to do that. Export behaviour should be governed by policy: disabled, manually reviewed by operators, or automated only where the authority has approved that operating model.
Part of Cases · Configuration · Home