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.

A whole new "Field Service" section has been added This is the headline change. Before, there was no field-service area at all. Now you have a complete new section in the app with two main pages:

Dealer module Customers — auto-create empty delivery When a customer is created with a branch assigned, the system now auto-creates an empty CustomerDelivery (no vehicle, expected date = today+7, contact details copied from customer). The user can later assign a chassis from the "Choose Vehicle" tab. Shares the customer-create transaction — delivery failure rolls the customer back. Customers — page restructure The standalone "Addresses" tab was folded into the Details tab as a sub-tab (web + mobile). Updated the tab order, first-visible-tab logic, sub-tab permission map, and address Edit/View embedding. The "Create Multiple Deliveries" button no longer requires the customer to have zero deliveries — visible regardless (web + mobile). Choose Vehicle tab cleaned up — small consistency tweaks across web and mobile. Batch quotation copy now also requires that the source delivery actually has a quotation linked — backend was rejecting it without the new gate (web + mobile + form screen). Customers — chassis/registration on grid Two new filters on the customers grid: Chassis Number and Registration Number, sourced from customer_delivery → pdi_vehicles → vehicles (V20771). Two new visible columns for the same values, inserted right after Customer Name (V20772). default_columns updated in grid_preferences. CustomerFilter (web component) extended with the two fields; CustomerResponse carries chassisNumber/registrationNumber; CustomerFilter (backend DTO) wires them through to the repository; export columns include them too. filterUtils.ts allowlist extended. Mobile parity: CustomerCard now shows chassis + vehicle registration as meta rows when present. EntityCard gained metaTextNumberOfLines and metaItemMaxWidth props so long values (full user name + employee code) can wrap rather than be truncated. Used Vehicle Purchases — 3-tier access control (V20773) UsedVehiclePurchaseController now mirrors CustomerController's 3-tier scheme: view:all → admin (no filter), view:branch → branch scope, neither → hierarchy mode filter by created_by (user + subordinates). Previously, users without either branch/all view got an empty result. Repository / QueryService / Service signatures threaded a new currentUserId for hierarchy filtering. V20773 revokes used-vehicle-purchases:view:branch from the Evaluator role — product decision: evaluators should fall back to hierarchy mode and only see their own / their subordinates' purchases, not all purchases across their branches. PDI Transit Notifications — multi-branch yards + OEM Approved When a movement targets a yard mapped to multiple branches, notifications now fan out to active users with pdi-vehicle:receive on any of those branches (uses the new findActiveUsersByPermissionAndBranchIds). Added a new notification type: PDI_OEM_TRANSIT_APPROVED. PdiVehicleMovementService wired through the new flows. PdiMovementModal — explicit movement-type selection Removed the auto-default YARD_TO_BRANCH / BRANCH destination type — when source location resolves, only sourceType is pre-filled and the user must explicitly pick movementType and destinationType. Web + mobile + types + i18n all updated. Same fix in mobile PdiMovementFormScreen + pdiMovementForm types.

Platform — the foundation pieces. We added an HTML sanitizer on the backend so anything coming out of the new rich-text editor gets washed through an allow-list before it hits the database. It strips script tags, on-click handlers, inline styles, iframes — the usual XSS surface. Product Lift uses it on changelog entries, request descriptions, and comments. We pinned an "India timezone" constant in DateUtils so anyone parsing a Maruti DMS feed doesn't accidentally pick up whatever timezone the scheduler user has set. The Maruti workshop-invoice mapper now uses it. The notification delivery service was building a JSON string by hand-concatenating quotes — which broke the moment an SMS provider sent back a response containing a quote. That's now a proper Jackson writeValueAsString.

What changed between v2.4.8 and the current main Two releases shipped on top of v2.4.8 — v2.4.9 and v2.4.10. Below is everything that actually went into them, told plainly. I've left out warehouse, supply-chain-core, and assets work as you asked. Pasco data clean-ups User names fixed. A lot of Pasco users had been seeded entirely in capitals (SHIV, CHAWLA, AZAD ANSARI). A migration now converts those to proper Title Case (Shiv, Chawla, Azad Ansari). Safe to re-run — it only touches names that are still all-caps. Service entries de-duped. The earlier bulk upload had created multiple SE-UPLOAD entries for the same vehicle on the same check-in date. The duplicates are now removed, with related bodyshop-conversion-request rows repointed to the surviving entry so the INTERESTED / NOT INTERESTED status and follow-ups are preserved. Strictly scoped to SE-UPLOAD rows — nothing else can be touched, and the migration fails fast if anything outside that scope slips in. Vehicle "active" state realigned. The same upload had marked every uploaded vehicle as Active even though their entries were all Checked Out, so the management table was showing an Edit button on long-finished historical rows. Two passes correct this — first using the same "is there an active entry?" rule the backend uses, then a second pass for ~3,755 vehicles that had a hanging phantom CHECKED_IN entry followed by a newer CHECKED_OUT (those are now marked Inactive too). Bulk-imported True Value used cars. 106 used cars from the customer-supplied digital stock report are now seeded under Pasco's PASCO SEC-18 branch with proper company / model / variant / colour lookups. Transmission (Manual / Automatic / AMT / CVT / DCT) and body type (Hatchback / Sedan / SUV / MPV) are derived from the model text. 12 of the 118 rows were skipped because their model didn't exist in the master. updated_at reset to created_at on the touched historic rows, because the earlier migrations had bumped updated_at = NOW() and floated tens of thousands of old rows to the top of the Service Vehicles and Bodyshop Conversions grids (both default-sort by updated_at DESC). Pasco flow toggles configured: Skip PDI Delivery Approval for used vehicles → enabled. Delivery Dispatch Gatekeeper Required → enabled. Required PDI Incharge role for Used Vehicle Dispatch → disabled (used-vehicle deliveries auto-dispatch at final approval). Allow Document Operations After Delivered for used vehicles → enabled (uploads / verification stay editable after DELIVERED). Grid behaviour — sorting, modified indicator, page size These are improvements that touch nearly every management page across dealer, automotive, accessories, services, insurance, platform, and product-lift. Header-click sort is now remembered. Click a column header to sort, refresh the page — your sort is still there. Previously only the Grid Config modal saved sort. Clearing sort (third click) clears the saved sort too. The little "modified" marker on the Grid Config button is now honest. It used to light up the moment any user-preference row existed, so after you clicked "Clear filters" it stayed orange forever. Now it lights up only when your saved preference actually differs from the system defaults — visible columns, column order, page size, sort, active filters, column widths. Reset Preferences fully unwinds. When you reset preferences from the modal, the filter strip now snaps back to the configured defaults instead of leaving stale values on screen. Page-size changes from preferences now actually apply. A one-shot initialisation guard was making post-load page-size changes inert; that's fixed. Duplicate save removed. Saving from the Grid Config modal used to fire two POSTs with a race between them; the redundant one is gone.

Display Vehicles You can now create a Lead directly from a Display Vehicle row. A new green "Lead" button shows up next to the QR button on each active display vehicle. Clicking it opens the Add Lead form with the branch, company, model, variant, and color already filled in from that vehicle, and Lead Source Type pre-set to "Event". Works the same way on mobile. The "Pick a vehicle" dropdown is smarter now. When adding a display vehicle, the dropdown only shows vehicles that are actually in stock or moving between locations. Vehicles that are sold, delivered, or stuck in OEM transit are hidden. If you're editing an existing display vehicle, the one already selected stays in the list even if its status would normally hide it — so you don't lose your selection. Display Vehicle PDFs and QR codes now carry the company logo. The QR code printed on the brochure has the OEM logo (Maruti, Mahindra, etc.) sitting in the centre, with the platform's app logo as a fallback if no company logo is uploaded. PDF brochures use the same logo handling. Brochure PDFs use Helvetica instead of Times Roman. Looks cleaner, especially on screens. Sales — New "Sales Lead Performance" Hub A whole new analytics section under Retail → Sales → Sales Lead Performance. It groups every lead-related report into one tile-based dashboard: Lead Pipeline — Cold (0–30) / Warm (31–70) / Hot (71–100) breakdown Monthly Trend — lead volume + average score month over month\

OEM Sync (auto-fetching data from car manufacturers) New "Web URL" connection type. Earlier you could only connect to S3 or SFTP. You can now also point at a regular web folder (HTTP/HTTPS), with optional username/password. "Run Now" button finally works for slow connections. Before, hitting Run Now on a slow source would silently time out and you'd never see the success message. Fixed. Start From Date. When you set up a new connection, you can now tell it "start syncing from this date" so it doesn't pull years of old files. It will never accidentally re-pull stuff you've already synced. Minimum sync interval raised from 1 minute to 2 minutes. One-minute polling was hammering the system and leaving no breathing room. Two minutes is the new floor. The sync no longer hogs the server. It now stops itself after 500 files in a single tick (the rest roll to the next tick), and any single file over 20 MB is rejected instead of crashing memory. So users browsing the app won't get slowed down by a heavy sync. "Records in File" page got a View button. Each row now has an eye icon that opens a clean detail popup with a "Full Error" tab — handy for reading long error stacks without the row getting cut off. Maruti new-vehicle GRN feed is live. Maruti's "VP" files (new vehicles arriving from the factory) now flow straight into the system as OEM-Transit movements, exactly as if you'd uploaded the Excel manually. Used Vehicle Purchase Three new columns on the list: Ex-Showroom Price Total Refurbishment Cost Delivery Status (shows when the used vehicle has been re-sold) All three are also in the CSV export. Condition tab now saves in two parts. "Condition Overview" (odometer, notes) and "Accident History" (count, description) are now separate save buttons — so saving one doesn't accidentally wipe unsaved changes in the other. Insurance company / policy number / bank name now check the format too, not just the length. Fuel type: added LPG, Petrol+CNG, and Petrol+Hybrid (these used to be rejected). Body type: locked to a fixed list (Sedan, Hatchback, SUV, MUV, Coupe, Convertible, Wagon, Van, Truck, Other). Number of owners: maximum dropped from 10 to 4. Mobile card redesigned. Now shows Purchase Date and Total Refurbishment Cost, swaps the price badge for "Ex" (Ex-Showroom), and adds a Delivery Status badge when the vehicle has been re-sold. The colored stripe on the left also reflects the delivery status. Vehicle Status page (the vehicle desk grid) The "Vehicle Status" filter actually works for all values now. It used to silently ignore options like "Final Delivery Dispatch", "Ready For Delivery", "At Yard", "Returned", and "Blocked" — even though those values were visible in the column. Now you can filter by any of them. Existing user grid customizations are migrated automatically. All filters are now searchable (model, variant, status, branch, yard, etc.) — type to filter the dropdown instead of scrolling. Mobile: added "Final Delivery Dispatch" to the status filter (was missing) and a new Movement Status filter that matches the web version. Customer Documents Upload happens right where the document goes. Before, you'd click "Upload Documents" and the whole section would switch to a separate upload screen. Now each document type card has its own upload button — click the one you need, pick the file, done. No more leaving the page. PDI Quality Status (web + mobile) "Status Notes" textarea removed. Users were confused about the difference between Status Notes and Status Reason; the notes field wasn't being used meaningfully, so it's gone. "Pending" removed from the dropdown. Pending is the starting state — there's no reason to manually set something back to Pending. Only Passed and Not Required are now selectable. Vehicron client (Vehicron-only data setup) Five new seed scripts that only run for Vehicron's deployment:

Used Vehicle handling (the biggest set of changes) Quality check is now skipped automatically for used vehicles. Earlier, every used vehicle still showed "Quality Pending" on the PDI inventory and on the customer delivery page, and someone had to manually mark it Passed before dispatch. Now the system marks it as "Not Required" on its own — both when the used vehicle is created in PDI, and when it's attached to a customer delivery. Dispatch is no longer blocked. There's a new global setting under Global Settings → Dealer → PDI to turn this off if needed (it's ON by default). Documents stay editable on used-vehicle deliveries even after the vehicle is delivered. For used-vehicle deals, after the delivery status becomes "Delivered" you can still upload missing documents, verify them, reject them, or resubmit a rejected one. The delivery status itself does not regress — it stays at "Delivered". For brand-new vehicles, documents become read-only after delivery as before. Controlled by a new global setting under Global Settings → Dealer → Customer (ON by default). The same vehicle can now have multiple in-progress quotations. Earlier, the moment any quotation/delivery was started for a vehicle, that vehicle disappeared from the dropdowns and chassis search for everyone else, even if the deal was just a draft. Now the vehicle only gets locked once a deal actually reaches "Sold" or beyond. Drafts, pending, approved, ready-for-delivery — none of these block other people from raising a quotation on the same vehicle. Customer page New "Mark Sold at Branch" button added on the customer Delivery tab (purple). It's a manual fallback that appears only when the vehicle has already been received at a branch, all PDI approvals are done, but the auto-mark-sold did not happen at receive time. Earlier we only had "Mark Sold at Yard" — this is the matching button for branch deliveries. Available on both web and mobile. Expected Delivery Date on the Choose Vehicle tab now defaults to one week from today instead of today's date. Same on web and mobile. Cleaner error messages while saving a quotation. When the quotation save fails because of validation, you'll now see the actual reason (e.g. "phone: must be 10 digits") instead of just "Validation failed". Block on saving a zero-price item. If an item's ex-showroom or offer price is zero, the page now stops you with a clear message — "Item 1: Ex-showroom price is zero. Please set the correct price for this variant at the selected branch before saving." — instead of letting it go to the backend and bouncing back with a generic error. Same on web and mobile. Quotation tab auto-adds the first item for you on the customer page. You don't have to click "Add Item" once before you start filling things in.

Filter system rewrite — every list page got rebuilt This is by far the biggest change in this release. Almost every list/management page in platform admin, dealer, automotive, accessories, services, insurance, lead sharing, product lift, and the mobile app was rebuilt to use a single new filter hook. What used to happen: every page had its own little pile of plumbing — one chunk read URL query parameters on first render to pre-fill filter values, another chunk kept a separate copy of those values in component state, and grid preferences (visible columns, column order, page size) lived in a third hook. The three didn't talk to each other cleanly, which led to subtle bugs — pagination not resetting on filter apply, URL params not surviving a reload, applied vs. live filter values getting out of sync. What happens now: one hook owns all of it. It holds the live form values, the last-applied values, the apply/reset/setFilters callbacks, the column and filter visibility, the page size, and the URL-parameter parsing. Pages just hand it an initial filter shape, a filter scope (so the allowlist is enforced), and small callbacks to reset pagination on apply or clear. Roughly: Platform admin — branches, branch staff, delegations, designations, feedback branch config, feedback categories, feedback sub-categories, groups, lead source types, menu management, permissions, report executions, roles, scheduled report config, users. Dealer — addresses, branch pricing, branch stock, current branch transit, current internal transit, current OEM transit, current PDI stock, customer document types, customers, customer feedback, display vehicles, drivers, leads, new transit request, partnerships, all six PDI movement child pages (approvals, costs, damages, documents, inspections, timelines), PDI movements, PDI stock yard employee assignments, PDI stock yards, PDI vehicles, pricing components, quotations, return to PDI, supplier drivers, used vehicle evaluations, used vehicle purchases, vehicle desk vehicle status, vehicle pricing, walk-in enquiries. Automotive — companies, customer drops, fuel fillings, internal vehicles, OEM connections, OEMs, test drives, vehicle classes, vehicle colors, vehicle models, vehicle types, vehicle variants. Accessories — branch pricing, categories, customers, inventory, inventory counts, manufacturers, price types, products, quotations, returns, stock adjustments, stock receipts, stock receipt imports, stock transfers, storage bins, sub-categories, units of measure, vehicle compatibility, warehouses, and all report pages (category performance, insufficient stock, inventory valuation, low stock, return analysis, sales summary, slow moving, stock movement, stock summary, top selling, warehouse utilization). Services — bodyshop conversions, feedback, replacement handovers, service vehicles. Insurance — leads. Lead sharing — shared leads.

Dms 34 — Added 16 flat office_* / shipping_* columns on customers so the Maruti sync no longer needs the polymorphic addresses table for those two address types. Mapper now copies office/shipping fields onto new customers, and only inserts a residential addresses row when we actually create the customer (so retries don't overwrite address history of customers we didn't make). Dms 35 — Created a permanent "Scheduler" system user (login disabled, fixed UUID ffff…0001) so every audited write the OEM scheduler does has a stable created_by/updated_by. Wired this user into Maruti INSERT/UPDATEs for customers, addresses, service_vehicles, service_entries, body_shop_entries. Also fixed an INSERT that was writing a non-existent customers.status column. Dms 36 — When the mapper creates/updates a service_vehicles row, it now passes the resolved customer ID through. Without it, the CHECK constraint (need at least one of customer_id / customer_name / customer_mobile) was failing. Dms 37 — On manual file retry from the OEM Sync UI, the engine now EntityManager.clear()s after rewinding the connection's last-synced slot. The L1 cache was holding the pre-rewind connection entity, so retries were no-ops. Dms 38 — Mobile is written to primary_mobile (matches the manual customer-create flow), not primary_phone. Vehicle inserts/updates now also denormalise customer_name and customer_mobile so they show up correctly on the Service Vehicles UI. Dms 39 — Added an OEM Code field on Vehicle Models and Vehicle Variants (entity, DTO, mapper, modal inputs, migration V10074) so OEM payloads can match against the OEM-supplied code when our internal code differs. Also added a new /oem-sync-runs/export endpoint with proper export service so users can download OEM sync run history. Dms 40 — Added explicit CAST(? AS BIGINT) on the Maruti UPDATEs because Postgres couldn't infer the type of standalone ? IS NULL parameters once enough COALESCE-NULL placeholders preceded them ("could not determine data type of parameter $N"). Dms 41 — Mapper now persists gstin on the customer (from gst_NUM), and on service_entries writes job_card_number (from trans_REF_NUM) and invoice_date (from trans_REF_DATE). Dms 42 — In the OEM Sync Runs/Files panes, "Failed" counts go bold red when > 0, and the partial/failure row tint moved from amber to a more saturated orange so failures stand out. Dms 43 — Started/Finished timestamps on those tables now show date and time (previously date-only). Dms 44 — Added branch_id on oem_sync_files (V10075). Mapper stamps the resolved branch on the file the first time it processes any record from that file. New column in the OEM Sync Files pane shows it. So operators can see which dealership branch each sync file belonged to. Dms 45 — On the Service Vehicles screen's "Change Service/Bodyshop" entry selector, moved the label from a floating-label-inside-Select to a side label, giving the dropdown more horizontal room. Dms 46 — Added a brand-new MarutiVsMapper for Vehicle Sale (VS) records on the dealer side. Mirrors the customer-master "create customer" flow at /dealers/customers: inserts customers (INDIVIDUAL) + customer_individuals + a residential addresses row. INSERT-only — never overwrites already-linked customers. Dms 47 — Fixed the SFTP container's USERS spec so the dms user's home is upload, so OEM files actually land in the expected folder. Dms 48 — Maruti dealer mapper now splits the two payload mobiles correctly (mobile2 → primary_mobile, mobile1 → alternate_phone, res_PHONE → primary_phone). Anniversary date (doa) now persists on customer_individuals.date_of_anniversary. Address line1/line2 now include village/tehsil (comma-appended, capped at 255 chars). Dms 49 — Major rewrite: Maruti VS mapper now also upserts a customer_delivery row alongside the customer. VIN looks up the