Odoo Changelog — 2025-01-09

Thursday, January 9, 2025

3 changes · 18.0

Improvements(3)

Enhancements to existing features

[IMP] mrp: improved mass produce wizard

Core18.0mrpMEDIUM

The mass production wizard now creates follow-up manufacturing orders in a clearer confirmed state with serial numbers already assigned. This improves traceability for partially produced items and helps avoid unintended component consumption.

Original PR description

In this commit:
====================
- The changes ensure better traceability by generating back-orders in a
  'confirmed" state with serial numbers assigned, preventing unintended
  consumption of components. This approach enhances clarity and aligns with
  user expectations for managing partial production.

task-4280758

#manufacturing#traceability#serial numbers#partial production

[DRAFT][IMP] mrp_workorder: improved mass produce wizard

PR #73886

Enterprise18.0mrp_workorderMEDIUM

Manufacturing users can now prepare back-orders from the Produce All action for final products tracked by serial number. This reduces workflow interruptions by avoiding unnecessary blocking from quality instructions tied to work orders.

Original PR description

In this commit:
====================
- Adjusted the workflow to enable users to prepare manufacturing orders (MOs) for back-orders when clicking 'Produce All' for final products linked with serial numbers (SN), without blocking for quality checks when instructions are associated with any work order.

task-4280758

#manufacturing#back-orders#serial numbers#produce all

[IMP] sale_subscription: avoid locking the entire transaction row

PR #76619

Enterprise18.0sale_subscription

Subscription invoice payment processing now uses a lighter database lock to avoid blocking related updates unnecessarily. This reduces the risk of deadlocks during automated subscription billing, improving reliability without changing user-facing workflows.

Original PR description

Before this commit, the transaction row was locked when payment was performed in the subscription invoice cron.
Using `SELECT FOR UPDATE` locks the entire row, primary key included (id in our case). As a result, it could prevent insertion or update or other table refering to the id too. As it is not necessary and could trigger unnecessary deadlock, it is better to rely on `SELECT FOR NO KEY UPDATE` which allow the update of foreign keys.

https://www.postgresql.org/docs/16/explicit-locking.html#LOCKING-ROWS

See https://github.com/odoo/enterprise/pull/74078#discussion_r1873729342

taskid: 4391755

#subscriptions#billing#performance#reliability

In this commit: ==================== - The changes ensure better traceability by generating back-orders in a 'confirmed" state with serial numbers assigned, preventing unintended consumption of components. This approach enhances clarity and aligns with user expectations for managing partial production. task-4280758

In this commit: ==================== - Adjusted the workflow to enable users to prepare manufacturing orders (MOs) for back-orders when clicking 'Produce All' for final products linked with serial numbers (SN), without blocking for quality checks when instructions are associated with any work order. task-4280758

Before this commit, the transaction row was locked when payment was performed in the subscription invoice cron. Using `SELECT FOR UPDATE` locks the entire row, primary key included (id in our case). As a result, it could prevent insertion or update or other table refering to the id too. As it is not necessary and could trigger unnecessary deadlock, it is better to rely on `SELECT FOR NO KEY UPDATE` which allow the update of foreign keys. https://www.postgresql.org/docs/16/explicit-locking.html#LOCKING-ROWS See https://github.com/odoo/enterprise/pull/74078#discussion_r1873729342 taskid: 4391755