Order Management — Release Notes v1.4.1
Order Management — Stage heatmap (v1.4.1)
| Release version | OMS 1.4.1 · Ailaaj One 1.3.5 | | Release date | 18 June 2026 | | Applies to | Insights → Reports v2.0 → Operations Intelligence → Operational KPIs → Heatmap | | Availability | GA — same View Operational KPIs Report permission as v1.4 |
What this release is
Warehouse leads can now see when work landed, not just how much. The Stage ledger heatmap adds an hour-of-day grid on Operational KPIs: each cell shows load and operators for that stage and hour; the footer totals load per hour and unique staff across the day (not a misleading sum of hourly headcounts).
New Features
- Heatmap tab on Operational KPIs — 24-hour columns with shift colouring when warehouse shifts are configured.
- Load / Crew / Load·op views — toggle what each cell emphasises (volume, operators, or load per operator).
- Hour detail drawer — click a cell to see operators and stage breakdown for that hour.
- Row layout — reorder or hide stage rows; layout persists per browser.
- Export — Excel (three sheets) and PDF with view picker; styling matches on-screen heatmap.
Improvements
- Crew day totals — row and footer operator counts use distinct staff for the period, including invoice and refund stages.
- Refunds in heatmap — hourly refund load appears when the compact KPI RPC omits buckets (repair fetch).
- Cloud-only heatmap RPCs — operator heatmap calls always hit cloud analytics so hub mirrors cannot serve stale function bodies.
Fixed
- Footer day operator total showed the sum of hourly distinct counts (e.g. 311) instead of unique operators for the period (e.g. 33) when
period_operator_totalwas missing from the API payload.
Database
Apply on each environment (dev before prod):
20260630150000_reports_v2_operational_heatmap.sql20260630170000_reports_v2_operational_kpis_refunds_hourly.sql20260630180000_reports_v2_operational_heatmap_invoice_refund_operators.sql20260630190000_reports_v2_operational_heatmap_period_operator_total.sql
npm run db:migrate:devCONFIRM_PROD_MIGRATE=yes npm run db:migrate:prodKnown limitations
- Hourly footer cells still show distinct operators that hour; only the Day column uses period-unique staff.
- Some manual/HMS metrics remain Not tracked for operator attribution until those workflows are wired.