Wednesday, April 22, 2026
2 changes · saas-19.2
Enhancements to existing features
This update lets users split a manufacturing order into multiple smaller orders when generating serial numbers. It makes it possible to assign one serial number to each sub-order in a single workflow, which simplifies production for items tracked by serial number.
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#257694 Forward-Port-Of: odoo/odoo#255577
Odoo now creates a local API key for each database during synchronization when one is missing. This reduces the need to rely on a shared global key and can make database updates noticeably faster, saving around half a second in some cases.
Original PR description
Before this commit, databases fetched from Odoo's SaaS were contacted using the global API key, which is more costly than using a key local to each database. Avoiding the call from the server to Odoo to check the foreign API key can spare about 500ms on each database where this key is not in the LRU. With this commit, after the synchronization with Odoo.com, we try to generate an API key on each database that doesn't have one yet. To do so, it relies on the API introduced by odoo/odoo#246118. Forward-Port-Of: odoo/enterprise#114406 Forward-Port-Of: odoo/enterprise#106372