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.

New "Reject by Customer" action (pick 6) A pickup/drop request can now be marked Rejected by Customer — a distinct terminal state, separate from an internal "Cancelled", so reports can tell the two apart. Added a manager-only permission service_pickup_drops:reject. It's auto-granted to every role that already has :cancel (admins/coordinators), and it pulls in :view as a dependency. The assigned driver does not get it, so the Reject button stays hidden on driver logins — exactly like Cancel. Backend: new PATCH /{id}/reject endpoint, rejectByCustomer() service method that notifies the assigned driver the job is off (same message as a cancellation), and a guard so a completed/cancelled/already-rejected request can't be rejected again. Migration V40213 extends the status CHECK constraint and wires up the permission + role grants. Web: new RejectByCustomerModal + Reject action in the management table. Mobile: matching ServicePickupDropRejectModal + card action. New "Created date" filter (pick 5) You can now filter pickup/drop requests by created date (from/to), in addition to the existing "requested date" range. Added createdAtFrom/createdAtTo to the filter allowlist, the backend native query, web filter UI, and the mobile list (mobile now supports a second date-range filter in its shared ListHeader).

The work after version 2.4.40 is a single release that moves the whole platform from 2.4.40 to 2.4.41. There were two commits, and apart from one set of build-script improvements (which you've asked to leave out), everything in this release is the version bump itself. No business module had any application code change. What actually changed: The application version was raised to 2.4.41 across the entire codebase. This includes the platform frontend package, all the backend service version files, and the root project version file. A database migration was added that updates the stored app version setting to 2.4.41 and the build number to 2040041, so a running system reports the new version correctly. The mobile client configurations for all four clients were also moved up to 2.4.41 with their matching build numbers. In short, between 2.4.40 and 2.4.41 there is no new feature, no bug fix in any business screen, and no change to any of the modules' logic. It is purely a version-increment release. The Assets, Warehouse, and Supply-Chain-Core modules likewise only had their version line updated and no real changes.

Customer Delivery now submits itself for approval automatically. Before, a salesperson had to manually click "Submit for Approval" once everything was in place (draft status, customer set, quotation linked, vehicle with chassis/registration attached, all mandatory documents uploaded). Now whichever action completes that checklist auto-fires the submit — order doesn't matter, and the manual button still works as a fallback. Built with two new events (DeliveryActionCompletedEvent, CustomerInvoiceUpdatedEvent) and a DeliveryAutoSubmitListener that runs after the user's action commits, in its own isolated transaction, so an auto-submit failure can never break or roll back the original action. A customer update re-checks every draft delivery for that customer. Fixed a document auto-verify bug on Customer Delivery. When verifying documents on behalf of a user, the "any one" rule was marking document types as VERIFIED even when no file had ever been uploaded. Now only types that actually have an uploaded file get auto-verified; the rest stay PENDING. Used Vehicle: dropped the free-text "Make" field, replaced with Company (migration V20796). The make is now derived from the vehicle's linked Company instead of a typed-in string. The "Make" column on both the Purchases and Evaluations grids becomes a "Company" column. Cleaned out across the entity, DTOs, mapper, service, export, search queries, and all five frontend edit tabs — and mirrored on mobile (see below). Lead & Quotation statistics cards now match the grid below them. The stat cards were computed with a different access scope than the list, so the totals didn't reconcile. They now use the exact same admin/branch/hierarchy scope as the grid. PDI Stock Yard statistics simplified. Statistics are now explicitly fleet-wide totals, and the "Current Occupancy" card was removed entirely (grid goes 5→4 cards). Vehicle-presence counts are now status-aware — they count distinct vehicles in IN_STOCK/AT_YARD/IN_TRANSIT and exclude anything that's reached final delivery, so the total reconciles with the in-stock + in-transit breakdown. Relatedly, when a vehicle is dispatched at final delivery, its open yard-location record is now closed so it stops counting as "present." Vehicle Status page dropped the "Registered" and "In PDI" cards (6→4). Cleanup: replaced hardcoded nil-UUID placeholders with the shared UuidUtils.NIL constant across several query services.

This was the largest non-warehouse theme — a rework of how multiple files get uploaded across the whole product. * One failed file no longer kills the whole upload. Previously, uploading several documents used Promise.all() / sequential loops, so a single failure aborted the entire batch. There's now a shared resilient batch-upload utility (platform/frontend/src/utils/uploadBatch.ts + mobile/src/utils/uploadBatch.ts) that uploads in parallel (3 at a time), attempts every file, and returns success/failure counts. It only errors if nothing uploaded. * iPhone photos (HEIC/HEIF) can now be uploaded. iOS captures photos as HEIC by default, which was being rejected. .heic is now in the allowed-extensions list on backend (ObjectStorageService.java), frontend, and mobile, backed by migration V614__Allow_heic_uploads.sql. The migration is idempotent and preserves any custom extension list an admin already configured. * Every document API was migrated to the new resilient batch. All uploadMultiple* methods across training, academic, personal, health, travel, employment, customer, feedback, used-vehicle, PDI, sales-order, accessories, product-lift, bodyshop and replacement document APIs now delegate to the shared utility and accept an optional batch-options (concurrency + progress) parameter. * Partial-failure messages are now honest. Instead of silently dropping files, screens now say e.g. "Uploaded 3 documents, 1 failed. Please retry the failed files." (DocumentUploadEdit.tsx, dealer's CustomerDocumentsView.tsx, FeedbackDocumentUploadSection.tsx, UsedVehicleDocumentsTab.tsx). * Mobile: thumbnails appear one-by-one as each file finishes instead of after the whole batch, and a new shared DocumentUploadIconsRow.tsx keeps the upload icons tappable (with a spinner beside them) so users can queue more documents while one is in flight. * Client-side validation now happens before upload on several screens (file type & size checked against admin-configured limits with an immediate toast), and file pickers now use the admin-configured accepted types instead of hard-coded lists. A real workflow fix: letting several customers compete for the same vehicle without crashing. * Multiple pre-SOLD deliveries can now exist for one vehicle. Previously this caused a NonUniqueResultException that surfaced to users as "Database is unavailable." Repository lookups now return prioritized lists ("winner-first") instead of assuming a single active delivery. * Marking a delivery SOLD auto-blocks the competitors. When one delivery is sold, the other pre-SOLD deliveries for that vehicle are automatically deactivated and marked "superseded," linked to the winning delivery. * New BLOCKED state in the UI (web + mobile). Superseded deliveries now show a red BLOCKED badge/banner — "This vehicle has been sold to another customer (delivery #XYZ)" — and all action buttons are hidden. New i18n keys added for customer:delivery.status.BLOCKED and the blocked title/message. * Backend guards every mutation. Editing, deleting, attaching a vehicle, verifying documents, or approving a superseded delivery now fails fast with a clear "delivery is blocked" error rather than partially applying.

Field Service — Pickup & Drop 1. Statistics cards now respect who's looking at them (backend: services module) Previously the summary cards on the Pickup/Drop management screen (Total, Pickup, Drop, Requested, In Progress, Completed) always showed global counts for everyone. Now they're scope-aware — a driver only sees counts for the requests they're actually allowed to see, a branch user sees their branch, and admins still see everything. The card numbers finally match the rows in the grid below them. New scoped count queries in ServicePickupDropRepository (countByAccessScope, countByTypeAndAccessScope, countByStatusAndAccessScope). New overloaded getStatistics(...) in ServicePickupDropQueryService that mirrors the list query's hierarchy/branch/assigned filters. The old unscoped version is kept (and still cached) for callers that genuinely want global totals. 2. "Accept Job" button only shows for the assigned driver (web + mobile) The Accept action used to appear for anyone with edit permission on an ASSIGNED request. The backend has always rejected anyone but the assigned driver ("Only the assigned driver can accept"), so the button was misleading. Now it only renders when the logged-in user is the assigned driver — on the web table, the mobile card, and the mobile detail screen. 3. Documents tab added to the Pickup/Drop view (web + mobile) Both the web view modal and the mobile detail screen now have a read-only Documents tab, showing the photos/files uploaded during handover (reusing the existing upload component / EntityDocumentsTab in read-only mode). 4. Stale action buttons self-correct after a failed action (web + mobile, all 3 mobile screens) If you tap an action (e.g. Accept) but the server has already moved the request on (someone else accepted it), the action fails. Previously the now-invalid buttons stayed on screen. Now the list/detail refreshes automatically after a failure so the buttons reflect the true server state. 5. Stronger input validation on the Pickup/Drop request (backend + mobile form) Backend (ServicePickupDropRequest): contact name restricted to letters/spaces/hyphens/apostrophes/periods; contact mobile must be exactly 10 digits; registration number must be alphanumeric only. Mobile form (ServicePickupDropFormScreen): full on-blur + on-submit validation matching the web modal — person-name format, mobile sanitization/format, registration format, required source. Mobile inputs now sanitize phone input and use the shared MOBILE_MAX_LENGTH. 6. Mobile handover screen — Remarks moved below the photos (mobile) The Remarks field on the handover screen was relocated to its own section after the document upload, for a more natural top-to-bottom flow. 7. Wording polish — mobile "Source is required" message added; "Pickup & Drop not enabled" now tells the user where to enable it ("Global Settings → Service"); section titles aligned ("Request", "Status Timeline", "System Information", "Documents").

Release 2.4.35 Complete Change Log 1. Internal Vehicles Bulk Import from spreadsheet (NEW FEATURE) Automotive (backend + frontend), mobile permission * Dealers can now upload a file to add their internal/demo fleet in bulk instead of one vehicle at a time. A new Import button appears on the Internal Vehicles page, gated behind a new permission. * The import is two-phase: a dry-run validation pass previews every row's outcome, then a write pass that commits each row independently  one bad row doesn't fail the whole file. Users get a per-row report (succeeded / failed / skipped) with field-level error messages to fix and retry. * Spreadsheet supports 16 columns: branch, model, vehicle types (comma-separated codes), fuel type, chassis, registration + optional variant, color, engine, transmission, odometer, FASTag, insurance/fitness expiry, notes. Requires branch + model + fuel type, and at least one of chassis or registration. Foreign keys resolved by name on the backend; company derived from the model. Duplicate chassis rejected both within the file and against the DB. * New permission internal-vehicles:import  granted to ADMIN, depends on internal-vehicles:view (migration V10091). Added to automotive frontend constants and the mobile permission list. Translations in EN / FR / HI. * Files: InternalVehicleController (new /bulk-import endpoint), InternalVehicleBulkImportService (~650 lines), 3 import DTOs, V10091, internal-vehicles/page.tsx, internalVehicleImport.ts (column config), internalVehicleApi.ts (bulkImport() with dry-run flag).

PDI (Pre-Delivery Inspection) — Dealer module 1. "New Transit Request" renamed to "Delivery Request" * The menu item, page title, and stats header are now "Delivery Request" everywhere — web sidebar, help text, and the mobile app (English / Hindi / French all updated). * The URL stays /dealers/new-transit-request, so old bookmarks and links keep working. 2. New global setting: "Show Create Movement for New Vehicles" * Setting key PDI_CREATE_MOVEMENT_NEW_VEHICLE under Global Settings → Dealer → PDI, off by default. * When off, the Create Movement (truck icon) button is hidden for new vehicles on PDI screens. Used vehicles always show it regardless. * Applies to PDI Vehicles, Current PDI Stock, and several mobile transit/movement screens. 3. Quality-check step can now be skipped on PDI pages * A new qualityCheckRequired switch controls whether the Quality Status button is a mandatory gate before Approve. * On PDI Vehicles / Current PDI Stock / Delivery Request: for internal movements in PLANNED status, the Quality Status button is hidden and Approve becomes the direct next step. * Branch Stock (and other pages) keep the old behavior — quality status must be filled before approval. 4. PDI roles trimmed (Pasco client) * PDI Incharge and PDI Gate Keeper roles lose access to: Final Delivery, Branch Stock, Vehicle Status, and Find Vehicle. The now-empty "Delivery" and "Vehicle Desk" parent menus disappear from their sidebars too. Replacement Vehicle / Handover — Services module 5. Handover status renamed "Approved" → "Booked" * The whole replacement-handover workflow is now CREATED → BOOKED → HANDED_OVER → RECEIVED (with CANCELLED). * The action button label changes from "Approve" to "Book", confirmation messages updated, and status badges/colors/filters updated across web, mobile, and the platform status utility. * DB migration drops the old CHECK constraint and updates live rows to BOOKED; historical audit logs keep the original "APPROVED" value for accuracy. 6. Replacement-vehicle dates now show date-only * Handover date, receive date, and last-receive date no longer show a time component — simplified to a clean date on the detail screen, detail page, and the management table (web + mobile).

Field Service * Field Service Engineers can now create service jobs. The role was granted the service_jobs:create permission permanently (migration V80034), so it no longer has to be patched into each database by hand. * A job an engineer creates no longer vanishes from their own list. When an "assigned-scope" engineer (who only sees jobs assigned to them) creates a job, they're now auto-added as an assigned engineer. * The Customer Machine list now respects who you are. Engineers only see machines whose latest service job they're allowed to view preventing the 403 error that used to happen when opening a machine's latest job. * The "Total / Active Machines" stat cards now match the list  same access scopes applied, so the counts no longer disagree with the grid. * Customer Machine export honors the same scopes  you can only export the machines you can actually see. * New Service Job modal auto-selects the branch when there's only one. Bodyshop Conversions * Leads can now carry their own Company / Model / Variant (migration V40207), independent of a linked service vehicle. All three are optional. * Bulk import gained an optional "Variant Code" column. Enter a variant code and the system auto-fills the Company, and the Model too if the variant maps to exactly one active model. Codes are case-insensitive and validated; a bad code rejects just that row with a clear message. * Manual lead creation now has cascading Company → Model → Variant dropdowns on both web and mobile. Picking a Company loads its Models, picking a Model loads its Variants, and changing a parent clears the children. All searchable, all optional. * A dedicated "Vehicle Details" section now appears on the conversion detail page (web) and detail screen (mobile) read-only when viewing, editable (same cascading dropdowns) when editing a manual lead. * Bulk-uploaded leads are now treated as editable manual leads (a new UPLOAD lead source alongside MANUAL), so they flow through the same edit path. * Grid filters and exports now match against both sources  the lead's own Company/Model/Variant or the linked service vehicle's, so one filter value catches every lead type, and exports show the correct values regardless of origin. PDI Vehicles * Fixed an incorrect "Received Date." Previously it was inferred from the oldest location row's creation time, which was unreliable for OEM-transit vehicles. There's now a real received_date column (migration V20787), stamped at the moment the vehicle is received at yard, and existing records were back-filled from status history. * "Received Date" is now a real grid column on both Current PDI Stock and PDI Inventory sortable, filterable, visible by default; shows on mobile vehicle cards too. * Received-date range filters now use the actual received timestamp (timestamp-precise, not a rough date), and mobile converts the picked day to full UTC day boundaries so it matches web exactly.

Service Pickup & Drop (brand-new feature — web + mobile) A complete new module for managing doorstep collection and return of customer vehicles for servicing. * Two request types: Pickup (collect vehicle from customer — always on) and Drop (return vehicle to customer — admin-toggleable, off by default). When Drop is disabled, its menu and forms are hidden on both web and mobile. * Request capture: registration/chassis or a linked vehicle, customer contact (existing CRM customer or quick ad-hoc name+mobile), preferred time, pickup/drop address, request source (phone, WhatsApp, app, email…), and notes. Each request gets a unique reference code. * Driver workflow with full status timeline: Requested → Assigned → Accepted → In Progress → Handover → (Return in Progress, for Drops) → Completed; can be Cancelled at any step with remarks. * Handover capture: odometer reading, fuel level (empty / quarter / half / three-quarter / full), and multiple photos/documents (vehicle-condition photos, insurance, other). Mobile photos are geo-tagged with location and timestamp. * Notifications: drivers are auto-notified on assignment and on handover completion. * Permissions & data scoping: view-all (admin), view-by-branch (managers/coordinators), view-own (drivers); plus create, edit (workflow transitions), assign, cancel, delete, export. The Driver role is auto-granted "own + workflow" access only. * Web management page under Services: filtering (branch, type, status, registration, driver, customer mobile, date range), sortable/customizable grid, statistics dashboard, CSV export, and a detail modal with history + attached documents. * Mobile app: dedicated list, request form, detail, and handover screens — drivers can accept, start journey, complete, cancel, and do photo/odometer/fuel handover on the go. Service Pickup & Drop (brand-new feature — web + mobile) A complete new module for managing doorstep collection and return of customer vehicles for servicing. * Two request types: Pickup (collect vehicle from customer — always on) and Drop (return vehicle to customer — admin-toggleable, off by default). When Drop is disabled, its menu and forms are hidden on both web and mobile. * Request capture: registration/chassis or a linked vehicle, customer contact (existing CRM customer or quick ad-hoc name+mobile), preferred time, pickup/drop address, request source (phone, WhatsApp, app, email…), and notes. Each request gets a unique reference code. * Driver workflow with full status timeline: Requested → Assigned → Accepted → In Progress → Handover → (Return in Progress, for Drops) → Completed; can be Cancelled at any step with remarks. * Handover capture: odometer reading, fuel level (empty / quarter / half / three-quarter / full), and multiple photos/documents (vehicle-condition photos, insurance, other). Mobile photos are geo-tagged with location and timestamp. * Notifications: drivers are auto-notified on assignment and on handover completion. * Permissions & data scoping: view-all (admin), view-by-branch (managers/coordinators), view-own (drivers); plus create, edit (workflow transitions), assign, cancel, delete, export. The Driver role is auto-granted "own + workflow" access only. * Web management page under Services: filtering (branch, type, status, registration, driver, customer mobile, date range), sortable/customizable grid, statistics dashboard, CSV export, and a detail modal with history + attached documents. * Mobile app: dedicated list, request form, detail, and handover screens — drivers can accept, start journey, complete, cancel, and do photo/odometer/fuel handover on the go.

Field Service (web + mobile engineer app) Two new job statuses between Pending and Work-In-Progress: Assigned (purple) and Journey Started (sky blue). Pending↔Assigned flips automatically when an engineer is attached/detached — no manual "Assign" button. "Start Job" and "Mark On-Site" action buttons replace status names on the Assignment tab and appear as row-level icons on the Service Jobs list, so dispatchers can advance a job without opening the detail page. Cancel is now also allowed from the new in-between states. GPS trips are now automatic. Starting a journey opens an OUTBOUND trip; Mark On-Site finalises it with distance and duration. Same for the return leg (Going Home / Reached Home). Engineers no longer start/stop trips manually. Live engineer position on the trips map as a pulsing marker, polled every 15 s while a trip is active. Polling stops once all trips are finalised. Server-side geofence arrival detection: when GPS points are submitted, the backend tells the app whether the engineer is within the destination radius (default 100 m). Notify-only — Mark On-Site is still manual. Default GPS sampling relaxed from 15 s to 30 s. Full engineer workflow on mobile (net new): Service Job list, detail and form screens, plus tabs for Details, Customer, Assignment, Trips, Documents, Complaints, History and System Info. Mobile complaints CRUD mirrors web one-for-one. Android background GPS is now a native foreground service with a persistent "Trip in progress" notification. A Play-compliant Location Disclosure modal is shown before the OS permission prompt, explaining tracking only runs Start Job ↔ Mark On-Site and Going Home ↔ Reached Home. Declining still allows the status change. Documents tab — View Status dropdown: users can inspect documents collected at any prior lifecycle stage (read-only). Uploads/deletes still target only the current status. Customer picker on the Add/Edit Service Job modal switched to server-side typeahead (name / mobile / phone) instead of preloading every customer. Edited jobs seed the current customer so it renders immediately. A new /customers/search endpoint backs it. Engineers sub-tab inside Assignment is now permission-gated via service_jobs:view-tab-assignment-engineers (ADMIN only by default). Field Service Engineer role granted the missing pieces it needed in practice: vehicle-models:view (so the Machine Model dropdown isn't blank on edit) and service_job_complaints:create/edit (delete remains ADMIN). GET single job re-enforces view scope (all / branch / assigned) — engineers can no longer bypass list filtering by hitting a UUID directly. Dead requiresSupervisorApproval field removed from request/response/entity; Customer-ID filter removed from list (name + mobile filters cover the same ground). Replacement Handover (web + mobile)

1. Field Service — "Created By" / "Updated By" now show on Customer Machine grid The Customer Machine grid was leaving those columns blank because the batch fetch never joined the user-detail chain. Added the LEFT JOIN FETCH for both createdByUser and updatedByUser, so the grid and View modal now actually show who created/updated each record. Files: CustomerMachineRepository.java 2. Services — Service Vehicle stat tiles refresh after every workflow event Check-in, check-out, temp-out, temp-in, status updates, cancellation, approvals, and the boom-barrier webhook were only evicting statistics.serviceEntry. They now also evict statistics.serviceVehicle, so the Service Vehicles widget no longer shows stale counts after a vehicle moves through the workshop. 3. Pasco client — Hyundai Grand i10 (legacy BS4, 2013-2019) seeded Client-specific data seed for Pasco's True Value used-vehicle business. Adds the original pre-Nios Grand i10 model under NON_MARUTI, ten variants (Era / Magna / Sportz / Asta in petrol manual, plus AT and CRDi diesel trims), and remaps the existing Hyundai base colours. Distinct from the Grand i10 Nios already seeded earlier. Won't run on non-Pasco clients. File: V910171__pasco_hyundai_grand_i10_legacy.sql 4. Mobile — Walk-In Enquiry phone-search results redesigned The phone-number search results screen was rebuilt for tablet/large display. Each card now uses a coloured left border for entity type instead of a circular icon, an inline phone/location icon per meta row, a "matched on …" chip, monospace styling for the code, all driven by the responsive cardStyles so they scale correctly on phones and tablets. File: PhoneSearchResults.tsx

Field Service (the bulk of the work) Service Jobs grid was reshaped from "one row per job" to "one row per machine" (migration V80022). The /dashboard/field-service/jobs list now shows one row per customer_machines row with aggregate columns: totalJobs, latestCallId, latestJobDate, latestJobStatusName, latestBranchName, latestEngineerNames. Filters updated to machineNo, customerName, customerMobile, branchId, machineTypeId, status, createdAtFrom/To. Mirrors the Service Vehicles list pattern so dispatchers see machine history at a glance. Customer machines globally deduplicated (migration V80023, the one currently open in the IDE). Same physical machine is now ONE row keyed on machine_no — was previously duplicated per customer. Migration reassigns existing jobs from duplicate machine rows to the canonical (oldest) row and deletes orphans. Dropped uk_customer_machines_no(customer_id, machine_no), added uk_customer_machines_machine_no(machine_no). New CustomerMachineQueryService + CustomerMachineExportService added with 14 filter fields and full export support. Controller permission matrix now accepts service_jobs:view OR customer_machines:view. New "Field Service Engineer" role (migration V80018) for on-site technicians who only see jobs assigned to them. Granted: service_jobs:view + service_jobs:view:assigned (scoped via active service_job_assignments), service_jobs:edit, all tab-level perms, plus profile/documents/attendance/dashboard access. Lead-sharing perms auto-granted (shared_leads:create, view:created, view:assigned). Menus: Dashboard, My Pages, Field Service, Lead Sharing. Tab-level view permissions added to Service Jobs (migration V80016): service_jobs:view-tab-{details, customer, assignment, trips, complaints, documents, history, system}. Auto-granted to every role with the existing service_jobs:view on rollout so nothing breaks for current users. View-scope permission dependencies declared (migration V80017): service_jobs:view:all, view:branch, and view:assigned now all imply service_jobs:view. Export endpoint also rewritten to honor caller's view scope instead of being admin-only — empty-branch case returns zero results with proper stats (matches the Customer page behavior). Customer entry mode persisted on jobs (migration V80019). New customer_entry_mode column on service_jobs with values LINKED (picked from CRM) or ADHOC (typed name+mobile inline). Edit screen now defaults the radio button and pre-fills the inputs to the original choice — previously it would lose the original intent on edit. Service job attachments migrated to platform document storage (migrations V80020, V80021). service_job_attachments now links to platform documents via document_id FK. Replaces legacy local-disk FileStorageService with the canonical S3/R2 path used elsewhere (FuelFilling, Customer documents, UsedVehiclePurchase). Enables presigned-URL inline preview and DocumentGridView thumbnails. New FIELD_SERVICE document category seeded; attachments now live under /FIELD_SERVICE/{callId}/FIELD_SERVICE/ in Document Explorer. file_url made nullable for legacy rows.

1. Replaced Ola Maps with Google Maps (commit e664cdb75 — "removed ola map and replaced with google map") The platform's map picker no longer uses Ola Maps anywhere. platform/frontend/src/components/common/GoogleMapPicker.tsx — now accepts an initialAddress prop (addressLine1, city, state, country, postalCode). When the picker opens and no lat/lng is supplied, it auto-geocodes the address through geocodingService, drops the pin at the resolved coordinates, and shows a "Locating address..." spinner while it works. platform/frontend/src/middleware.ts — Content-Security-Policy connect-src whitelist trimmed: https://api.olamaps.io and https://*.olamaps.io removed, only https://maps.googleapis.com remains. Comments mentioning Ola Maps workers/blobs were cleaned out. platform/frontend/package.json / package-lock.json bumped to drop the Ola SDK dependency. mobile/.env.example and mobile/android/app/build.gradle no longer carry Ola keys/config. All four mobile client configs (mobile/clients/logix/, pasco/, platinum/, vehicron/ config.json) were updated to remove Ola configuration. 2. Field Service – Documents tab rewritten (commit 227ba562f — "field service 22") The Service Job "Documents" tab was redesigned to mirror the accessories IssuanceDocumentUploadSection pattern instead of the old generic upload grid. field-service/frontend/src/components/serviceJobs/tabs/ServiceJobDocumentsTab.tsx — removed the dropdown/caption/drag-zone uploader. Now renders one card per document TYPE that the catalog defines for the current job status. Each card has a "+" button that triggers a file input scoped to that type, mandatory types show a "Mandatory" pill, empty types render a dashed "Click to upload" placeholder. A new client-side catalog file field-service/frontend/src/types/serviceJobDocumentTypes.ts defines the stages. Backend: ServiceJobAttachment entity, ServiceJobAttachmentResponse, mapper and service learned a new documentType (code-level) field; migration V80009__Create_service_job_attachments.sql got the new column. The new field is also surfaced in serviceJobAttachmentApi.ts and the request flows from the page into the new uploader. Controller signature: ServiceJobAttachmentController accepts the new documentType parameter. 3. Field Service – Server-driven document catalog (commit 3bf6988da — "field service 23") The hard-coded catalog from the previous commit was lifted to the backend so web and mobile share one source of truth. New file field-service/backend/src/main/java/ai/fieldservice/service/ServiceJobDocumentTypeCatalog.java — defines per-status document types (PENDING → Arrival Photo + Job Authorization, WORK_IN_PROGRESS → Work Photo + Parts Photo + Materials Checklist, WORK_COMPLETE → Completion Photo + Work Report + Checklist, GOING_HOME / REACHED_HOME / GOING_OFFICE / REACHED_OFFICE → Odometer Photo, DONE → Customer Signature + Invoice, CANCELLED → Cancellation Reason). Each stage carries a mandatoryCodes list (WORK_PHOTO, COMPLETION_PHOTO, CUSTOMER_SIGNATURE, CANCELLATION_REASON). New DTO ServiceJobDocumentStageResponse exposes statusCode, category, types, mandatoryCodes.

1. Field Service — smarter Documents tab on a job (part 1) Until now, when an engineer opened the Documents tab on a service job, they just saw one big generic Upload button. They had no idea which documents they were supposed to collect at the current stage. This change turns the Documents tab into a set of clearly-labelled cards that depend on the job's current status: When the job is Pending (engineer just arrived) → cards for "Arrival Photo" and "Job Authorization". When Work in Progress → cards for "Work Photo", "Parts Photo", "Materials Checklist", with "Work Photo" marked as Mandatory in red. When Awaiting Approval → an "Approval Email" card, marked Mandatory. When On Hold → an "On-Hold Reason" card, Mandatory. When Work Complete → "Completion Photo" (Mandatory), "Work Report", "Completion Checklist". During the return-leg statuses (Going Home / Reached Home / Going Office / Reached Office) → an "Odometer Photo" card. When Done / closing out → "Customer Signature" (Mandatory) and "Invoice". When Cancelled → a "Cancellation Reason" card, Mandatory. Each card is its own bucket — anything uploaded to the "Work Photo" card is stored against that type, so later we can show exactly which photo is which. 2. Field Service — same Documents catalogue, now shared with mobile (part 2) The list above (which documents go with which status, and which are mandatory) was initially hardcoded into the web app only. That meant the mobile app couldn't show the same cards. This change moves that list to the server so both web and mobile read from the same place. If we ever need to add a new document type or mark one as mandatory, it's a one-line change on the server and both apps pick it up automatically. One small behaviour tweak that came out of this: statuses like "Awaiting Parts", "Awaiting Payment" and "Awaiting Customer" now correctly show an empty state ("No documents are collected at this status") rather than reusing the in-progress card set. 3. Mobile — fixed the "stuck loading spinner" on document previews (part 1 of three) On the mobile app, when you tapped a document to preview it, the loading spinner would sometimes stay on the screen forever even though the document had already loaded behind it. This was tracked down to a timing issue between how images are cached and how the preview modal initialises itself. It's been fixed. At the same time, the Customer → Documents tab was switched to a faster path for downloading and viewing documents: instead of asking our own server for each file (which makes it the middle-man), the app now asks the server for a short-lived direct link to the file and downloads it straight from cloud storage. Faster, less load on our backend. 4. Mobile — same speed-up rolled out everywhere else (part 2) The same direct-link conversion was applied to every other place on mobile that shows document thumbnails or downloads: Customer Feedback attachments PDI (pre-delivery inspection) movement documents PL Request comments (the attachments inside each comment) Accessory Sales Order documents (in both the Customer view and the Accessory Quotation view) The shared "Item Documents" section used by accessory orders In all of these, image thumbnails now stream directly from cloud storage. PDF thumbnails were temporarily shown as a plain red PDF icon — see the next item for what came next. 5. Mobile — brought back real PDF thumbnails, the proper way The plain red PDF icon from item #4 was just a stopgap. This change restores actual first-page previews for PDFs everywhere on mobile (Customer Documents, Feedback, PDI Movements, PL Request comments, and the shared Item Documents section). The new implementation renders the first page of the PDF using a hidden web view, then caches the resulting image in memory — so if you scroll past the same PDF twice, the second time is instant. And because it uses the same direct-link cloud storage path as the images, it's still fast and doesn't go through our backend.

A brand-new module: Field Service We built an entire new section of the app for handling on-site service jobs (think: engineer goes to a customer's site to fix their machine). You can now keep a record of every machine each customer owns ("installed base"). When a customer calls in with a problem, you create a Service Job for that machine. It moves through proper statuses (open → assigned → in progress → closed) so nothing gets lost. A job can have more than one engineer assigned to it, and each engineer accepts their own assignment from their phone. The customer's complaints are tracked as a list against the job (not just one free-text field), so you can mark each one as resolved separately. Engineers can upload photos and documents against the job (before/after photos, signed worksheets, etc.). Every change to the job is recorded as a history/activity stream — you can see who did what, when. The job detail screen is laid out in tabs: Details, Customer, Engineers, Complaints, Documents, History, Trips, System info. There's a "Phase 2" placeholder visible on the page — parts, spares, and billing are the next chunk of work. We also imported the customer's old machine-type and call-type lists so their existing data lines up with the new system. An earlier "checklist" idea we'd started on got dropped — the activity/attachments approach replaced it. File storage is no longer tied to AWS Behind the scenes everything that said "S3" has been renamed to "Object Storage." The app no longer assumes Amazon — it works with any S3-compatible storage (MinIO, etc.). This was a big internal rename but you shouldn't see any difference as a user. The Storage tab that used to be on the Admin Settings page was removed because those settings moved elsewhere. Bigger control over who can see what PDI vehicles The "view PDI vehicles" permission now has three levels instead of one: View all — admin-style, sees everything. View branch — sees PDI vehicles for the branches the user is assigned to. View (plain) — sees only PDI vehicles created by the user themselves and their subordinates. Existing roles weren't broken — anyone who currently had "view" was automatically bumped to "view branch" so what they see stays the same. Admin and Auditor were given "view all." The Evaluator PDI role intentionally dropped to the strictest level so evaluators only see their own work. Other PDI improvements: You can now filter PDI movements by registration number on the grid. The PDI In-charge role can now pick a driver when creating a movement (a small permission gap that was blocking them). New setting: when a used-vehicle purchase is completed, the system can optionally notify everyone at the destination yard by push / email / WhatsApp. Off by default — you turn it on per dealership. On mobile, the PDI vehicle and movement cards got several rounds of polish (cleaner layout, proper translations in English / French / Hindi). New "Visitor" role A receptionist-style role that can only create walk-in enquiries — they can't see the list, can't edit, can't delete, can't export. Built specifically for front-desk staff who hand customers off to a salesperson. Unlike most roles, this one is not a system role, so dealers can edit or delete it.