Wednesday, January 3, 2024
4 changes · 17.0
Enhancements to existing features
This update improves the performance of Odoo's messaging features by reducing unnecessary internal tracking work in JavaScript records. Users should see smoother mail and chat interactions, especially when loading or updating larger conversations and channel member lists.
Original PR description
The goal is to remove unnecessary usage of the reactive proxy. See individual commits for more details.
The Point of Sale interface is easier for restaurant staff to use, with clearer table navigation, longer idle time before closing tables, visible order-line attributes, and safeguards against moving orders to tables already in use. These changes reduce confusion during service and help prevent operational mistakes.
Original PR description
This commit presents UI improvements: Renamed the back button to "Change Table." Increased idle table closure time from 1 minute to 3 minutes. Implemented a restriction preventing users from transferring orders to tables already in use. Displayed the attributes of an order line in the order widget. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The scheduled cleanup job now runs with higher priority so it is less likely to be blocked by other failing background tasks. This helps prevent old temporary data from accumulating, reducing the risk of database growth and performance slowdowns.
Original PR description
There are various cases where we observe crons which systematically face a CPU / memory limit. In a setup where a single worker cron is launched, a failing cron will prevent subsequent crons to run. This happens because the limits are evaluated at the worker level: the worker is killed, then it starts over with the same job order. If the vacuum cron cannot be run anymore, it leads to tables not garbage collected anymore (e.g. `bus_bus`), causing performance issues. To avoid this, we give a higher priority to the vacuum cron. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Administrators can now delete approval requests, whereas previously only officers could delete their own approvals. The system was updated to remove product-related restrictions that prevented deletion, making the approval process more flexible for administrators managing the workflow.
Original PR description
Make basic rights for administrator to gives them permissions to delete approval requests before it was limited to the domain for officer (i.e. only your own approval). The products was also preventing the deletion of the approvals thus the unlink method had to be rewritten to make it possible. task-3463942 Forward-Port-Of: odoo/enterprise#51966 Forward-Port-Of: odoo/enterprise#51002