Monday, June 16, 2025
4 changes · saas-18.2
Resolved issues and error corrections
The purchase dashboard now labels the Not Acknowledged and Late Receipt tooltip counts as purchase orders instead of requests for quotation. This avoids confusion for users because these indicators track confirmed purchase orders, not RFQs.
Original PR description
**Steps to reproduce:** - Purchase Order > Dashboard > hover on not acknowledged, late receipt and their counts **Issue:** - Tool tips of 'not acknowledged' and 'late receipt' mentions RFQ's instead of PO's. These two kpi are related with PO and filter only Purchase Orders not RFQ's **Solution:** - Update the title of divs to 'POs' opw-4848307
This fixes an issue where Point of Sale guided demo tours failed because their required files loaded in the wrong order. The change helps keep POS demos and automated walkthroughs reliable for training, testing, and demonstrations.
Original PR description
Fake tours were not working in the Point of Sale app because thier assets were loaded before the global assets. This commit ensures that the fake tours are loaded after globals one.
This fix prevents unnecessary warning messages when creating Australian payroll accounting reports in a database without demo data. It ensures the report calculation waits until the related report information is ready, keeping system logs cleaner without changing user-facing payroll behavior.
Original PR description
[FIX] l10n_au_hr_payroll_account: avoid NewId warning in compute steps to reproduce: 1.install l10n_au_hr_payroll_account 2. without demo data 3. run the test test_form_new_record The compute method was being triggered too early, while the record still had a temporary NewId and not a real database ID. This caused a warning when using the field in a domain: Domains don't support NewId. We added a dependency on previous_report_id to make sure the compute only runs after the field is set and the record is saved. This avoids the warning and keeps the logs clean. build_error-115303
This update fixes a small issue in the Urban Piper point of sale integration where the delivery button was missing an expected setup value. It helps prevent potential errors when using delivery-related actions in the point of sale.
Original PR description
Before this commut, the static props of delivery_button was not defined. This commit adds empty static props to the DeliveryButton component.