- Enviado
- 7 de novembro de 2026 às 23:37 UTC
- Autor
- Kamo
- Confirmação
- 5da3b2b
The Rental and Procurement pipeline screens were mock data and their New pages were Coming Soon placeholders. They now read and write SecurityService: - Rental Requests, Bookings, Purchase Requests and Vendor Orders lists read /pos/rental-requests, /bookings, /purchase-requests and /vendor-orders, with an Account column, status words instead of codes, and plain empty states. Procurement switches between requests and vendor orders. - /commerce/bookings/new creates a rental request (asset, dates, rate type, estimate worked out the way the server does, optional customer account); /commerce/procurement/new creates a purchase request (vendor id sent as a string, never Number()). Both read ?accountId, ?marketId and carry ?back. - Record pages show only what the DTOs carry, keep Confirm Booking and Approve, and let a manager file the record under an account (PUT .../account) or take it off one. - Lists open records with withReturn; every rental New goes to /commerce/bookings/new (the old /commerce/requests/new never existed). - posApi types now match RentalRequestDTO, BookingDTO, PurchaseRequestDTO and VendorOrderDTO, including accountUid / accountName.