Tuesday, April 16, 2024
6 changes · saas-17.2
Resolved issues and error corrections
The barcode scanning settings now allow a slightly longer delay between scanned key inputs by default. This helps slower scanning devices work more reliably and reduces missed or misread scans.
Original PR description
This commit sets the default value for the time between keys config parameter from 100 ms to 150 ms for better support of slow device. Enterprise PR: odoo/enterprise#60611
This fix prevents simulated grouped data requests from crashing when sorting by date fields grouped by day, month, or similar periods. It improves reliability of web module testing tools, helping developers catch issues without false failures.
Original PR description
Before this commit, a mocked read_group with an orderby that contains a date field with granularity (day, month, ...) crashed because the granularity was not removed before looked up in the available fields. 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
New loyalty promotion programs now correctly receive their default trigger when created. This prevents promotions from being set up with missing behavior, reducing manual correction and helping loyalty campaigns work as intended.
Original PR description
Following commit https://github.com/odoo/odoo/commit/20c2e5996651168db3a6d75ace6a8907c1661792 and because the compute method is covering multiple fields, some of them weren't computed any more when creating a new program. The compute was only applied when changing the program type. opw-3850252
Restores a missing autofill template for spreadsheet pivot tables that was accidentally removed in a recent update. This helps users continue filling pivot table data consistently and reduces the risk of broken spreadsheet workflows.
Original PR description
The pivot autofill template was removed by mistake during a recent update of the lib (due to a lack of tests ...).
Survey questions using radio buttons with filtered choices now keep their original labels and order, including translated text. This helps employees and managers see consistent, localized appraisal survey options instead of technical or reordered values.
Original PR description
The "radio selection with filter" widget allows to show/hide some selection values given a list of allowed selection values. The feature is similar to the "filterable selection" widget but for radio buttons. The allowed selection context now takes a list of technical strings instead of a list of (technical string, human string) pairs. This allows to keep the (possibly translated) original values along with the original selection order. task-3829801
Survey radio button questions that filter available choices now keep the original choice labels and order, including translated labels. This prevents users from seeing incorrect or untranslated options in filtered survey selections, such as recruitment surveys.
Original PR description
The "radio selection with filter" widget allows to show/hide some selection values given a list of allowed selection values. The feature is similar to the "filterable selection" widget but for radio buttons. The allowed selection context now takes a list of technical strings instead of a list of (technical string, humain string) pairs. This allow to keep the (possibly translated) original values along with the original selection order. task-3829801