Thursday, February 4, 2016
5 changes · master
Enhancements to existing features
This update makes warehouse configuration clearer by offering three setup levels, from a single warehouse and location to multiple warehouses with multiple locations. It also adjusts related menus and fields so users only see options relevant to their chosen warehouse complexity, and ensures new companies get a related warehouse automatically.
Source documents shown in the chatter history can now be opened directly, making it easier for users to trace conversations back to related business records. This improves navigation across sales, purchases, stock, manufacturing, and events when reviewing document history.
Original PR description
Task: https://www.odoo.com/web#id=19637&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 pad: https://pad.odoo.com/p/r.xrbkexmZvkwd7Sp7 Make source document in the chatter and make clickable too.
Warehouse and location settings are now clearer, with separate options for managing multiple locations or multiple warehouses. New companies automatically get a related warehouse, making setup easier and reducing manual configuration.
Original PR description
- Separate group_stock_multiple_locations into 2 groups: o group_stock_multi_locations o group_stock_multi_warehouses - Add a selection fields to manage the 3 levels of warehouses management complexity: o Manage 1 WH with 1 location o Manage 1 WH with multi locations o Manage multi WHs with multi locations - Display the menuitems and fields accordingly - On a company creation : Create a related Warehouse - stock.location : Add a helper on the parent location - stock.warehouse : Add a helper on the company_id field
Resolved issues and error corrections
Updates made to a parent business object now automatically carry through to related child objects. This improves consistency across the system and reduces cases where customizations or upgrades behave differently depending on the model relationship.
Original PR description
The problem we address is the following: - suppose model B inherits from model A; - extend model A (using `_inherit`) by adding fields, methods, etc. - the changes made to A are not visible in B. We have modified the way the models are built, such that changes in parent models are automatically visible in children models. This fixes #9084.
Features or functions removed from Odoo
An obsolete reference to an old field type was removed from the calendar area. This keeps the codebase cleaner and avoids maintaining legacy references that no longer affect current business workflows.
Original PR description
This one2one reference is no longer needed since one2one fields have been deprecated for ages. Official statement from Olivier Dony: https://twitter.com/odony/status/694558878718136320