Thursday, June 18, 2020
6 changes · master
Enhancements to existing features
Inventory workflows now default newly created products to storable items, allow product creation directly during inventory adjustments, and keep key transfer actions visible when records are unlocked. Replenishment is also easier to use with the stock app alone, reducing setup friction for businesses getting started with inventory management.
Original PR description
Adds improvements for inventory onboarding experience: 1. New Products "Storable" by default - Makes it so the default "Product Type" = "Storable Product" ('type'='product') when creating a new…
Adds improvements for inventory onboarding experience:
1. New Products "Storable" by default - Makes it so the default "Product Type" = "Storable Product" ('type'='product') when creating a new product in a manufacturing order, an inventory transfer, a Lot/SN, a scrap order, and a batch picking, . Previously the default was "Consumable".
2. Creating new products is possible in an inventory adjustment. This is possible in the following cases:
- Via the `product_ids` field in the `stock.inventory` form view
- Via the `product_id` field in the `stock.inventory.line` tree view **when** no `product_ids` assigned
These new products follow same "Storable" by default
3. Keep picking action buttons visible when unlocked. This covers buttons: "Check Availability",
"Validate", "Sign", "Print", "Return", "Unreserve", "Scrap", and "Cancel". Additionally relax the 'is_initial_demand_editable' restriction on 'qty_done' in 'stock_move_line_operation_tree' so that readonly status is only dependent on 'is_locked' status.
4. Make it so product replenishing can occur with just the stock module. This is done by adding a new "pull" rule in the receive routes. This rule is removed when installing manufacturing or purchase modules to prevent unexpected behavior for MTO related products. When manufacturing/purchase modules are removed, "pull" rule will not be re-added and it is expected that advanced users will be able to handle the case when customized receive route rules are deleted by installing manufacturing/purchase modules.
Task: 2220129
Enterprise PR: odoo/enterprise#10719
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prOdoo now handles placeholders in translated messages more safely, reducing the chance that a bad translation breaks a workflow. Many existing messages were updated to the clearer format, improving translation quality and flexibility across languages.
Original PR description
Support two new syntaxes with `_()` method:
```py
_("This is so %s") % 2019
_("Text with %s placeholders", 42)
_("Text with %(num)s placeholders %(symbol)s", num=42, symbol="🧀")
```
The main benefit is to have a fallback on the source string if formating the
translated string fails (e.g. `"Foo %s"` translated `"Foo s%"`).
This PR converted most (but not all) calls to _ using placeholders to use the
new syntax. Hopefully, the remaining ones will be converted in the future and
avoid technical debt.
Use named placeholders when needed. If more than one placeholder is present in a
string, using named placeholder can be beneficial to reorder the placehodler
position (for languages like Japanese that do not use the same phrase
construction). On some sentences, it also brings clarity on the meaning of the
placeholders.
Task-id: 1853119This update aligns many Enterprise modules with Odoo’s newer translation wording format. It is an internal modernization that helps keep messages consistent and easier to maintain, with little direct impact on day-to-day users.
Original PR description
Enterprise part of odoo/odoo#52155
Planning users can now start or open a chat by clicking an employee's avatar in the Gantt schedule. This makes it faster for managers and teams to contact the right person directly from the planning view.
This update improves how budget records are queried behind the scenes, helping related budget information load more efficiently. It supports smoother performance for users working with accounting budgets without changing day-to-day workflows.
Original PR description
Enterprise part of odoo/odoo#42831
Products created from the Barcode app during operations or inventory adjustments now default to Storable Product instead of Consumable. This better matches inventory workflows, helping ensure newly scanned or added products are tracked in stock correctly from the start.
Original PR description
This commit makes it so the default "Product Type" = "Storable
Product" ('type'='product') when creating a new product in the
barcode app's Operations or Inventory Adjustments. Previously the
default was "Consumable".
Specification 1 of Inventory Onboarding task.
Task: 2220129
Community PR: odoo/odoo#51676