Daily updates from Odoo
Wednesday, June 4, 2025
5 changes
1 change
Enhancements to existing features
Belgian point-of-sale systems can now fall back to a websocket connection when the usual longpolling connection to the blackbox is unavailable. This temporary improvement helps keep fiscal device communication more reliable until the newer IoT HTTP service replaces it in a later version.
Original PR description
We updated the way of contacting the blackbox to allow using the websocket as a fallback for the longpolling. This is a temporary fix that is solved by the use of the `iot_http` service in saas-18.4. Community PR: odoo/odoo#212052 Task: 4824066
2 changes
Enhancements to existing features
Sections and notes are now hidden from the journal items tab, making accounting entries easier to review. This reduces clutter for users working with invoices, reports, and localization-specific accounting views without changing the underlying accounting data.
Original PR description
Hide sections and notes in journal items tab. task-4517560
Document activities now make it easier to assign an owner with a quick assignment dropdown, helping users complete ownership tasks faster. Folder locking has been removed because improved access rights now cover that need, and unlock confirmation messages now display correctly when another user locked the document.
Original PR description
**Specifications:** -To enhance owner assignment, the activity view shows a 'quick assign' button with a dropdown of available owners to streamline user workflow. -Remove the lock feature for folders, as the improved rights management now covers the use case. -When attempting to unlock a document locked by another user, the confirmation dialog message is not displayed correctly. **Technical**-After PR https://github.com/odoo/enterprise/pull/83203, in the RelationalModel the value of a many2one is now represented using an object instead of an array. While converting the use in the documents module, some occurrences have been missed resulting in strange front-end behavior. Fixing that by making sure all the many2one values are correctly accessed using an object key. **Task**-4637016
2 changes
Enhancements to existing features
Invoices and vendor bills created from sales or purchase orders now keep the order’s existing analytic split while also adding matching analytic distribution rules. Sales orders that create projects also retain both the project analytic account and other non-conflicting analytic accounts, improving reporting accuracy without extra manual work.
Original PR description
The commits in this PR address two points: 1. An account move created from a Purchase Order or Sales Order with an Analytic Distribution only has the analytical distribution from the PO/SO. The invoice/vendor bill does not add the Analytic Accounts expected from matching Analytic Distribution Models. 2. When confirming a SO with a product that creates a project, the Analytic Distribution of the line is filled with the Analytic Account of the project. But this does not happen if there is already another AA in the line before confirming the SO. Another AA may be there because it was added manually or because of an existing distribution model set on the partner or the product. More information on each can be found in the commit messages. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Automated actions now log which action ran and how many records it processed. This helps teams identify poorly performing automations faster and investigate performance issues with clearer evidence.
Original PR description
It regularly happens that badly written automated actions have a negative impact on performances. Unfortunately, there little to no logging which would help the investigation. In other words, there is no clear log of which action is being executed. We improve the logging by recording which automated action is executed on how many records. This will give better clues to fix performance issues. Technical note: the `sudo()` is necessary since the automations are searched as superuser, but returned with the current user which might not have a read access. Test [2] is failing is no `sudo()` is set. [1] https://github.com/odoo/odoo/blob/6a244922b3fac8f3258726301373273d60871c27/addons/base_automation/models/base_automation.py#L608-L609 [2] https://github.com/odoo/odoo/blob/6a244922b3fac8f3258726301373273d60871c27/addons/base_automation/tests/test_automation.py#L75