Saturday, November 4, 2023
15 changes · 17.0
Enhancements to existing features
The point of sale receipt structure is adjusted so tax letters can be shown for each order line through a related enterprise change. This supports clearer tax information on receipts with minimal direct impact in the community module.
Original PR description
In this commit we adjust the pos module such that, in the corresponding enterprise commit, we can more easily add the tax letters corresponding to each orderline in the receipt. https://github.com/odoo/enterprise/pull/50134 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update adds a helpful tooltip explaining the option for using sections in accounting reports. It makes the setting easier to understand for users configuring composite reports, reducing confusion during setup.
Original PR description
The goal of this pr is to add a tooltip to the use_sections field. task: 3569038 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The IAP "View My Services" button now takes users directly to the services list inside Odoo instead of sending them to the IAP website. This makes service management more consistent with the general settings experience and reduces navigation friction.
Original PR description
Description of the issue/feature this PR addresses: The "View My Services" button of the widget should open the IAP accounts tree view, just as the main "View My Services" button of the general settings. Current behavior before PR: View my services widget redirected to iap website Desired behavior after PR is merged: Updated the widget to redirect to tree view of services task-3580190 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
The accounting screens now place the invoice date before the accounting date in list and search views. This makes the legal invoice date easier to find first, improving clarity for users reviewing or filtering invoices.
Original PR description
We currently have two date fields, "date" and "invoice_date". Before this pr, the "date" column was before the "invoice_date" field. We think it's more logical to have "invoice_date" before the other, since it's the legal date. What has been done: - Swap in the tree view the two columns - Swap in the search view the two columns --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The self-ordering flow now shows a loading screen while orders or menu data are being processed, helping customers understand that the system is working. Search is also easier to use because the input is focused automatically, and restaurant demo data now includes a combo menu for better examples.
Original PR description
- Add loading when rpc in progress. - Auto focus input search when button clicked
Spreadsheet pivot table formula cells are now easier for the system to identify by using the cell’s evaluated result as the pivot display name. This improves reliability when working with pivot tables in spreadsheets without changing the user workflow.
Original PR description
In order to identify an ODOO.PIVOT.TABLE formula cell, we set the display name of the pivot as the evaluated value of the cell containing the formula. Task: 3580153 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
Website editors now have access to refreshed text highlight designs for page content. This gives marketing and content teams more visual options to emphasize key messages and improve page presentation without custom development.
Original PR description
task-3285817
Website input fields now use a standard white background with borders by default, making forms look cleaner and more predictable across themes. A new customization option lets designers choose a different input background color when a non-standard palette is needed.
Original PR description
This PR refactor the "inputs design system" by reverting the correlation `$input-bg == $light == color-3` initially introduced by https://github.com/odoo/odoo/pull/120302. Beside ensuring…
This PR refactor the "inputs design system" by reverting the correlation `$input-bg == $light == color-3` initially introduced by https://github.com/odoo/odoo/pull/120302. Beside ensuring color-consistency, the former system aimed to simplify palette edition by clarifying how `color-3` was used (simply all the UI elements...). While the former system was responsive to user customization and color-presets, it didn't necessarily delight everyone's discerning taste, at least not with default settings/palette. This commit enforces a classic "white with borders" design that's independent from the color palette and doesn't adapt to color-presets. The rationale behind this decision is that the need for non-white inputs is nonexistent and exceptional cases should be addressed using the SCSS editor. As a workaround for users that still wants to challenge themselves with the creation of "not standard" palettes/designs, this commit introduce a colorPicker option assigned to `$input-bg`. The hope is that this new controller help users finding a "compromise color" that could work with any color-presets. Embracing flexibility and open collaboration. task-3568806 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The tax usage check now looks at smaller relationship data instead of scanning large accounting tables, reducing delays on large databases. This helps accounting, purchasing, expenses, and point-of-sale workflows stay responsive when many tax records exist.
Original PR description
Problem --------- The compute_is_used function currently parses through a huge amount of data using the _read_group ORM function. Which causes some performance issues in large databases. Objective --------- Improve performance of the said function. Solution --------- Instead of reading the data on whole tables (ex.account_move_line), we read the relation table between the modules and the taxes. This is done using SQL queries with the EXISTS statement. Furthermore, the code logic is modified so that if all the taxes for which we compute `is_used` have been found, we don't look further in other modules since doing this cannot add any new relevant information and actually slows down the computation. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Website page templates were cleaned up to remove repeated or conflicting styling choices. This helps pages created from these templates display more consistently without changing the underlying website features.
Original PR description
When introducing the templates for the "new page" feature in [1], on some elements classes ended up being specified twice, or being added without removing a contradicting class (e.g. different bottom paddings) This commit adjusts the blocks of the new page templates so that: - no class appears twice - only the visually applied class of several conflicting classes is kept For `pt*`, `pb*` and `o_cc*` the class with the highest number is the visually applied one. [1]: https://github.com/odoo/odoo/commit/b27d52c193a08fe6a4471c844afa3d01a33ccace task-3562147
Account reports now clearly display which companies are being used in the report, making it easier for users working with multiple companies, branches, and tax units to understand the scope of their data. This improvement reduces confusion when generating reports across different organizational entities.
Original PR description
When having multi company (with branches and tax units) it may sometimes be a bit difficult for the user to realize what companies are currently used by the report. This commit adds under the filters, on top of the report the names of the companies present in the options dict with the key companies under certain conditions. task: 3573675
This update improves how pivot table data is processed and displayed in Odoo spreadsheets. The enhancement refines the ODOO.PIVOT.TABLE function to provide better data accuracy and consistency, ensuring that spreadsheet reports pull and display information more reliably from your business data.
Original PR description
Adat tests following the changes of https://github.com/odoo/odoo/pull/140674 Task: 3580153
This update improves the accounting reports experience by adding a quick configuration button directly on reports and enhancing how menu items are managed. Users can now easily access report settings, while the system automatically prevents duplicate menus, refreshes after manual menu creation, and properly handles menu cleanup when reports are deleted or archived.
Original PR description
This PR contains twos commits, one is an improvement on the composite reports and the second is a backport of this pr: https://github.com/odoo/enterprise/pull/49443. The goal of the first commit is to add a button on the reports next to the filters that will redirect to the configuration page of the report. On this page we have changed a placeholder and hide the use_section field in case the report has lines. While the backport adds the following improvements: - Automatic reload after manual menuitem creation. - A UserError is raised when trying to create a duplicate menuitem. - Any existing menuitem is removed when deleting a report, or archived when archiving the report. task: 3569038 and 3422314
This update adds tax letter identifiers to each line item on point-of-sale receipts in Belgium and Sweden. Tax letters help customers and auditors quickly identify the tax category applied to each product, improving receipt clarity and compliance documentation.
Original PR description
In this commit we add the tax letters corresponding to each orderline in the receipt. https://github.com/odoo/odoo/pull/140974
The invoice date and transaction date fields have been reordered in the accounting module's views. The invoice date now appears first since it represents the legal date of the transaction, making the interface more intuitive for accounting users.
Original PR description
We currently have two date fields, "date" and "invoice_date". Before this pr, the "date" column was before the "invoice_date" field. We think it's more logical to have "invoice_date" before the other, since it's the legal date. What has been done: - Swap in the tree view the two columns - Swap in the search view the two columns