Tuesday, March 5, 2024
8 changes · 17.0
Enhancements to existing features
The salary configurator now intelligently manages benefit choices for Belgian employees. When selecting a Private Bike benefit, the system automatically disables the Fuel Card option and clears any previously entered amount, preventing conflicting benefit selections and improving the user experience.
Original PR description
[IMP] l10n_be_hr_contract_salary: improve salary configurator choices This commit includes improvement to the benefit selection. Implementing a logic where selecting "Private Bike" automatically disables the "Fuel Card" option and resets any entered amount to 0 Task-3749460
The Documents module has been improved by removing an outdated archive toggle that was no longer relevant and reorganizing the workflow rule form to combine conditions and actions into a single unified page. This simplifies the user interface and makes the workflow configuration process more intuitive.
Original PR description
**Commit 1:** Since we can no longer archive documents, the 'Include Archived' toggle checkbox of the domain selector is now irrelevant and hence this commit removes it. Technical: The archive…
**Commit 1:** Since we can no longer archive documents, the 'Include Archived' toggle checkbox of the domain selector is now irrelevant and hence this commit removes it. Technical: The archive feature for documents has been removed with #37389. However, the active field is still being utilized for the 'trash' feature and hence cannot be removed. Whether the `Include Archived` toggle should be displayed or not, is determined by checking if a particular model has 'active' in its fieldDefs (i.e. if the model has archive/unarchive feature). As a result, the condition becomes true in the case of 'documents' model despite archive records feature not being available anymore. Thus, this commit adds a condition to check resModel, and hides the toggle checkbox from the domain selector in case of 'documents' model, by deleting 'active' from fieldDefs. **Commit 2:** This commit alters the view of documents workflow rule form such that the two separate pages for 'conditions' and 'actions' are now reorganized and merged altogether. Task: [3695462](https://www.odoo.com/web#id=3695462&menu_id=4722&cids=2&action=333&active_id=965&model=project.task&view_type=form)
This update improves the order preparation display system with better note editing, product organization, and order progression logic. Notes are now edited in-place instead of recreating order lines, products are sorted by category for easier viewing, and orders advance to the next stage more intelligently based on which items are marked as complete.
Original PR description
Behavior before the changes: - When a note was modified, it cancelled the old orderline and recreated it with the new note. - Products were not sorted by category in the order preparation display. - Clicking on the header of an order sent it directly to the next stage, regardless of whether lines were crossed out or not. - There were brackets around the order number. Behavior after changes: - When a note is modified, it is modified directly on the existing orderline. - Products are now sorted by category in the order. - Clicking on an order header sends only the crossed-out lines to the next stage. If no line is crossed out, the entire order is sent. - There are no longer any brackets around the order name. taskId: 3764317 community PR: https://github.com/odoo/odoo/pull/155246
This update fine-tunes the Luxembourg payroll salary rules to reflect regulatory changes that took effect in 2024. The changes affect salary rule parameters, categories, and contract configurations to ensure accurate payroll calculations and compliance with updated Luxembourg tax and employment regulations.
Original PR description
Tuning lu salary rules, especially some rules and parameters changed in 2024. Backport of - https://github.com/odoo/enterprise/pull/44597 task-3770404
The restaurant point-of-sale system now handles order notes more efficiently by updating them directly instead of recreating orders, organizes products by category for better clarity, and improves order progression logic so only completed items advance to the next stage. These changes streamline kitchen operations and reduce confusion during order preparation.
Original PR description
Behavior before the changes: - When a note was modified, it cancelled the old orderline and recreated it with the new note. - Products were not sorted by category in the order preparation display. - Clicking on the header of an order sent it directly to the next stage, regardless of whether lines were crossed out or not. - There were brackets around the order number. Behavior after changes: - When a note is modified, it is modified directly on the existing orderline. - Products are now sorted by category in the order. - Clicking on an order header sends only the crossed-out lines to the next stage. If no line is crossed out, the entire order is sent. - There are no longer any brackets around the order name. taskId: 3764317 enterprise PR: https://github.com/odoo/enterprise/pull/57385
This update significantly speeds up the process of creating automatic reorder points in your inventory system. By optimizing how the system calculates product stock levels across multiple warehouse locations, the operation now completes 16-30 times faster, reducing processing time from several seconds to under a second for typical configurations.
Original PR description
This commit changes the computation of product having a negative forecasted quantity to create manual orderpoints. The issue was that each replenish location needed multiple `_read_group` on…
This commit changes the computation of product having a negative forecasted quantity to create manual orderpoints. The issue was that each replenish location needed multiple `_read_group` on `stock.quant` and `stock.move` on all storable product. This commit makes only 3 `_read_group`s for all products x locations and post process the group and quantity sum by location in Python. This method gives some performance gain in time as well as in memory consumption Task: 3653272 Here is the time comparison before/after the patch for different configuration | | before | after | |---|---|---| | 700 loc, 300 prod | 14.08s | 850ms | |10 loc, 3k prod | 2.174s | 349ms | |700 loc, 30k prod | TO | 74s | Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#154596 Forward-Port-Of: odoo/odoo#149966
This update improves the performance of spreadsheet reports by reducing unnecessary recalculations when filters are used. When loading reports with filter references, the system now waits for all data to be ready before recalculating, rather than recalculating after each individual data fetch. This change reduces loading time for the Timesheet report from approximately 10-15 seconds to 6-9 seconds by eliminating redundant calculations.
Original PR description
Steps to reproduce:
- create a relational filter, let's say on `res.company`
- add a default value
- reference the filter in a cell with `=ODOO.FILTER.VALUE("my filter")`
=> every `ODOO.FILTER.VALUE` triggers an evaluation
With this commit, the re-evaluation after the data is fetched uses the
data source mechanism which only re-evaluates when all the data promises
are resolved, instead of evaluating after every resolved promise.
With this commit, the number of evaluations required when loading the
Timesheet report on our prod goes from 5 evaluations to only 3 (each evaluation
is 2-3s) because `ODOO.FILTER.VALUE("Company")` is present two times.
One issue this commit doesn't fix: there one RPC per `ODOO.FILTER.VALUE`
(can be fixed in master very easily because we refactored data fetching)
Task: 3787125
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThis update corrects terminology and adds Italian language translations to the Italian EDI (Electronic Data Interchange) website sales module. The changes ensure that Italian users see properly translated and accurate terms throughout the module, improving the user experience for Italian-speaking customers and businesses using this e-commerce feature.
Original PR description
Correct the terms in this module and translate them in Italian. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#155993 Forward-Port-Of: odoo/odoo#155905