Daily updates from Odoo
Thursday, January 9, 2020
8 changes
Enhancements to existing features
Reordering rules now calculate timing automatically, including supplier, production, purchasing, and safety delays, so replenishment is triggered at the right moment. Scheduler processing is faster and purchase or production requests from the same rules are grouped more accurately, reducing manual planning work and avoiding late or duplicated procurement.
Original PR description
- Improve the onboarding on reordering rule with an automatic computation of delay - Improve the scheduler performance by running the procurement requests together. - Add the days to purchase notion. - Merge production from same reordering rules. More details could be find in each specific commit. Task 1849912
Website editor option controls can now automatically enable related controls when selected or previewed. This makes editing behavior more consistent and reduces the chance that users need to manually adjust multiple related settings.
This change avoids recalculating values that Odoo has already computed and temporarily stored during record creation. It can significantly speed up bulk operations, such as creating many sales order lines, without changing user-facing behavior.
Original PR description
Description of the issue/feature this PR addresses: Unnecessary recomputation of values already present in cache, leading to a substantial overhead in some use cases (e.g. creation of multiple sale.order.line records). Current behavior before PR: Computed field values that have not yet been written to the database may be recomputed even if the correct result for that record is already present in the cache. Desired behavior after PR is merged: Computed field values that have not yet been written to the database are recomputed only if the correct value for that record is not already present in the cache. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Website editors can now set an explicit default value for supported form fields instead of losing input changes during editing. This makes it easier to prepare pre-filled forms for visitors while keeping file upload fields unchanged.
Original PR description
Description of the issue/feature this PR addresses: Without this patch, changes done in any of the inputs are not saved. Now, that behavior remains the same, but a new explicit option is added to each supported input (all except `type="file"`) to set a custom default value.  -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr @Tecnativa
This update adds clearer internal labels to sections of the CRM lead and opportunity form. It helps implementers and partners customize the form more reliably without changing what end users see.
Original PR description
Description of the issue/feature this PR addresses: Since this view has several times the same fields (such as partner_id), it is tricky to use a xpath to locate such fields. Adding a name on the groups makes them very easy to xpath. Current behavior before PR: No reliable way to locate a field using xpath. Desired behavior after PR is merged: Reliable way to locate a field using xpath. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update prevents saved mass mailing records from having an empty name. It avoids save-time errors caused by the underlying marketing source record requiring that name, making mailing edits more reliable.
Original PR description
Description of the issue/feature this PR addresses: mass_mailing Current behavior before PR: Before this commit "Name" was not required on `mailing.mailing` while it is required at field level `utm.source` so making it empty will raise error  Desired behavior after PR is merged: After this commit, "Name" field will be required on Created Records (This is not needed while creating new Record as we set a default value from create method)  -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The app home menu has been rebuilt to provide a cleaner, more consistent experience across standard and Studio modes. Users get improved keyboard navigation, updated layout behavior, and better integration of related tools such as expiration notices and app/icon creation.
Original PR description
We completely rewrite/test the home menu with the owl library.
SEPA batch payments can now be marked for batch booking, so all payments in a batch appear as one combined line on the bank statement. This makes bank reconciliation easier and reduces manual matching work for finance teams.
Original PR description
[IMP] account_sepa_direct_debit, account_batch_payment: put payment_method_code field in account_batch_payment (still invisible), so that submodules needing it don't have to add it every time [IMP] account_sepa: add a checkbox on batch payments to enable batch booking (just like for direct debit) With batch booking enabled, all the payments of the batch will be grouped in a single line on the bank statement, easing reconciliation.