Brand-new: User Activity Tracking (Administration → Permissions → User Activity) The biggest new platform feature. Two tabs on one page: * Activity History — an append-only log of what a tracked user actually did. Every write on any module controller is captured server-side, and every genuine browser navigation is captured client-side (deliberately client-reported, because the server cannot tell a page refresh from a real navigation). Each row keeps the action, module, entity, route, HTTP method, success/failure + failure reason, IP, browser, OS, device type, session and timestamp. The user's name, email and branch are snapshotted onto the row, so the trail survives even if that person is later deleted. * Live Users — who is online right now, their last action, last module, last location, last activity time, source (web/mobile) and their roles. Supporting behaviour: * Three ways to switch tracking on, OR'd together: a per-user toggle (also self-servable from Profile → Preferences), a per-role toggle (added later in the cycle — "track everyone who is a Sales CRE", and it keeps following the population as people join and leave the role), and a global all-users switch. * Three-tier visibility: :view:all sees everyone, :view:branch sees users staffed at your branches, plain :view sees only yourself. New resource, so nobody inherits a legacy unfiltered view. * Rows are purged automatically past the retention window. * View modal is tabbed (Activity / Location / Device / System). * Both tabs export, and the Live Users export matches exactly what the grid shows (roles column included). * Filters were expanded mid-cycle from 3 to 10 on Live Users (User, Role, Last Action, Last Module, Last Location, Last Activity From/To), with searchable user/role dropdowns, and filters now persist between visits. * The menu was moved out of Administration and re-parented under Permissions, next to Login History, and given the menu grants it was originally missing. Exports — a broad correctness sweep * "Export all entries (one row per entry)" checkbox added to the export modal as a reusable platform capability. Ticking it flattens a parent grid into one row per child record, repeating the parent block on each row. Adopted by Service Vehicles and Field Service Jobs (below). * Excel dates now export as real dates, in your format. Previously exported timestamps didn't match what the grid showed. The converter now emits proper Excel date/time format codes, honours the user's configured date format, and separately handles date-only vs time-only columns. Location Tracking, Permission Audit and Delegation exports now pass raw timestamps through so the timezone renders correctly. * Every export endpoint now returns through one shared method (createExportResponse + generateExportFilename). Roughly 20 controllers across dealer, automotive, platform and supply-chain had been hand-rolling their own content-type and filename logic; that's gone. * New Service Approval Config export service.

The old page at /dashboard/services/vehicles/performance was just a catalogue of report cards. It's now a proper role-based dashboard with 7 tabs, built the same way as the dealer Lead Performance hub and the Used Vehicle hub. The tabs, and what each one actually answers: * Management — Total Entries, Completed, In Workshop, Total Revenue, Completion %, Avg Turnaround, plus Service Activity Trend, Revenue Trend, Pipeline Composition, Revenue by Branch, Workshop vs Body Shop, and Entry Source Mix. * Workshop Operations — Check-In vs Check-Out, WIP Aging (open vehicles by days since check-in), Delivery Commitment (open vehicles by promised date), Priority Mix, Temp-Out Status including vehicles physically off-site right now, Open WIP by Branch, and Status split by entry type. * Branch Manager — volume, revenue, completion rate (green ≥80%, amber 60–80%, red below), avg turnaround (green ≤2 days, red above 5), overdue counts, a Bottom-5 branches list, and a full per-branch detail table. * Service Advisor — the same shape per advisor, plus Commitment Load (overdue / due today / due this week) and a Discipline Score — 100 minus 5 per overdue promise and 2 per due-today promise. * Revenue & Billing — Revenue Composition Trend, Estimate vs Final Variance (green = under quote, red = over), Ticket-Size Distribution, Payment Mode Mix, Payment Status Mix (customer / warranty / AMC / dealership), Revenue by Service Type, Discount by Branch. * Vehicle & Customer Mix — Channel Mix, Top Models, Fuel Type, Transmission, Vehicle Age, Odometer at Check-In, Visit Frequency, Top Customer Cities. * Reports — the original 10 report cards, preserved. ServiceVehicleReportsIndexPage.tsx was split so the card catalogue could be reused as a tab instead of duplicated, and its quick-stats fetch moved off useEffect onto React Query.

Auditor role realigned across the whole product The read-only AUDITOR role had drifted badly since it was created. Twelve migrations (one per module) now enforce a single rule: Auditor gets every read-shaped permission Admin holds, and loses every write verb — including every :export (deliberate product call: auditors read, they do not extract). It also closed a latent security hole: several modules had granted Auditor a :view:all scope row without the base :view. Those rows are inert today because runtime authorities come straight from role_permissions and are never expanded through permission_dependencies — but the day anyone granted the base :view intending branch-scoped access, the dormant :view:all would have silently upgraded them to org-wide. Where a resource has no :view:all tier at all, Auditor simply mirrors Admin's tiers rather than inventing one. Metric Info — explain-this-number system A brand-new reusable component set (MetricInfoAnchor, MetricInfoButton, MetricInfoModal, MetricInfoTable). Every stat card, chart and table on the analytics hubs now carries a small info affordance; clicking it opens a modal explaining what the number means, how it's calculated, what it excludes, and — importantly — shows the live value for the current filter selection alongside the definition. Rolled out to 8 performance hubs (detailed under each module below). One fix during rollout: the anchor's z-index was removed because it created a stacking context that pushed the popup behind open modals. Sequential code generation — real production bug fix Delivery numbers, quotation codes, driver codes and call IDs were being generated from a table row count. As soon as any row is deleted, the count falls behind the highest code already issued, and the generator starts re-issuing codes that are still taken — failing the unique constraint on every subsequent attempt. This actually happened: customer creation was blocked for an entire branch because the delivery count had fallen 21 behind. New SequentialCodeGenerator derives the next sequence from the codes already issued for the same prefix, and compares them numerically rather than lexicographically — so 9999 → 10000 no longer wraps. Email

A delivery can no longer be dispatched until its documents are verified. Added a document-verification status (PENDING/COMPLETED) that gates dispatch specifically — it no longer blocks the normal status progression, only the actual dispatch step. Document verification (and PDI approval) now only kicks in once a delivery is out of DRAFT — draft deliveries are ignored so you're not chased for documents on something you haven't finalized. Fixed a bug where "phantom" PENDING rows were created for document types that were never actually uploaded — those are now excluded, so verification isn't falsely stuck. Document verification was decoupled from the general approval checks (in the delivery mapper/repository) so non-document approvals can complete independently. Latest-delivery visibility & actions on the customer grid The customer list now shows each customer's latest delivery status as a column, and the plain "Active" status column is hidden by default. Added action buttons for the latest delivery directly in customer management, plus a document-verification action for that latest delivery — you can act on the delivery without drilling in. Delivery movement / dispatch corrections When a final-delivery vehicle movement is cancelled, the delivery is now un-dispatched (reversed back to approved state and the vehicle reactivated), instead of being left stranded in a dispatched state. Delivery details are now re-fetched after a vehicle is attached or changed, so the screen reflects the real current status instead of a stale one. Movement forms and delivery tabs got a YARD_TO_BRANCH default movement type parameter. Added a delivery-location-type field to the customer response for richer delivery handling. Post-delivery document operations Added support for document operations on new vehicles after delivery (previously this was gated differently for used vehicles). Permissions Customer detail permissions split into finer grants: VIEW_CONTACT and VIEW_TYPE_DETAILS. Admins and Branch Admins can now bypass the creator/status split for vehicle management (they can manage vehicles they didn't create). Delivery-vehicle management permission extended to specific additional roles. For the Pasco client specifically, the "Dispatch Delivery" action permission was removed from certain roles.

1. Submittals — Role-based approval routing (the big one) Previously every submittal on a branch ran a single approval chain wired to specific named people. Now approval is driven by roles, and multiple chains can run at once. Uploader now picks one or more approval roles when creating a submittal. Each picked role kicks off its own approval chain. Chains run in parallel, levels run in sequence inside each chain. A rejection now fails only that chain instead of the whole submittal — the others keep going. New status: "Partially Rejected" — shown when one chain has failed while others are still in progress. A submittal only becomes fully "Approved" once every chain approves. Approvers are resolved dynamically: each level targets an approver role, and whoever currently holds that role in the branch can approve — no more editing configs when staff change. Backwards compatible: old branch-only configs with named assignees keep working exactly as before; nothing was migrated away or dropped. Approval-config screen now shows and lets you filter by "Routing Role" and "Approver Role" columns. Submittals grid gained "Approval Roles" and "Approval Progress" columns (hidden by default, available in export). Fixed a latent bug where recording a "Rejected" event in the status history violated a database check constraint — the history now accepts both REJECTED and PARTIALLY_REJECTED. Touched: new SubmittalApprovalRole entity, config/service/repository rewrites, the submittal detail + approval-config modals and workflow UI, migration V110012, and English/French/Hindi translations. Mobile got the matching approval UI (SubmittalFormScreen, SubmittalApprovalsSection) so it stays in parity.

Until now, users:view returned every user in the organisation to anyone who held it — including Branch Admin. And the Users page wasn't even reachable for them. This release closes both ends of that. Data scoping. The Users grid now works in three modes, the same pattern the dealer Customer page already uses: * users:view:all → see everyone (ADMIN) * users:view:branch → see only users staffed at your own branches * neither → unchanged legacy behaviour, so no existing role loses anything A Branch column and a Branch filter are now visible by default on the grid. For a branch-scoped user, the branch filter dropdown only offers their own branches — it can't tempt you with branches whose users you're not allowed to see. Reachability. Branch Admin now gets the Users menu, the full users:* action set, and read-only access to the Role / Group / Department / Designation lookups so the filter dropdowns actually populate (they were coming back empty). The Roles / Groups / Departments menus stay hidden — API read access only. The View/Edit buttons now work. Those buttons don't open a modal, they navigate to the profile page — a completely different page with its own gates, and Branch Admin was being bounced straight back to the dashboard. Two permissions the frontend had been referencing for months (user_profile:view_all, user_profile:edit_all) had never actually been created as rows — only ADMIN ever got through, via a role bypass rather than by holding a permission. Same story for users:manage_roles / users:manage_groups. All four now exist properly. Branch scoping isn't weakened by any of this: the profile read and save both go through a branch-scope guard on the server, so a Branch Admin still can only open and edit people in their own branches. One thing I want to flag honestly: the profile page has ~12 sub-tabs, each served by its own controller. Some of those have no authorization on the target user at all — any authenticated user could already read/write them for anybody, with or without this change. Others are hardcoded to ADMIN-only, so a Branch Admin will see the tab and get a 403. This release makes those tabs reachable in the UI; it did not create the underlying exposure, which predates it. It's documented in the migration and tracked as follow-up work.

You can now bulk-upload historical policies from Excel Until now a policy could only be created one at a time through the UI. If you were onboarding a dealer with two years of already-issued policies, that was hopeless. There's now a full import flow on the Policies page — download template, fill, validate, preview, import. * 26 columns: 8 mandatory (Branch, Customer Name, Customer Mobile, Insurer, Policy Number, Policy Type, Reg. No., Risk Start/End Date), 18 optional (email, chassis, engine, make/model/variant, IDV, NCB, OD/TP/add-on premium, discount, GST, payment status…). Branch and Insurer come down as dropdowns in the template so nobody can typo them. * Duplicates are keyed on the insurer's policy number — both against what's already in the DB and against other rows in the same file. * The import doesn't reimplement policy creation. It builds a normal PolicyRequest and goes through the same createPolicy path as the UI, so the underwriting rule engine still runs and a BLOCK rule fails that row instead of sneaking a bad policy in. Each row runs in its own transaction, so one bad row doesn't kill the batch (InsuranceNinjaPolicyBulkImportService.java). * One deliberate exception worth knowing about: normal policy creation lands in PENDING_INFO because reaching IN_FORCE needs payment + documents + discount approval. A five-year-old policy has none of those artefacts, so the import stamps the lifecycle status straight from the risk end date — past expiry → EXPIRED, future → IN_FORCE. That bypass exists only on the import path, it's behind its own permission, and every stamp is written to the policy history timeline as POLICY_IMPORTED. * New permission ins_ninja_policies:import, granted to ADMIN, and it implies create (V120176). 2. Insurers can hold more than one email and phone An insurer used to have exactly one contact email and one contact phone. Real insurers have a claims desk, an underwriting desk and a regional manager. * New child table ins_ninja_insurer_contacts (V120175). Existing single values are backfilled as the primary entry, and the old contact_email / contact_phone columns are kept and stay in sync with whichever entry is marked primary — so the grid column, the filters, the export and every bit of existing native SQL keep working untouched. * The Insurer add/edit modal and the view modal now use a new repeatable-row control: add row, remove row, star one as primary. * "At most one primary per type" is enforced in the service, not by a partial unique index — a partial index can't be deferred in Postgres, so moving the star from one row to another inside a single Hibernate flush would transiently break it. * Insurer export gained All Emails and All Phones columns (primary first, semicolon-joined) alongside the existing single-value columns. 3. Leads can hold multiple customer mobiles and emails Same treatment on the Leads side, and this one matters more day-to-day — a customer gives you their number, then their son's number, then a work email. * New ins_ninja_lead_contacts table (V120180), keyed on lead_id and not customer_id, because a lead can be created by typing a brand-new customer where there's no customer record yet. * Scoped strictly to Insurance Ninja leads — the shared customers table and the dormant customer_contacts table were deliberately left alone. * customer_mobile / customer_email remain as the denormalized primary, which is what keeps the bulk-import duplicate key (branch|mobile|registration), the grid filters, the search and the export all working as before. * Validation catches duplicates within the list and empty added rows on both web and mobile. * Lead export gained All Mobiles and All Emails columns. * Applied to the mobile Lead form screen in the same change, so web and mobile behave identically.

GPS trip-tracking now heals itself when the phone kills it (v2.4.85) This is the big one. On some Android phones the OS "freezes" the background location service to save battery, so a driver's live trip silently stops updating. The fix adds three safety nets working together: * Server-side watchdog — a scheduled job on the backend watches for trips that have gone quiet (a "gap" with no location pings) and sends a push notification to the phone to wake the tracking service back up. New TrackingHealthResponse, a last_gap_kick_at column on trips (migration V80054), and a health endpoint on the trip controller support this. * Native Android alarm backstop — an exact/inexact alarm (TripHealthAlarmReceiver) periodically revives the native location service even if the app process was frozen. * A tripActive state flag so the service knows whether it should be running and can decide whether to revive itself, avoiding zombie tracking after a trip legitimately ends. * The mobile Job Assignment tab and notification service were wired up to react to these wake-up pushes. You can now filter Service Jobs by their latest Call ID (v2.4.86) A new Latest Call ID text filter was added to the Service Jobs grid — on both the web page and the mobile job list. This required backend changes (the CustomerMachine query/repository/export services now accept and filter on latestCallId) plus registering the field in the platform filter allowlist (filterUtils.ts) so it isn't silently dropped. English/Hindi/French labels added.

Document Thumbnails (platform-wide — affects every module's document grids) * Uploaded images now get an auto-generated thumbnail at upload time (small JPEG, stored alongside the original). Non-images (PDF/HEIC/corrupt) safely fall back to the full file. * Document grids now load lightweight thumbnails instead of full-size images (presigned URLs accept a variant=thumb), while full-screen views still load the original. This is why almost every module's document API changed. * Thumbnails preserve aspect ratio, don't upscale, flatten transparency onto white (no black backgrounds), and respect EXIF orientation (portrait phone photos no longer show sideways). * Old documents get a thumbnail generated on first view (lazy backfill), done outside the DB transaction so it never ties up the connection pool. * Bumped default thumbnail size to 256px for crisper previews; added mobile rendering optimizations (Android decode-time downsampling, memoization) so many thumbnails no longer blow up memory. * Temp-file cleanup: capture/crop/watermark libraries used to leave junk files that filled the cache after ~10 photos and froze the camera button — these are now cleaned up per-upload and swept on app launch. * Fixed an S3 "insufficient data written" upload failure (stream was being re-read on retry) by switching to a fresh-stream provider.

GPS trip-tracking now heals itself when the phone kills it (v2.4.85) This is the big one. On some Android phones the OS "freezes" the background location service to save battery, so a driver's live trip silently stops updating. The fix adds three safety nets working together: Server-side watchdog — a scheduled job on the backend watches for trips that have gone quiet (a "gap" with no location pings) and sends a push notification to the phone to wake the tracking service back up. New TrackingHealthResponse, a last_gap_kick_at column on trips (migration V80054), and a health endpoint on the trip controller support this. Native Android alarm backstop — an exact/inexact alarm (TripHealthAlarmReceiver) periodically revives the native location service even if the app process was frozen. A tripActive state flag so the service knows whether it should be running and can decide whether to revive itself, avoiding zombie tracking after a trip legitimately ends. The mobile Job Assignment tab and notification service were wired up to react to these wake-up pushes. You can now filter Service Jobs by their latest Call ID (v2.4.86) A new Latest Call ID text filter was added to the Service Jobs grid — on both the web page and the mobile job list. This required backend changes (the CustomerMachine query/repository/export services now accept and filter on latestCallId) plus registering the field in the platform filter allowlist (filterUtils.ts) so it isn't silently dropped. English/Hindi/French labels added.

Services (Vehicle gate / boom barrier) * Auto-close stale check-ins at other branches. When a vehicle re-enters at a gate, the system now automatically closes a leftover "CHECKED_IN" entry that was left open at a different branch — a physical vehicle can only be checked in at one branch at a time, and the stale entry was blocking its exit at the new branch. * That auto-close was then tightened to only touch gate-created (AUTO) entries — staff-created manual or bulk-uploaded entries are never auto-closed — and the same-branch and cross-branch close paths were refactored to share one close-and-audit routine so their side effects stay identical. * Bug fix in the payment-status check. checkPaymentStatus was marked read-only, which silently dropped the audit-log rows it writes for every payment check. It's now a writable transaction so those audit records actually persist. * Financial tab split into two permission-controlled sub-tabs on the service-vehicle detail page: a Financial summary sub-tab (payments + invoice/charges) and a Documents sub-tab (bills/uploads). New per-sub-tab view permissions were added and granted by default to every role that already had the Financial tab, so nothing regresses for existing roles. Dealer * New "Find Vehicle" search. Added an endpoint/service to look up a PDI vehicle by chassis or registration number across the entire database with no branch/yard restriction — exact chassis match first, then partial chassis/registration match — excluding delivered and cancelled vehicles. Used to locate where a vehicle currently is. Automotive + Field Service * Consistent machine/model labels. Added a canonical getModelDisplayName() on VehicleModel that renders "Name (CODE)" (e.g. 135 (JCB-135)), and switched the Field-Service Customer-Machine and Service-Job mappers and export services to use it — so grids, detail views, and exports all show the same label the dropdown shows. Product Lift * Project-scoped dropdowns. Category and status dropdowns can now be filtered per project, so request forms/modals (web) and the mobile request form only offer the categories/statuses valid for the selected project. Platform — PASCO client * New "Billing Service Executive" role created for the PASCO client with a specific permission set. * That role is locked to the Documents sub-tab only — a follow-up client migration enforces that a Billing Service Executive sees only the Documents sub-tab (ties into the new services Financial/Documents sub-tab permissions above).

Services — Replacement Vehicles 5. Body Shop "Under Maintenance" toggle * Staff can now flip a replacement vehicle between AVAILABLE ↔ UNDER_MAINTENANCE from both web and mobile, with a confirmation dialog. * Gated by a new replacement_vehicles:maintenance permission (granted to exactly the roles that can already view the page), and the change is recorded in the vehicle's activity history. * Safety fix: a vehicle that's under maintenance can no longer be assigned during a handover. 6. New "On Fuel Run" status * Replacement-vehicle tracking gained an "On Fuel Run" status, wired through the stats page, tracking components, types and EN/FR/HI translations (plus the dashboard chart). 7. "On Replacement" label clarity * The "On Replacement" status label was reworded for clarity and localized across EN/FR/HI, on both the web Service Jobs view and mobile. 8. Housekeeping * Mobile MAINTENANCE category color was corrected to match the web CATEGORY_CONFIG (visual consistency). * Removed a couple of unnecessary document types from the replacement-handover constants (web + mobile). Field Service — Job Trips / GPS accuracy 9. Device-reported GPS interruption * The old gps_interrupted flag was inferred from gaps between saved GPS points — so a trip that recorded 0 or 1 points couldn't be detected as broken and looked like a legitimate no-travel trip. * The device now sends an authoritative interruption signal (native recording-health watchdog: GPS stopped delivering fixes, or Location/permission was turned off mid-trip). It's latched true and OR-ed into gps_interrupted at finalize, so near-total GPS failures are now correctly flagged. 10. Higher GPS precision (mobile native) * The trip service now waits for an accurate GPS fix before starting and requests highest-precision location for navigation (Android + iOS). 11. Capture device brand & model on trips * Each job trip now records the device brand and model, to help diagnose GPS-gap problems per device type. 12. Mobile Service Jobs branch dropdown * The branch dropdown on the mobile Service Jobs screen is now scoped to field-service branches only, matching the web Service Jobs page. 13. Bug fix — CustomerMachine filters * Fixed the CustomerMachineRepository query to use COALESCE for the created-by / updated-by filters, so those filters return the right rows. Field Service + Mobile — Image cropping 14. Immediate aspect-ratio selection * The image cropper (field-service jobs page + shared mobile component) now lets you pick the aspect ratio immediately and refreshed the available crop options accordingly.

Services — Replacement Vehicle Stats (brand new page) This is the biggest piece of new work. A whole new "Replacement Vehicle Stats" page was built, web + mobile. * New statistics dashboard for replacement vehicles that respects whatever filters the user has applied — the numbers on the cards recalculate to match the filtered view, they're not just a global total. * Added the full backend for it: a new ReplacementVehicleStatsResponse DTO, stats queries in the repository, service logic, and a new controller endpoint. * New menu entry inserted so the page shows up in navigation (migration V40231). * Built the matching mobile screen (ReplacementVehicleStatsScreen) with its own API, types, navigation route, and route-mapper wiring — so mobile users get the exact same stats page. * Also added filter-aware statistics to the existing Replacement Vehicles management page (the list page now shows live counts for the current filter). * Follow-up polish: reordered the statistics cards into a more logical order and turned the cards into clickable navigation links (tapping a stat jumps you into the filtered list) on both web and mobile. * Search added: the replacement-vehicle filters now support a text search box, and the dropdown handling was reworked to be cleaner. * Crash fix: branch dropdown options are now guarded against null/empty branch names so a bad branch record can no longer crash the mobile screen. Services — Pickup & Drop can now be scheduled for today Previously service pickup/drop requests could only be booked for tomorrow onward. Now: * Users can pick today (any time) or later, up to one month out — earlier calendar days are still rejected. * This was fixed properly end-to-end: the date picker's minimum date on web and mobile (the shared date util's getTomorrowStart became getTodayStart), and the authoritative backend validation in ServicePickupDropService (now uses "not in the past" against India-timezone start-of-day instead of "must be in the future"). * Editing other fields of an already-past-dated request still won't be blocked — the not-past rule only kicks in when the date itself actually changes. Field Service — Auto-complete work (skip the "Work Complete" button) * New workflow setting FS_AUTO_WORK_COMPLETE (default OFF, so nothing changes for existing clients). * When ON: the moment an engineer taps "Mark On-Site", the job jumps straight from Work In Progress → Work Complete. The manual "Work Complete" button disappears and the return-leg actions (Going Home / Going Office) appear immediately. * On this auto-flip the completion-photo requirement and the open-complaint guard are bypassed (they still apply to the manual transition when the flag is off). * Server-driven, so web and mobile both inherit it. * Enabled specifically for the Pasco client via a client override (V910187); all other clients keep the default off.

Mobile app (mobile/) New "Tracking Readiness" panel on the Service Job screen. The assigned engineer now sees, right above the status buttons, three device checks before starting a journey: Location permission granted Device Location (GPS) turned on Battery unrestricted (Android battery-optimization exemption) Each row shows a green "Ready" chip or a red "Fix" button. There's also a fourth, informational row — "Allow all the time" (background location) — which is shown but does not block starting (Android capture works without it, and hard-gating it risks Play Store rejection). Journey start is now blocked until the required items are Ready. If they aren't, the engineer gets a clear instruction instead of a vague error: "Get all Tracking Readiness items above to 'Ready' — tap each red 'Fix' to resolve it." One-tap "Fix" for each item. Tapping Fix runs the exact remediation needed — pops the OS location-permission dialog, turns GPS on in-app (Android) or opens Settings (iOS), and nudges the battery-optimization exemption. Each dialog only appears if that condition is actually unmet. The panel auto-rechecks whenever the app comes back to the foreground (i.e. after the engineer returns from a Settings screen). Mid-trip watchdog. While a trip is actively recording, the app re-verifies all three conditions on a timer and on every foreground return. If the engineer revokes location permission, switches off GPS, or the app gets re-restricted for battery during the trip, they now get an alert ("your trip route has stopped recording") — previously this produced a silent GPS gap, which was the leading cause of interrupted trips in production. Alerts are one-shot so they don't stack. Smart visibility. The readiness panel shows for the assigned engineer from the moment a journey can be started, through all en-route / on-site / return phases, and hides once the job is terminal (Done / Cancelled / Auto-closed) or still pre-acceptance. While a trip is actively recording, the rows go read-only (the watchdog handles fixes) to avoid double-prompting. GPS points are now tagged with their trip. Every queued point records which trip it was captured under, so a leftover offline queue always uploads to the correct trip and never bleeds into the next one. Old untagged points from a previous app build are attributed to the resuming trip or dropped rather than misfiled. iOS native buffer hardening (TripLocationModule.m). The offline point buffer was rewritten from a single JSON array to a durable append-only JSON-lines file (one point per line), with automatic migration from the old format and quarantine of corrupt lines — so no buffered point is lost across an app upgrade or crash. New i18n strings for all of the above (serviceJob.json).

Insurance Ninja (biggest area of work — 121 commits) New features Vehicle lead-candidate pages — new "Used Vehicles" and "Service Vehicles" grids under Customers that pull dealer used-vehicles and service-center vehicles cross-module as insurance lead candidates, with branch-type scoping (SHOWROOM vs SERVICE_CENTER). Includes an ignore/restore workflow (mark a candidate as ignored with a reason, restore later), and a safety check so the pages don't break if a source table is missing. Master customer-vehicle consolidation — leads and policies now link to a single master vehicle record instead of each carrying its own copied vehicle details. Color now cascades from the chosen variant. Policy draft lifecycle, payments & cancellation — full draft → in-force flow: record payments (pending only), cancel with a reason, new PENDING_INFO status, auto-expiry from risk-end date, and a rule blocking cancellation of fully-paid in-force policies. The ACTIVE status was renamed to IN FORCE. Policy document file uploads — real upload/download replaces the old metadata-only entries. Policy History Timeline — event-based audit timeline on the policy edit page; the old standalone Policy Audit page and view modal were removed. Lead bulk operations — CSV/Excel bulk import and bulk assignment of leads to CRE users. Renewals — configurable renewal window, bulk + single assignment modals, and a renewal-chain view inside the lead's Policies tab. Task management overhaul — assign / cancel / reschedule actions, REJECTED_BY_CUSTOMER status, activity timeline, linked-record association, and read-only enforcement on terminal tasks. Agent Profile restructure — agents managed through an "Insurance Agent" role instead of free create/delete; added Pending Verification and Suspended statuses. Menu reorg — Leads moved under Customers, Renewals moved under Policies. Shared Customer Profile / KYC tab reused across Lead and Policy sections. Improvements Converted lead / policy / renewal / task status filters and "Assigned CRE" to multi-select. Added a DND (Do Not Disturb) lead status; removed QUOTE_PRESENTED and PROPOSAL_SUBMITTED; dropped the mandatory lead-source requirement; enforced strictly-future follow-up dates. Added ~5,000 lines of in-app contextual help across every Insurance Ninja page. Empty grid cells now show "N/A"; forms switched from Select to SearchableSelect; customer dropdowns now show mobile numbers; default sort shows most-recently-modified first. Added URL validation on insurer website, document-presence checks for payment transitions, and remarks validation for follow-ups/renewals.

Services module Service documents * Added a full document-management feature for service entries — you can now upload, list, and manage documents (photos/PDFs) against a vehicle's service entry, with a new "Documents" tab in the service vehicle detail view. Seeded a "Bills" document type. WhatsApp financial summary * You can now send a financial/invoice summary to the customer over WhatsApp directly from a service entry. The system records the timestamp of when the message was sent (financialWhatsappSentAt) — and records it before dispatching so status tracking is accurate. Added a WhatsApp settings screen to toggle these notification features. Financial summary in detail view * Added a read-only invoice & charges summary to the service vehicle detail view, and split the Financial tab into two sub-tabs: Summary and Documents. Pickup/Drop reschedule * Added the ability to reschedule a service pickup/drop request via a new modal, with date validation (can't pick past dates; helpers for "tomorrow"/future dates). New reschedule permission seeded. Vehicle registration branch fix * When registering a vehicle, the branch dropdown now only shows showroom branches instead of all user branches. Field Service module Split trip distance into outbound + return * The "latest job distance (KM)" was split into two separate columns — outbound KM and return KM — in the service jobs grid, each with its own filter. Added the total distance to the customer machine response and export as well.

Test Drives / Demo Requests * The export now actually works — it was previously a stub returning an empty file. A real export service generates CSV/Excel honoring every active filter (code, branch, customer, lead, model, demo vehicle, status, date range, over-KM-limit) and the user's branch scope. Exported columns include dispatch/receive odometer & fuel, condition, driver, rating, and created/updated audit fields. * New filters added: Test Drive Code (text), Customer, Demo Vehicle (shows model + registration/chassis), and Over KM Limit (Yes/No). * Branch, Customer, Vehicle Model, Demo Vehicle, and Status filters converted to searchable selects with their own search placeholders (EN/FR/HI added). Customer Drops * Added a Drop Code text filter, wired through to the export so a code-filtered export returns only matching rows (EN/FR/HI added). Fuel Fillings * Replaced the internal-vehicle dropdown with a Registration Number text filter — type a registration directly instead of picking from a list. Removed the now-unneeded internal-vehicle fetch. Also added vehicle-fuel field validation. Vehicle Colors * The color-code filter now also matches hex code, so you can find a color by its hex value. Filter handling simplified to shared applyFilters/resetFilters. OEM Connections * Seeded the missing grid filter definitions so the Configure-Grid Filters tab works (previously "No filters available").

Three new columns on the vehicle list New / Used — every vehicle now shows whether it's new or used. Delivery Date — the date the vehicle was actually handed over to the customer. RM Name — the salesperson (Relationship Manager) who sold the vehicle. All three are sortable, filterable, and now also appear in the CSV/Excel export. RM filter is now a proper dropdown Previously you typed an RM's name into a free-text box (error-prone). Now it's a searchable dropdown that only lists people who can actually sell vehicles, and only those attached to your showroom branches — so you can't accidentally filter by someone irrelevant. New "Purchase Date" range filter You can now filter vehicles by the date they were purchased from the supplier (Purchase Date From / To) — useful for spotting aging stock. Cleaner filter bar Eight rarely-used filters (Vehicle Variant, PDI Code, PDI Status, Current Yard, Movement Status, PO Number, and the two purchase-date fields) are now hidden from the default filter strip but still available via the Grid Config gear. Less clutter for everyday users, full power still there for advanced users.

Exports now match the grid filters for: Branch Staff, Branch Working Hours, Document Category, all Feedback config screens (Branch Config, Category, Sub-Category, Global Config), Lead Sub-Source, Menu, Permission Matrix, and User Working Hours. Each export now accepts search + the same filter fields as its management grid, with proper branch scoping. Menu export also got a proper permission guard added (it was missing one). Export filter bug fix (frontend): falsy-but-valid filter values like "New Vehicle" (isUsedVehicle=false) or "Inactive" (isActive=false) were being silently dropped from exports. They now go through correctly. WhatsApp service: added the ability to send a WhatsApp message directly to a raw phone number (without needing a platform Notification record) — used by things like delivery OTPs. Filter allowlist & sort additions: registered the new Service Pickup/Drop and Vehicle filters (vehicle type, received/delivery date ranges, created-by/updated-by user) so they actually reach the API, and added missing sortable columns.

Dealer Bodyshop Conversions New Created By and Updated By filters (searchable dropdowns, scoped to your branches; opt-in via Grid Config). New Odometer document type (alongside Vehicle Condition / Other). Marking a conversion Converted or Follow-up Later now requires the mandatory Vehicle Condition document to be uploaded first. "Not Interested" still works without it. After marking Converted / Follow-up Later, you're auto-returned to the list. Used Vehicle Purchases New Created By and Updated By filters. New export of Used Vehicle Evaluations (honors the evaluation grid's filters and your branch scope). PDI (stock & movement) New Vehicle Type filter (New / Used / True Value) added to nine PDI grids (All PDI Stocks, PDI Movements, transit screens, Branch Stock, Return to PDI, etc.). Export added to five PDI Movement screens — Approvals, Damages, Documents, Inspections, Timelines — each with its own new export permission granted to Admin. Customers — list position is now preserved when opening a customer's View/Edit or the Feedback list. Vehicle Key Number — field length reduced from 100 to 20 characters everywhere (DB, new-vehicle form, PDI form) to match used/OEM-transit forms. Mobile-only menu hiding — several Performance dashboards (Used Vehicle Purchase, Customer, Dealer Performance hub, Stock) are now hidden in the mobile app (no mobile screen exists). Still on web. Cleanup — removed the dead free-text "Driver Name" search from the Supplier Drivers filter.

Field Service (mobile + web) This release's biggest real work. The whole point: make sure an engineer's trip route actually gets recorded and stop it silently failing. GPS won't start unless the phone's Location/GPS is actually on. Previously the app only checked that you'd granted location permission — but you can grant permission while the device's GPS toggle is OFF, in which case tracking "started" but recorded zero points. Now, when a trip starts, the app checks the device GPS itself. If it's off: On Android it pops the one-tap "Turn on location?" system dialog (the same one Google Maps uses) so the engineer enables GPS without leaving the app. On iOS (where you can't toggle it programmatically) it shows a "Turn on Location" alert with an "Open settings" button. The trip start is now blocked until GPS is genuinely on, instead of starting a dead tracker. A watchdog now catches GPS being turned off mid-trip. Every 20 seconds while a trip is active, the app re-checks that GPS is still on. If the engineer turns it off mid-route, it prompts them (once) to turn it back on so the route doesn't silently stop recording. It also re-checks the instant the app comes back to the foreground (the timer is paused while backgrounded). Tracking now auto-starts for the assigned engineer. When the engineer who's actually assigned to a job opens an en-route job that isn't being tracked yet (e.g. the status was advanced on the web or another device, or the app was reinstalled mid-trip), tracking turns itself on — no banner tap needed. It only tries once per job/status so a declined start doesn't loop. Only the assigned engineer records GPS. Added a guard so a manager or admin merely viewing an en-route job no longer auto-starts tracking and records their location against the trip. Polished the "tracking is OFF" banner. It's now hidden while a start attempt is in flight (including while the consent modal is open) so it doesn't flash, and it only shows for the assigned engineer. New dependency react-native-android-location-enabler (2.0.1) added to power the in-app Android "turn on GPS" dialog. Code-cleanup: the device-GPS check was moved out of the useActiveTrip hook (which now just delegates) into the location service as the single authoritative place. Web grid (field-service): the "Updated At" column is now visible by default on the Service Jobs grid (/dashboard/field-service/jobs). The grid already sorted by Updated At, but because the column was hidden, it never appeared in the Grid Configure → Sorting tab as a selectable sort column. (Migration V80043.) Wording tweak on the "trip didn't start" message — now tells the engineer to check that device Location is on, not just permission. PDI / Vehicle Movement (mobile labels) Added a "Vehicle Type" field label and a full set of movement-type labels to the mobile PDI movement screens (English, French, Hindi). These translate the raw codes into readable text, e.g. YARD_TO_BRANCH → "Yard (PDI) to Showroom", COMPANY_TO_YARD → "OEM to Yard (PDI)", plus an "All Types" filter option and an "N/A" fallback. (Commit "PDI 1".) Note: the dealer backend changes in this range were test-only — expanded integration-test coverage for PDI movement/damage flows; no production dealer code changed. Submittals (mobile) Fixed the date-filter labels on the mobile Submittals list. The "from" and "to" date pickers were both mislabeled "Created At". They now correctly read "Created From" and "Created To" (with new i18n keys added in English, French, and Hindi). Replacement Handovers (mobile) On the Replacement Handover form, document upload is no longer camera-only — engineers can now pick existing files/photos from the gallery instead of being forced to take a live photo (cameraOnly flipped to false). Mobile menu visibility (hide web-only performance pages on mobile)

What changed since v2.4.52 The work falls into four real features/fixes plus the routine version bump. There are also ~190 test files updated, which I've left out since they're not user-facing. 1. New "Vehicle Type" filter (New vs Used / True Value) across all PDI screens You can now filter PDI vehicle and movement grids by whether a vehicle is New or Used (True Value). This was wired end-to-end: Dealer web — added a "Vehicle Type" dropdown (All / New Vehicle / Used Vehicle) to the PDI Inventory filter and the PDI Movement filter. It now appears on all the PDI grids: All PDI Stocks, PDI Movements, Branch Stock, Current Branch Transit, Current Internal Transit, Current OEM Transit, Current PDI Stock, New Transit Request, Return to PDI. Mobile — the same dropdown was added to the PDI Vehicle list and every PDI movement screen so mobile matches web. Backend (dealer) — the /management, branch-stock, and export endpoints now accept an isUsedVehicle param, and the native SQL filters on v.is_used_vehicle. Export services honour it too (including a new nullable-boolean helper so "All" correctly leaves the filter unset). Database — two migrations (V20804, V20805) register the filter in filter_definitions and grid_preferences.default_filters for all nine grids. (The column existed since V20661 but the filter was never registered, so the UI silently did nothing — this fixes that.) Platform — isUsedVehicle was added to the filter allowlist in filterUtils.ts for the PDI inventory and movement scopes (otherwise the field would be dropped before reaching the API). 2. Key Number capped at 20 characters everywhere The "Key Number" field was inconsistent (100 chars in some places, 50 in others). It's now uniformly limited to 20 characters: Backend — validation on VehicleRequest and PdiVehicleRequest set to max 20. Database — migration V20806 shrinks vehicles.key_number from VARCHAR(100) to VARCHAR(20) (verified safe: longest existing value is 14 chars). Web — maxLength reduced to 20 on the OEM Transit, PDI Inventory, and Used-Vehicle "Complete Purchase" modals. Mobile — maxLength reduced to 20 on the PDI Vehicle form and the Used-Vehicle Complete Purchase screen. 3. Field-service trip GPS tracking made reliable (mobile) The biggest behavioural fix. Engineers' trip routes were sometimes silently not recording on the first journey. Multiple root causes were addressed: Permission race fixed — requesting OS location permission while the disclosure modal was still fading out caused Android to auto-deny it without showing the dialog. The flow now waits ~400ms for the modal to fully tear down, and double-checks the actual OS permission state before concluding the user denied it. Trip lookup retry — the trip is created server-side in the same transaction as the status change, but a replica/network race could mean it wasn't returned yet. The lookup now retries up to 4 times (~3s) instead of giving up immediately. "Route tracking is OFF" banner — a tappable amber banner now appears whenever a job is en-route but the GPS sampler isn't running for it, so a missed or declined start is always recoverable in one tap. Device-location pre-check — warns the engineer early if the device's GPS is switched off (app permission can be granted while GPS itself is off). Clear success/failure feedback — starting tracking now shows an explicit "tracking started" / "did not start — allow permission and retry" message instead of being fire-and-forget. Capture-meta retry — the telemetry POST that records capturing platform/source now retries 3× and logs a release-visible warning on persistent failure. New activeTrip state is exposed from useActiveTrip (with a tracking listener) so screens can reflect whether the route is actually recording. New i18n strings added for the messages above.

Dealer Three new analytics hubs (the bulk of the work): Sales → Customer Performance — a 15-report hub (lifecycle, segment/source attribution, value distribution, sales funnel, repeat visits, salesperson & branch leaderboards, follow-up discipline, etc.) plus 4 dashboard tabs. New permissions customer_performance:view / :view:branch / :export, all granted to ADMIN. Vehicle Desk → Stock Performance — 5 persona dashboards (Management, Inventory, Logistics, Sales, Branch) built on PDI/stock data: on-hand counts, ageing buckets, PDI readiness, transit-by-lane, days-to-sell, monthly inflow/outflow. Used Vehicles → Purchase Performance — 6 dashboards (Management, Branch, Buyer, Procurement, Pricing, Mix): spend, margin, valuation variance, procurement funnel, condition/age/odometer mixes, seller-source analytics. All three evict their own statistics caches on writes, and translations were added in English, French, and Hindi. Sales workflow & filters: Customers, Leads, Quotations, and Vehicle Pricing pages now share a branch-scoped useVehicleFilterDropdowns hook, and the Customer list/export gained Vehicle Model + Variant filters. Lead documents are now filed into the Document Explorer under /LEAD/{leadCode}/LEAD/ (new seeded LEAD category) instead of being uploaded folderless. Delivery gatekeeper split by vehicle type: the single "Delivery Dispatch Gatekeeper Required" setting is now separate toggles for new vs. used vehicles. Plus a bug fix: when the gatekeeper is not required, the DELIVERED state now correctly closes the vehicle's open location record so delivered vehicles stop showing as still present. Fixes: Pricing Component form dropped the "Depends On" parent/child field (simplified). Branch Pricing Status filter fixed (it had silently broken when the key changed from status to isActive). PDI vehicle grid sorting fixed — joined-column sorts (yard/branch/model/variant/company/status) no longer throw "missing FROM-clause entry"; delivered/completed vehicles are now visible across branches. Customer modal loyalty points capped at 0–999,999; Quotations page dropped a redundant stat card; OEM Transit import now reads the configurable row limit. Platform Document Management (big theme): Documents grid is now exportable (/documents/export, documents:export permission, includes created/updated-by columns). File-size filtering reworked to proper Min/Max KB numeric filters (both documents and my-documents); upload-date filtering fixed for timezones. Document viewing migrated off backend byte-streaming to presigned S3/R2 URLs — the preview modal and every personal-profile document view (Academic, Training, Travel, Health Card, Employment History) now open via presigned links. Configurable bulk-import limit: the hardcoded 500-row import cap is now an admin setting (bulk_import_max_rows, default 500, max 5000) editable in Admin Settings → Miscellaneous, applied globally across every module's import. Shared UI/utilities: New formatFileSize() and formatTagList() formatters. Date/time display switched to 12-hour AM/PM across all formatters. Input now actually enforces maxLength on number inputs; ViewModalBase now supports tab-less single-section modals. Filter allowlist + cache registrations added for the new dealer performance hubs. Testing: new reusable @WithMockUserPrincipal annotation + security-context factory, and the platform integration suite updated to use authenticated mock principals. One thing to confirm: the AdminSettingsMiscellaneousTab.tsx UI for the new bulk-import setting currently shows only as an uncommitted working-tree change — the backend setting and frontend hook are committed, but the UI tab edit isn't yet. Worth landing it in a commit.

The big behavioral fix here: users can no longer see jobs they can't actually open. * The jobs dropdown on the customer-machine edit page now shows only jobs the current user is allowed to view/edit. * Admins / view:all users → still see everything. * Assignment-scoped users → only their assigned jobs. * Branch-scoped users → only jobs in their branches (and a branch-scoped user with no branches now correctly gets an empty list instead of accidentally seeing everything). * The customer-machine list applies the same scoping to the Entries (job count) column and to all the "Latest" job columns (Latest Call, Job, Status, Branch, Customer, Mobile) — these now reflect the user's latest accessible job, not the machine's newest job overall. * Export was brought in line: the exported Entries count and latest-job data now match what's shown on screen for that user.

There are really three big stories here, plus some data and plumbing fixes. 1. The old "Reports" placeholder became a real Submittals module (brand new feature) The empty reports/ module was renamed to submittals/ and built out from scratch into a full feature. This is the single largest change — a whole new module, backend + frontend. What it actually does: Submittals workflow — users submit a "submittal" (a report-style document tied to a branch and a submittal type), and it moves through a status flow: SUBMITTED → APPROVED (final), or RETURNED → fix it → resubmit. Every status change is recorded in a history table so you can see who did what and when. Multi-level approval engine — there's a configurable "Approval Config" screen where admins define approval rules per branch, with assignees and conditions. Submittals route through these approvers.