2026-10-18
- Bookings: Physical Register Page Code (
2026OCT18PG1) on the Daily Approved Visa Manifest — approved visas now carry a dynamic page code in the format<yyyy><MMM><dd>PG<pageNumber>(e.g.2026OCT18PG1,2026OCT18PG2), generated byVisaShortCodeHelper.generateSigningPageCodeand computed in-memory from the approval day (Asia/Colombo) and approval order — 8 rows per page to match the physical register sheets, with no database column or migration. Visa only; flights are untouched.DailyApprovedVisaPdfServiceprints the code prominently in the top-right of every manifest page and again as a greyed-out badge and watermark line in the footer, and the redundant per-rowSigning Pagecolumn was dropped in favour of a clean 8-column table (the Custody & Handover footer is now a bordered card). The code is exposed onVisaResponseDTO.signingPageCode, shown as aSigning Page: 2026OCT18PG1badge inTaskDetailDrawerand as a Passport Handover Register Page card inVisaDetailPanel, so front-desk staff can pull the right signature sheet without searching. - Bookings: Outdated Ticket Departure Warning Indicator —
FlightRequestRepositoryevaluatesisTicketOutdated/ticketDaysOutdateddirectly in the JPQL projection (flightDate < :now, status notCANCELLED/TICKETED, not finalised) rather than in the service layer. The icon is hidden only when the ticket is issued and payments are fully settled; unpaid, partial or un-invoiced tickets keep showing it.TaskListView,AdminTaskTableandFlightDetailPanelrender a compact amberInfoicon with a tooltip showing the departure date and days overdue, driven straight from the backend flag with no client-side rule duplication.
Last updated on