Daily updates from Odoo
Wednesday, April 24, 2019
10 changes
Enhancements to existing features
Inventory planning can now use available stock first for products that would otherwise always trigger a purchase or replenishment. This reduces unnecessary purchase orders when enough stock is already available, such as after returns, while keeping the existing buy-to-order behavior when stock is insufficient.
Original PR description
In some occasions, products can be available in a location,
but are still ignored when the MTO is set on those products.
(e.g.: When a product is returned)
To avoid this, we add a `procure_method` named `mts_else_mto`,
allowing procurement to reserve the products if enough of them
are available in his source location.
In order to achieve this, we apply the MTS or the MTO `procure_method`
on the moves from the procurement depending on whether or not there are
enough quantities of the needed products in the source location
('All or nothing' logic).
**Quick performance test:**
With a Sale Order of 800 differents products set as MTO+Buy,
Half of these products available in stock.
**Before the patch :**
2m30s to confirm the SO (800 PO Lines created)
**After the patch:**
- MTO (procure method MTO): 2m30s to confirm the SO (800 PO Lines created)
- MTO (procure method MTS_ELSE_MTO): 2m26s to confirm the SO (400 PO Lines created)
TaskID: 1831347The notification system has been modernized and made available on the frontend, giving users more consistent toast-style messages across Odoo. This helps features in areas like Calendar, Barcodes, and partner autocomplete show clearer feedback while reducing duplicated notification behavior.
Users can now preview email templates in a chosen language before sending them. This helps teams verify translated emails and ensure customers receive correctly localized messages.
Original PR description
Task : https://www.odoo.com/web?#id=30245&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 Pad: https://pad.odoo.com/p/r.cd909afd5e2214a1845d437b3bf52d66
Studio now shows more user-friendly names for available field widgets, making customization easier for users. It also hides widget options that do not apply to the selected field type, reducing confusion and configuration mistakes.
Original PR description
Description of the issue/feature this PR addresses: Task: https://www.odoo.com/web#id=1918327&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.aa716e047f2963e27e3b789ea1921ced Current behavior before PR: - Widget names are not user friendly - Unnecessary widgets were there which are not compatible with field type Desired behavior after PR is merged: - Widget names will be user friendly - Unnecessary widgets are removed which are not compatible with field type -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Messages typed in Discuss or chat are no longer cleared before the system confirms they were sent. This helps prevent message loss during slow or interrupted connections, reducing frustration and repeated work for users.
Original PR description
Before the changes, when a message was posted (on Discuss or in the chat window), the composer was cleared directly as it didn't wait for the rpc response. If there was latency or a connection loss, the message disappeared from the composer but took time to appear in the content window or didn't appear at all and was lost. Now, the composer waits for the rpc response and then is cleared. Task #1957856
Users can now reorder records directly in ungrouped Kanban views by dragging cards when a handle field is available. This brings the same easy sequencing experience already available in list views to Kanban views, including embedded one-to-many Kanban sections.
Original PR description
Task: https://www.odoo.com/web?#id=1902808&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.9956a77772756a2093564a078716e335 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update makes invoice screens, portal views, PDF reports, and email templates clearer by reorganizing fields, removing duplicated information, and improving labels and wording. It also standardizes the multiple-attachment upload experience so users get a more consistent interface when adding files in forms and emails.
Original PR description
Impacted modules: account, mail and web. (The 2 last only for the upload widget). The merge brings lots of small UI improvements for invoices: - reorganize form view to group field by their puprose and information type they provide to the end user - remove duplicate information - clean labels and tooltips for some fields It also makes the "upload multiple widget" (the cutom one from the chatter) generic for all form views, ... (notably for the email composer wizard). Task-1930087
Studio now shows clearer widget names and descriptions so users can better understand available field options. It also hides incompatible or undocumented widgets in normal use, reducing confusion when configuring views.
Original PR description
Description of the issue/feature this PR addresses: Task: https://www.odoo.com/web#id=1918327&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.aa716e047f2963e27e3b789ea1921ced Current behavior before PR: - Widget names are not user friendly - Unnecessary widgets were there which are not compatible with field type Desired behavior after PR is merged: - Widget names will be user friendly - Unnecessary widgets are removed which are not compatible with field type - **New test case added** -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The frontend notification experience was adapted across barcode, enterprise web styling, and Studio reporting areas to align with the newer notification system. This helps keep user messages consistent across apps and reduces friction when users interact with these screens.
Resolved issues and error corrections
This fixes an incorrect Belgian payroll value that could cause an employee contract wage to be automatically overwritten with a higher amount after editing. The change helps ensure payroll contract wages stay as entered and prevents unintended salary adjustments.
Original PR description
Commit ec86223 changed the employer onss to the 2019 value. But commit 41a8e9b introduced the 2018 value elsewhere in parallel. As the two commits did no conflicted at rebase it was not seen when merging and the 2018 value was left unmodified. The consequence of this wrong value is seen when changing the wage of a contract: set the wage, then it is overwritten by an onchange to a higher value. Sadly this behaviour is wrong.