Three places
The complaint, the case and the map are updated separately.
Code complaints flow from 311 into the case system and onto a code-case map, and closures flow back, so officers, the public and the dashboard all agree.
The complaint, the case and the map are updated separately.
Cases without a map point can't be planned into a route.
The complainant never hears that the case was closed.
The 311 triage template checks each changed request, sends new potholes, lights and trees to Scheduler crews, code cases to the ArcGIS map, and everything else to an SFTP file.
When Sentra 311 sends request.created, code-enforcement requests become new Accela records. Everything else is ignored.
Sentra 311 → Sentra Scheduler → PostgreSQL / PostGIS → Esri ArcGIS feature layer → SFTP serverCleans and checks changed 311 requests, sends bad ones to a data-quality sub-flow, checks the city database to see if each is new, then routes new…
Accela Civic Platform → Sentra 311Every 15 minutes, finds Accela records closed since the last run and closes the matching Sentra 311 request.
Pre-built connectors used in this solution. Anything else with an API, a database or SFTP works too.
We'll set up a workspace with your systems in a sandbox and build your first flow with you.