Odoo Changelog — 2024-07-16

Tuesday, July 16, 2024

4 changes · master

Improvements(3)

Enhancements to existing features

[IMP] *: lazy load gantt views

Enterprisemasterappointmenthr_attendance_gantthr_gantthr_holidays_gantthr_payrollhr_payroll_holidayshr_work_entry_contract_enterpriseindustry_fsmmrp_workorderplanningplanning_contractproject_enterpriseMEDIUM

Gantt scheduling views are now loaded only when needed instead of during initial app startup. This should improve loading performance for users who do not immediately open scheduling screens, while keeping gantt functionality available across affected business apps.

Original PR description

We make the gantt view and its extensions to be lazy loaded.
locs (js,xml,scss) added in "web.assets_backend_lazy" ~ 8500.

Task ID: `3546321`

#performance#gantt#lazy-loading#scheduling

[IMP] *: new reports document layout

PR #64811

Enterprisemasteraccount_followuphr_payrollindustry_fsm_reportindustry_fsm_salel10n_au_hr_payrolll10n_be_hr_payrolll10n_be_reportsl10n_br_edil10n_ch_hr_payrolll10n_cl_edi_stockl10n_co_dianl10n_co_reportsl10n_ec_edil10n_in_hr_payrolll10n_mx_edil10n_my_reportsl10n_pe_ediplanningpos_blackbox_besale_rentingsale_subscriptionsignweb_studioMEDIUM

Report documents across payroll, accounting follow-up, field service, sales, point of sale, and multiple localization areas have been adjusted to align with the new standard document layouts. This improves visual consistency while preserving special payroll and local statutory report formats where required.

Original PR description

This PR follows the changes made in community to introduce and review the report documents layouts.

- Adapting tables to community changes
- Fixing xpaths
- Disabling layout design on payroll report

Community PR: https://github.com/odoo/odoo/pull/169512

task-3628644

#reports#document layout#payroll#localization

[IMP] web_studio: add columns in qweb tables

PR #66724

Enterprisemasterweb_studioMEDIUM

The report editor now lets users add or remove columns in complex report tables that previously could not be edited this way. This makes customizing business reports in Studio easier while preserving current limitations around row editing.

Original PR description

The report editor edits raw qweb. In this setting, tables can contain illegal nodes with regard to html spec. So we need to convert those tables into something else, that is, as simple div-like elements displayed as flex.

Before this commit, it was not possible to add/remove columns. This commit proposes a solution to this.
Note that, given the use cases, removing/adding rows is still impossible because we assume tables of that type are doing a `t-foreach` in the row dimension.

task-3940106

#reports#studio#table editing

Removals(1)

Features or functions removed from Odoo

[REV] purchase, account, sale: add account.order(.line).mixin

PR #66597

Enterprisemasterpurchaseaccountsaleaccount_avatax_saleaccount_avatax_stockaccount_budgetaccount_invoice_extract_purchasedelivery_shiprocketdocuments_accounthelpdesk_accounthelpdesk_sale_timesheethelpdesk_stockindustry_fsm_saleindustry_fsm_sale_reportl10n_br_edi_salel10n_br_test_avatax_salel10n_cl_edi_stockMEDIUM

This change rolls back a previous attempt to share common sales and purchase order logic because it added complexity and limited how each process can evolve. It also restores related naming changes to avoid conflicts, keeping sales and purchasing behavior separate and more stable.

Original PR description

In the end the feature as implemented in the original PR is not desired/correct and the mixin is also not wanted due to it adding more complexity than removing. Additionally, we want to keep the SO and PO functionality/evolution separate so moving their apparently common fields/methods into a mixin was a mistake.

Therefore we revert the mixin and all of the renaming refactorings that also came out of the PR since they depend on the mixin and we do not want to handle the complexity of fixing the conflicts.

#revert#sales#purchase#orders

This PR follows the changes made in community to introduce and review the report documents layouts. - Adapting tables to community changes - Fixing xpaths - Disabling layout design on payroll report Community PR: https://github.com/odoo/odoo/pull/169512 task-3628644

The report editor edits raw qweb. In this setting, tables can contain illegal nodes with regard to html spec. So we need to convert those tables into something else, that is, as simple div-like elements displayed as flex. Before this commit, it was not possible to add/remove columns. This commit proposes a solution to this. Note that, given the use cases, removing/adding rows is still impossible because we assume tables of that type are doing a `t-foreach` in the row dimension. task-3940106

In the end the feature as implemented in the original PR is not desired/correct and the mixin is also not wanted due to it adding more complexity than removing. Additionally, we want to keep the SO and PO functionality/evolution separate so moving their apparently common fields/methods into a mixin was a mistake. Therefore we revert the mixin and all of the renaming refactorings that also came out of the PR since they depend on the mixin and we do not want to handle the complexity of fixing the conflicts.