Thursday, April 23, 2026
6 changes · saas-19.3
Enhancements to existing features
Users can now split a manufacturing order directly from the serial number generation wizard. This makes it possible to assign one serial number per sub-order in a single step, instead of having to choose between splitting the order and generating serials separately.
Original PR description
Since 4bb4e08066449, producing multiple serial that have been generated is only doable on one mo. We can split mo. we can generate serial number but we cannot do both at the same time. This commit adds a new button into the generate serial wizard to split the main mo into the number of serial wanted and attribute one for each sub mo. 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 Forward-Port-Of: odoo/odoo#259156 Forward-Port-Of: odoo/odoo#255577
This update streamlines how notifications are sent within Odoo. Previously, notifications were delayed, but now they are sent immediately when a 'store' is created, improving efficiency. This change ensures notifications are delivered promptly and reliably, enhancing the user experience.
Original PR description
Since [1], store result is computed at the very end of the TX. As a result, no matter when `bus_send()` is called, the actual value of the notification will be the same: the one computed during bus's precommit hook, which creates the notifications. As a result, calling `bus_send()` manually is useless: we can just call as soon as a store is created, provided it has a bus target. part of task-5242369 [1]: https://github.com/odoo/odoo/pull/256079 enterprise: https://github.com/odoo/enterprise/pull/114187
This update improves WhatsApp functionality by automatically sending messages through the system's messaging bus when a WhatsApp channel is created. This streamlines the process of sending messages and ensures they are properly routed. It's part of a larger effort to enhance WhatsApp communication within Odoo Enterprise.
Original PR description
`Store` automatically calls bus send when a bus channel is given. part of task-5242369 community: https://github.com/odoo/odoo/pull/259865
This update improves the setup process for printers in our Point of Sale system. A new checklist document has been added to the POS form, guiding users through the necessary steps to enable LNA access for their printers via the browser. This will reduce user frustration and improve the overall POS experience.
Original PR description
The LNA configuration for printers is complicated for users. To help them this PR will add a check list document inside the point of sale form view which will explain all the steps the clients should do to enable LNA access for their printers in the browser. Task-[5933321](https://www.odoo.com/odoo/project/1737/tasks/5933321) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#254551 Forward-Port-Of: odoo/odoo#249226
This update enhances the reporting of audits by allowing users to search for return types by name. Crucially, it now uses fiscal year periods instead of annual periods for generic, French, and Belgian audits, aligning with updated reporting requirements.
Original PR description
This change enables the user to search for the return types using the name of the return. In addition, it switches the generic audit, french audit and belgian audit to use the fiscal year periodicity instead of the annual periodicity. task: 5948404 Forward-Port-Of: odoo/enterprise#112280
This update streamlines offer contract management by automatically treating contract start dates within existing periods as amendments, creating new versions and archiving outdated data. A new warning system alerts users to potential replacements, and technical changes ensure data consistency and prevent cache issues, improving overall system stability.
Original PR description
**Contract Amendment & Versioning Logic** * When an offer's contract start date falls within an existing contract period, it is treated as a contract amendment (new version) rather than a new…
**Contract Amendment & Versioning Logic** * When an offer's contract start date falls within an existing contract period, it is treated as a contract amendment (new version) rather than a new contract. * For contract amendments, the offer's contract end date is read-only and automatically inherited from the existing contract. * When creating a new offer, any existing versions with effective dates **on or after** the new offer's contract start date are automatically archived, as they likely contain outdated data. * Added a warning to notify users when a new offer will replace existing future versions. **Technical Refactoring** * Simplified the `employee_version_id` computation by delegating to the existing `_get_version` method on the employee model. This ensures the selected employee version correctly matches the contractual state effective at the new offer's * Ensured cache invalidation after rollback savepoints to prevent stale data. The overridden `_get_version` in `hr_contract_salary_payroll` writes to `employee.version_id` and the `contract_template_id`; although rolled back, it polluted the cache. We now always invalidate the cache after rollbacks to avoid inconsistencies, including later module installation. **Simulation & Chatter** * Inside the simulation, when calling `_get_version`, we need to adjust the contract dates of the version being simulated. The main challenge is allocating this simulated version between existing employee versions without creating contract overlaps, since overlaps raise validation errors. * To avoid this issue, we move to a new approach. We archive all versions after `employee.version_id` and set `employee.version_id.contract_date_end = False`. * Then, instead of replacing the active version, we create the simulation version as an amendment to `employee.version_id`. The amendment's effective date is set to `max(fields.Date.today(), employee.version_id.contract_date_start, self.contract_start_date)` + 1 day. This ensures the current version remains unchanged, avoids contract overlaps, and prevents chatter pollution. task: 5408192 Forward-Port-Of: odoo/enterprise#108552 Forward-Port-Of: odoo/enterprise#103846