Spreadsheet formulas for Odoo lists and pivots now apply formats dynamically based on their results, including cleaner integer display without unnecessary decimals. List formulas can also use the correct currency formatting for each user, making exported and manually created spreadsheet reports easier to read and more reliable.

depends on https://github.com/odoo/o-spreadsheet/pull/1460
=========================================


[IMP] spreadsheet: Adapt pivot/list formula to dynamic format
---------------------------------------------------------------------
Following the introduction of dynamic formats in task 2857337,
https://github.com/odoo/o-spreadsheet/commit/5ddee35f36939dabf3b9d0ddb9fb658604466efa
Odoo specific formulas (i.e. ODOO.LIST, ODOO.PIVOT) can have different
formats depending on their evaluation, rather than be hardcoded during
the model insertion, which did not work when one would manually create
those formulas. (task 2857337)

Furthermore, we take this opportunity to differentiate `integer` measures
from `float` and `monetary` as the former should not have a format with
decimals.

Task 2857337 and 2899195

Co-authored-by: Rémi Rahir <rar@odoo.com>

[IMP] spreadsheet: Apply currency formatting to lists
----------------------------------------------------------
With the introduction of dynamic format for formulas, we can now apply
currency specific formats to list formulas (it required to fetch
res.currency data from the server) which will apply a dedicated format
for each user depedending on the fetched records.

Note that this feature does not apply to pivots as the aggregate can mix
up different currencies and we don't have a simple wsay to detect if a
single currency was used. For these cases, users can resort to a static
currency format.

Task 2788853

Co-authored-by: Alexis Lacroix <laa@odoo.com>

The Approval app interface has been visually cleaned up by removing unnecessary styling that affected button appearance. This makes buttons look more consistent, improving the overall user experience without changing functionality.

Prior to this PR, there was unnecessary scss for an opacity on an 
element. The changes make all the buttons consistent with each others.

task-2922387

Expense attachments are now sent for digitization through a scheduled background process instead of immediately all at once. This helps prevent the system from slowing down or getting stuck when many receipts or documents are scanned at the same time.

Purpose:

Send attachments for digitization via triggering the cron so that in case
lots of documents are scanned simultaneously, the system does not get stuck.

task - 2893608

SMS-related tests were reorganized into a dedicated area, making them easier to maintain and reducing overlap with broader mail integration tests. The update also adds new activity and performance checks, helping improve reliability and future performance work without changing day-to-day user workflows.

In this merge we introduce a new module ``test_mail_sms`` that holds the
tests for sms application, like ``test_mail`` does for mail. Currently all
sms tests are inside ``test_mail_full``. After this merge code is moved
from ``test_mail_full`` into that module. Full testing module should be used
mainly to test integrations with a lot of submodules and for performance
tests, not testing details of SMS implementation.

We also add ``mass_mailing_sms`` as dependency of ``test_mass_mailing`` so
that both mailing types are tested in the same module. It eases maintenance
and writing of tests. Mass mailing SMS tests  from `test_mail_full`` are
therefore moved in ``test_mass_mailing``.

This merge also allows some cleaning in classes used in tests, to have
classes in ``test_mail_sms`` and ``test_mail_full`` that contain everything
necessary to test mail features.

This merge also adds some additional features

  * new mail related tests;
  * new performance tests;
  * some cleanup in tools;
  * fixup in a randomly crashing test;
  * updater query counters;

See sub commits for more details.

Task-2890111 (Test Mail/Mass Mailing: SMS tests reorganization and move)

This update adds support for private bicycle reimbursement as a salary advantage for Belgian employees and adjusts how cycling days are handled in related reimbursements. It helps payroll teams apply the correct reimbursement rules and rates through July 2022.

Updates internal naming from channel partners to channel members in enterprise live chat and helpdesk live chat areas. This keeps terminology consistent across Odoo and supports smoother maintenance without changing day-to-day user workflows.

\* = mail_enterprise, website_helpdesk_livechat

Community: https://github.com/odoo/odoo/pull/95912
Upgrade: https://github.com/odoo/upgrade/pull/3681

The Sign app now continues processing valid uploaded documents even when some files cannot be read. Users receive a clearer message identifying which PDF uploads failed, making it easier to correct issues without losing successful uploads.

In sign it is possible to upload multiple files, however if one of them can't
be read, an error is raised and it's not possible to know which uploads failed.
This commit changes the way file upload is done, in order to allow clearer
messages. Single and multiple file upload is done using the same method call and
if there are failing PDFs, a message is returned to the client showing which
files failed. The choice of returning the message instead of raising an error
was intended, as we don't want to prevent further processing of the successful
files.

task-2697096

The Studio sidebar checkbox for enabling mass editing now uses the correct layout wrapper. This fixes its styling and alignment so the option appears consistently with the rest of the Studio interface.

The "Enable Mass Editing" check box wasn't wrapped with
`o_web_studio_sidebar_checkbox` so the style and the alignment of the
checkbox was wrong.

This fixes automated checks around the year picker in Documents Spreadsheet. It helps keep releases reliable by ensuring the filter panel is tested correctly, with no expected change to everyday user workflows.

Runbot-id 4096
Runbot-id 4104

This fixes an issue in Point of Sale where an order linked to a fiscal position could become impossible to delete. It helps cashiers and store managers correct mistakes more reliably during POS operations.

Part of https://github.com/odoo/odoo/pull/96090.

Internal spreadsheet tests were updated to match recent changes in how user context is handled. This helps keep automated checks reliable and reduces the risk of future spreadsheet regressions reaching users.

This fixes some tests due to changes in context handling.
Related to odoo/odoo#96161

Resizing a Knowledge article while the chatter panel is open no longer triggers an error popup. This improves stability for users editing or reviewing articles in smaller or changing browser windows.

Fix the bug where an error message would pop up when resizing the window in the
article form view with the chatter open.

`this._chatterContainerTarget` was not set up in the knowledge form renderer and
is required by the mail form renderer. This commit properly set up the target
when the chatter is rendered.

Task-2917593

Spreadsheet editing tools have been moved into a dedicated module so they can be reused outside Documents. This prepares future dashboard editing while keeping existing document spreadsheet features available through the new shared foundation.

This commit is a step toward dashboard introduction.
In order to allow the edition of the future dashboards without dependency
to `documents`, we have to extract the edition features from
`documents_spreadsheet` (pivot/list/graph insertion, side panels, ...)

So, a new module is created: `spreadsheet_edition` which contains all
theses features. `documents_spreadsheet` depends now on this module. The
plan for dashboards is to make the dashboard module dependent of this one.

Part of task-id 2799682

Stpes to reproduce the bug: - Install industry_fsm_stock - Enable Multi-Step Routes option - Create a storable product “P1”: - Routes: Buy and MTO - add any vendor - Create a SO with the product “P1” and confirm it - Go to the created PO and confirm it - Ensure Marc Demo’s access right is set to - Sale: Own User documents - Inventory: Administrator - Connect as Marc Demo - Go to inventory and attempt to validate the receipt of the purchase order Problem: User a

Stpes to reproduce the bug:
- Install industry_fsm_stock
- Enable Multi-Step Routes option
- Create a storable product “P1”:
    - Routes: Buy and MTO
    - add any vendor

- Create a SO with the product “P1” and confirm it
- Go to the created PO and confirm it
- Ensure Marc Demo’s access right is set to
    - Sale: Own User documents
    - Inventory: Administrator
- Connect as Marc Demo
- Go to inventory and attempt to validate the receipt of the purchase
order

Problem:
User access error, with the user Marc, we try to access a sale order
line created by another user, whereas Marc only has access to his own SO

Solution:
If a user has access to inventory, he is supposed to be able to validate
a transfer without error, so we must read the SO line as a superuser

opw-2904462

Forward-Port-Of: odoo/enterprise#29444

In the case of intrastat, there is a specific vat code used when the vat code is unknown. This code is QV999999999999. At present this code is not being used, except when the country_id is not set on the partner. This commit generalises the use of the unknown vat code so that, if the vat on the partner is not set, the unknown vat code is used. task-id: 2894443 Forward-Port-Of: odoo/enterprise#29561 Forward-Port-Of: odoo/enterprise#28853

In the case of intrastat, there is a specific vat code used when the vat
code is unknown. This code is QV999999999999. At present this code is
not being used, except when the country_id is not set on the partner.
This commit generalises the use of the unknown vat code so that, if the
vat on the partner is not set, the unknown vat code is used.

task-id: 2894443

Forward-Port-Of: odoo/enterprise#29561
Forward-Port-Of: odoo/enterprise#28853