Monday, January 10, 2022
7 changes · master
Enhancements to existing features
Imported electronic invoices now choose the correct counterpart based on the invoice type instead of always treating them as vendor bills. This helps accounting firms and other users import customer and vendor documents more accurately, reducing manual corrections.
Original PR description
Currently, when importing an invoice, it is assumed that it is a vendor bill. But it is not always the case (accounting firms). This is why the invoice counterpart is now adapted based on the move_type. opw-2697984 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Mass mailing now lets authorized users turn off next-day mailing reports from the settings or directly from the report email. This reduces unwanted report emails while keeping reporting enabled by default for teams that still rely on it.
Original PR description
Purpose ======= Allow users with enough access rights to disable next-day report on mass mailing lists. The option has been added in the mass mailing settings and is enabled by default. Mass mailing reports can also be disabled with a "Turn off mailing reports" button in the report email itself. Reports are enabled and disabled for all responsible. Task-2692211
Event pages now show clearer countdown text for rooms, talks, and exhibitor connections, including a friendly “Starting now!” message when an item is about to begin or has just started. This helps visitors better understand timing and reduces confusing blank countdown labels like “in” or “ago.”
Original PR description
Purpose ======= Change weird formatting sometimes showing "In" or "ago" without displaying any text, give user better awereness of when a room/track starts or has started. Specifications ============= Change widget in website_event_meet to digital: False, display "Starting now!" if track starts/has started within less than 60sec, display info box showing when page was last refreshed. Task-2677865
This update lets Odoo open the main command palette with custom settings, such as a tailored placeholder or pre-filled search text. This makes the search and command experience more flexible for teams that want to adapt it to specific workflows or interfaces.
Original PR description
This commit adds the possibility to open the custom main command palette.
So it is possible to replace some parts of the default command palette
config.
For example, we will customize the placeholder:
```
this.command_service.openMainPalette({
placeholder: "My custom placeholder",
})
```
This commit also modify the api of CommandPaletteConfig, we replace
namespace by searchValue. Now it is possible to open a command palette
with a value in its input.
For example:
```
this.command_service.openPalette({
searchValue: "@test",
})
```
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-prOdoo no longer performs broad cleanup checks after rendering every page, reducing unnecessary work during page generation. This improves overall page response speed and prepares the platform for future streaming of page content to browsers.
Original PR description
This PR removes the two post processing operations applied on rendered templates. This speed up the rendering of every page. 1/ Don't remove empty lines after rendering, but fix the root cause of view inheritancies that was adding lots of empty lines. 2/ handle page break in the only report that uses it (financial reports in Enterprise), rather than parsing every QWeb view rendered to check if there is a page break. It's the first step to stream QWeb templates to highly improve the TTFB (Time to First Byte) and send the <head> to browser so that he can load assets while Odoo is still computing the "slow" content to render. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Page-break handling has been moved out of the general webpage rendering process and into the relevant accounting report logic. This keeps the behavior where it is needed while avoiding unnecessary processing for other pages, improving efficiency and maintainability.
Original PR description
Removed the data-page-break feature from QWeb: it's too specific to just one report, and will allow to not post-process every web page rendered.
Resolved issues and error corrections
This change prevents mail-related records from being deleted automatically in cases where a required link is simply changed to another record. It fixes a bug that could cause unintended data loss or broken behavior in mail features, making the system more reliable for users.
Original PR description
Previously, relational required fields had their auto-generated inverses defined with `isCausal: true`, which seemed logical: if a record is deleted, all the records that depend on it must be deleted too. In practice, it turned out to be a bad idea since there are some cases where you don't want the dependent records to be deleted. For example, there is no point in deleting the current record when a required field is replaced by another one. Furthermore, this actually led to the introduction of new bugs, as the one described in task-2730667. Fixes bug described in task-2730667. Reverts some of these changes: https://github.com/odoo/odoo/pull/81679