What high-level problem are you trying to solve?
We use ODK Entities to power multi-stage case management workflows (e.g., GBV intake, clinical follow-ups, referral tracking). In these workflows:
- Field workers use ODK Collect to log initial cases(Form A), creating a lightweight Master Entity with basic metadata.
- Back-office staff log into ODK Central to review cases and fill out Form B (Back-Office Form). This form asks sensitive follow-up questions, applies complex validation logic, and updates the Entity's operational status (
case_status,assigned_to).
The Friction: Currently, back-office users in ODK Central are forced to open Form B in a separate external browser tab/session (via Web form/Enketo). For staff managing dozens of multi-stage case updates daily, constantly switching back and forth between the Central admin interface and standalone form tabs creates severe tab clutter, breaks operational context, and introduces significant workflow fatigue.
Any ideas on how ODK could help you solve it?
Allow Web Forms to render natively inside the ODK Central UI for logged-in Central Web Users.
- In-App Form Rendering- When a back-office user opens/submits a form linked to an Entity or Submission inside Central, render the form within a native slide-out panel, modal, or integrated inner view rather than launching a new browser tab.
- Seamless Context Retention- Upon form completion, the user should be returned immediately to the active Entity/Submission view in Central with updated state, without having to close tabs or manually refresh the list.
- Native Desktop Experience-This would transform ODK Central from just a data collection backend into a streamlined, single-canvas case processing hub (similar to native web forms in enterprise CRMs like Salesforce or NetSuite).
Upload any helpful links, sketches, and videos
N/A