Tutorial: Ops exception board
Outcome: external numbers land in the app on a schedule; the system flags exceptions; humans review and resolve them. Same shape as ops dashboards and watch queues. Use your own CSV or API; keep the tutorial domain generic.What you will assemble
Step 1 | Prompt in Build mode
Build an operations exception board. Operators upload a weekly CSV of metrics (entity id, period, and a few numeric columns). The app stores the batch, computes simple rollups, and creates alerts when a row crosses configurable thresholds. Operators work an alert queue: acknowledge, resolve with a note, or escalate. Managers see a digest of open high-severity alerts on weekday mornings. Roles: operator, manager.Approve when alerts are rows you can resolve, not only chart annotations.
Step 2 | Import → metrics → alerts
Upload form → import tool → compute metrics → generate alerts → alert queue page Use a small sample CSV. Failed rows should surface clearly (count + reason), not fail silently.Step 3 | Review queue
Wire resolve alert with a required note. Resolved items leave the open queue and appear in history. Preview as operator for the happy path.Step 4 | Thresholds and manager digest
- Config form for thresholds (manager or operator, your choice; document it in Access).
- Scheduled automation: email or in-app digest of open high-severity alerts to
manager. - Confirm under Executions after a manual or scheduled run.