Martin Maes
ae7e503947
In 16.4, this commit https://github.com/odoo/odoo/commit/c3b7a87462cd41654d0e2bd3beb2f0e065ddfb75 created a notification when replenishing a product. However, it achieved it by modifying a stock.order_point which was not the ideal solution as we don't want the order_point to change. In this commit, we will revert to the previous behaviour, but we'll keep the notification by delegating it to the wizard itself. The way the record created were retreived (to display the notification) was thanks to the orderpoint. As we do not have access to orderpoints now, we are just retreive the first record (of a certain type) created just after the start of the function. This method has a big problem : concurrencies. If anyone creates a record on ``manufacturing.order``, ``purchase.order.line`` or ``stock.move`` between the start of our timer and the creation of our record, a wrong record will be selected. task-3527727 Part-of: odoo/odoo#145384
12 lines
395 B
Python
12 lines
395 B
Python
# -*- coding: utf-8 -*-
|
|
# Part of Odoo. See LICENSE file for full copyright and licensing details.
|
|
|
|
from . import change_production_qty
|
|
from . import stock_warn_insufficient_qty
|
|
from . import mrp_production_backorder
|
|
from . import mrp_consumption_warning
|
|
from . import product_replenish
|
|
from . import stock_assign_serial_numbers
|
|
from . import mrp_production_split
|
|
from . import stock_label_type
|