Thursday, May 15, 2025
5 changes · saas-18.3
Resolved issues and error corrections
The AI chat button is now hidden in Documents folder views where there is no specific record for the chat to reference. This prevents users from encountering an error when opening the chatter and clicking the AI button in that context.
Original PR description
How to reproduce: - Open Documents, go into a folder - Open its chatter, click on the AI btn Current behavior: - Traceback: https://pastebin.com/kyCq2yBE Solution: The AI chat requires a record but when opening a folder in the Documents app, there is no record to refer to, resulting to an error. As a fix, we won't show the AI button in case of missing record. Task-ID: 4796869
Kiosk mode now sends the required authorization information when communicating with IoT devices, so actions such as receipt printing are accepted by the IoT Box. The fix also resolves a payment terminal error that could appear after a payment was approved or cancelled.
Original PR description
Kiosk mode didn't sign the request headers with "Authorisation" needed by the IoT to execute actions like printing. This PR fixes it along with an error caused by the refactoring PR https://github.com/odoo/odoo/pull/186359 To reproduce the authorisation issue: connect a kiosk with an iot box + printer, then make a payment. The printing would never be done because no "authorization" is sent in the headers, so the IoT Box refuses to execute the action To reproduce the bug linked to the refactoring: connect an iot terminal (tested with Worldline) then try to make a payment. A traceback appears upon payment approval or cancellation task-4794798
This fix prevents barcode kanban screens from crashing when background requests finish after a user has left the page. It also groups independent data requests together, improving reliability for stock barcode and batch picking workflows.
Original PR description
… condition In JS, rpc is not a service anymore so it will return no matter if the component is already destroyed. In turn, the orm service is protected, so if it is passed it will crash. After this commit, we prevent this race condition and we batch calls that are independant from one another. runbot-error-190605
This fix prevents crashes when viewing document folder details with aliases enabled, especially in debug or read-only views. It also improves how activity assignees, alias spacing, and cleared domain fields appear, making the Documents details panel more reliable and consistent for users.
Original PR description
1. Configure aliases 2. Open documents in debug mode 3. Select or enter a folder 4. Open details panel (Info & Tags) 5. See crash Without debug mode in readonly, you'll see "Activity assigned to" instead of "No activity assignee". Also fixes * domain field disappearing if cleared * irregular spacing of alias in readonly * filtered props passed to the Many2OneField (see related COM PR) Tests are not exhaustive but expanded to increase coverage of alias fields and `isContainer` 'fake' records. Follow up of 4724349 Task-4749289
Manual tax-related returns now run their validation checks immediately when created, instead of waiting for a page refresh. The checks screen also shows a name that matches the return type, reducing confusion for users handling different return processes.
Original PR description
Before this commit: When we would create return manually for instance: Ec sales and intrastat, the checks would not run automatically since they only run on page refresh. The fix here is to run these checks on creation of the return. Another fix is the display name of the checks view. It was always 'VAT Return Checks' which is wrong. Now we base the view name on the return type name. task-4783937