This update adjusts the default value for a critical field ('id') across several core Odoo modules, including AI, Approvals, Planning, VoIP, and WhatsApp. This change ensures consistency and simplifies configuration for these features, streamlining the user experience.

* planning,voip,website_helpdesk_livechat,whatsapp 
"id" is now the default value in the parent class.

task-4801145

PR community: https://github.com/odoo/odoo/pull/246122

This update improves the readability of vehicle names within the Odoo Enterprise system. A test related to the fleet report has been updated to align with the new vehicle name format – ensuring consistent reporting accuracy. This change maintains the integrity of the fiscal categories fleet report.

The vehicle display name format has been improved for better readability.

Adapt the fiscal categories fleet report test to reflect the new format:
- From "Wayne Enterprises/Batmobile/No Plate"
- To   "No Plate: Wayne Enterprises/Batmobile"

This keeps the test consistent with the updated vehicle name representation.

task-5013634

This update clarifies the labels used for DIMONA categories within the Belgian HR payroll module. The changes also enforce a specific ordering of these categories, ensuring data consistency and accuracy for payroll calculations. This improves the reliability of payroll reporting and compliance in Belgium.

…ordering

Task Id:5478540

This update resolves an issue where the default appointment view wasn't consistently displayed. The previous code prioritized a Gantt view, overriding the intended list view. The fix removes unnecessary code calls to ensure the list view is used by default, while still allowing customization through Odoo's studio interface.

Steps to reproduce
==================

- Install web_studio,appointment
- Go to Appointment > Schedule > Staff Bookings
- Open studio
- Click on Views > List > Set As Default
- Exit studio
- Refresh the page

=> The list view is not used by default

Cause of the issue
==================

The action is overriden in python in order the have the gantt view first.

Solution
========

insert_reorder_action_views is called for three actions and all of them
already contains the inserted views in the correct position.
We can thus remove calls to it. By default, it will be as intended, and
if someone wants to change the order with studio, it will be possible.

opw-4969903

A recent update to WhatsApp functionality within the Odoo Enterprise platform has been fixed. Specifically, an error occurred when users without WhatsApp access attempted to view conversations, preventing them from seeing messages. This fix ensures all users can access and view WhatsApp conversations correctly.

As we refactored the scale driver, we need to update the checksum.

see odoo/odoo#239695

This update ensures compatibility with standard CSS by requiring custom property values to use interpolation. Previously, older versions of the Sass compiler allowed full SassScript expressions, which created inconsistencies with CSS. This change aligns with industry best practices and improves the overall stability of our design tools.

Older versions of LibSass and Ruby Sass parsed custom property declarations just like any other property declaration, allowing the full range of SassScript expressions as values. But this wasn’t compatible with CSS.

To provide maximum compatibility with plain CSS, since version 3.5.0, LibSass requires SassScript expressions in custom property values to be written within interpolation.

Reference:
https://sass-lang.com/documentation/breaking-changes/css-vars/

This update fixes an issue with the IoT Box's driver download process. Previously, enabling a setting allowed it to download standard drivers, leading to potential conflicts and duplicated files. Now, the system avoids downloading standard drivers from standard modules to prevent these issues and ensure stability.

The stable IoT Box uses drivers from git repository: it doesn't download them from the database as it used to do.

However, sh/on premise clients might want to develop custom drivers that the IoT Box would download.
For that, they have to enable a checkbox on the IoT homepage, making the IoT Box download handlers as before.

The issue is it will also download standard drivers that are already present on the IoT Box: on newer databases it would simply overwrite them, but on older ones, it would duplicate as names might have changed. Also, it would introduce issues back that were already fixed.

To avoid this, we avoid adding drivers from standard modules to the downloaded archive, to prevent issues with the main ones.

Forward-Port-Of: odoo/enterprise#105770
Forward-Port-Of: odoo/enterprise#105531

This update fixes an issue where the Follow-Up Report displayed incorrect amounts for reconciled entries. Now, the report accurately shows the remaining balance (residual amount) for each entry, ensuring accurate reporting and financial analysis. This improves the reliability of financial data presented to users.

Currently, when viewing the followup report with reconciled entries, we display full amounts instead of the residual amounts.

task-5868881

Forward-Port-Of: odoo/enterprise#105507

This update corrects a technical issue where order documents weren't being properly updated in the l10n_mx_edi module. By forcing a write-date update, the system now accurately reflects the document's status, ensuring data consistency and compliance. This resolves a previous limitation in how documents were identified for updates.

Before the commit 8b118a7, the search of the documents to update has been limited and ordered.

With the actual domain the records to update will be most of the time the same because is not being updated.

To fix this issue we force to update it.

OPW-5368047

Forward-Port-Of: odoo/enterprise#105282
Forward-Port-Of: odoo/enterprise#103272

This update ensures document discoverability settings (like public or private access) are consistently maintained when moving documents within the system. Previously, moving a document could unintentionally change its visibility based on the destination folder's settings. The move confirmation dialog now clearly reflects this change, providing users with accurate information.

This commit improves the handling of a document's discoverability setting (`is_access_via_link_hidden`) when it is moved between folders.

Previously, when a document was moved, it would inherit the discoverability setting from the destination folder. This could lead to unintended changes in a document's visibility. For example, a publicly discoverable document could become private (requiring a direct link) simply by being reorganized into a different folder.

This behavior was inconsistent with a previous improvement that prevented discoverability from propagating downwards from a parent folder to its children. See PR-93697.

With this change, a document's discoverability is now treated as an intrinsic property that is fully preserved when the document is moved. It is no longer affected by the settings of its destination folder.

To ensure clarity for the user, the move confirmation dialog has been updated to reflect this new logic. It now correctly informs the user that the document's original discoverability setting will be maintained.

Task-5159832

Forward-Port-Of: odoo/enterprise#105877
Forward-Port-Of: odoo/enterprise#97045

This update fixes an issue with how employer social insurance contributions are recorded in the Odoo Enterprise system for Saudi Arabia. The change ensures that these payments are accurately assigned to the correct accounting accounts, improving financial reporting and compliance. This resolves a previous error impacting payroll processing.

Fix the account configuration used by Saudi social insurance contribution salary rules for the company.

This ensures employer contributions are posted to the correct accounting accounts.

Task-5468575

Forward-Port-Of: odoo/enterprise#105182

This update modernizes the process for sending Chilean Electronic Data Interchange (EDI) reports – invoices, factoring documents, and stock pickings – to government servers. Previously, these were automatically sent via a daily cron job. Now, invoices and factoring documents use a new Send & Print wizard, while stock pickings require manual sending. This change enhances efficiency and aligns with Odoo's current system.

`l10n_cl_edi` was written before `account_edi` was developed, as such, it doesn't actually rely on it's sending process for communicating with the SII and government servers. Nevertheless, it still uses a cron to automatically send the records on post rather than the more modern send & print system.

This commit refactors the `l10n_cl_edi*` modules to utilize Send & Print where possible.

Regression: Before, all Invoices, Factoring Documents, and Stock Pickings would be sent automatically and linked properly when the custom cron ran once a day. For invoices and factoring documents this is now accomplished via the Send & Print wizard, but for pickings since there isn't any Send & Print functionality, it must manually be sent now via the button on the form view.

Note: I can't actually find any reason why `l10n_cl_edi` was depending on `account_edi`. It was added in a commit that added it to a lot of modules but never actually used for the sending process or any of the edi format/document code. As such there are no upgrade scripts necessary to migrate from the document system to custom fields.

task-5190489