This update enhances Odoo's ability to convert and map domain values, streamlining data filtering within key modules. The change simplifies a previous design restriction, making the system more flexible and efficient. This improves reporting and data management capabilities.

As PR #238734 changed `filter_domain_leaf()` to take only one function to both map and filter the domain (instead of a function to filter and a dict to map, which was too restrictive), and renamed it to the more explicit `filter_map_domain()`, parts using `filter_domain_leaf()` had to be changed to fit the new function prototype.

task-5379826

This update simplifies the dashboard editing experience by renaming the 'Edit' button to 'Edit in Spreadsheet'. With recent changes to dashboard creation, the associated 'Add a spreadsheet' button and related elements have been removed to streamline the workflow. This change improves user understanding and consistency.

### Description

- Rename the dashboard edit button to "Edit in Spreadsheet" for improved clarity and consistency with the dashboard editing workflow.

- As the form view for the spreadsheet dashboard group has been removed and users can now create dashboards using the New button, remove the "Add a spreadsheet" button from the list view, along with its related tours and tests.

Task: [5259227](https://www.odoo.com/odoo/project/2328/tasks/5259227)

This update resolves an issue where clicking 'Send' in a Sign Request wizard incorrectly redirected users to the signing interface when the sender was also a signer. The fix ensures that clicking 'Send' now correctly closes the wizard, streamlining the signing process for all users.

When creating a Sign Request where the sender is also one of the signers, clicking Send in the wizard incorrectly redirected to the document preview/signing interface. This fix ensures that clicking Send always closes the wizard and does not trigger any redirect, regardless of the sender’s signer status.

task-5408155

Forward-Port-Of: odoo/enterprise#101816

This update resolves an issue where requests to the IoT box for customer display functionality were failing due to incorrect data formatting. The PR corrects this formatting, ensuring the IoT box receives the necessary information to display customer data properly. This improves the reliability of the customer display feature.

Currently the requests sent to the iot box to use customer display cause and error because of the bad format of the data in the request. This PR formats the data correctly to be sent to the iot box

The compatibility for webrtc for the iot boxes in 19.1 isn't necessary as webrtc was removed in 19.1

task-5408081

Forward-Port-Of: odoo/enterprise#101821

This update resolves a technical issue preventing PoS sessions linked to Fiskaly from closing correctly when cash in/out entries had reason names exceeding 40 characters. The change ensures all reason names are truncated to meet Fiskaly's requirements, preventing errors and maintaining proper integration with this payment processing system. This improves the reliability of our German Point of Sale functionality.

Before this change, closing a PoS session linked to Fiskaly would fail if a cash in/out entry had a reason exceeding 40 characters. Fiskaly returned: "body/cash_statement/business_cases/2/name must NOT have more than 40 characters". This commit ensures reason names are truncated to comply with Fiskaly's schema.

opw-5208191

Forward-Port-Of: odoo/enterprise#98853

This update resolves an issue that occurred when users attempted to duplicate transactions through the account module. Specifically, the system would throw an error if no journal was associated with the duplication process. The fix ensures a valid command is used when a journal is missing, preventing the error and improving stability.

Currently, an error occurs when user opens the `account.duplicate.transaction.wizard.form` view and saves it.

**Steps to Reproduce:**

 - Install the `account_accountant` module.
 - Using `Open View`, open the `account.duplicate.transaction.wizard` view > enter the start date, and save..

`ValueError: Compute method failed to assign account.duplicate.transaction.wizard(22,).provider_duplicate_ids`

The error occurs because when the view is opened and saved, the _compute_provider_duplicate_ids method is triggered. Since no journal is linked to the wizard, the method assigns an empty list ([]) to provider_duplicate_ids [1]. Because this is a O2M field, assigning a raw empty list is invalid and causes the error.

This commit ensures that when journal is missing, instead of assigning an empty list ([]), a valid relational command `([Command.set([])])` is used.

Ref: https://github.com/odoo/enterprise/pull/97196/commits/c109e0bcce20f14b6dbd3d28e61b135f1fd048f2

[1] https://github.com/odoo/enterprise/blob/d808ad3f6ff52632e00cf1a68de0e5270e52895d/account_online_synchronization/wizard/account_journal_duplicate_transactions.py#L53

sentry-7080686084

Forward-Port-Of: odoo/enterprise#101177

A recent test failure related to task scheduling time zones has been corrected. The fix ensures that task planning uses UTC time, preventing inaccurate date calculations and ensuring consistent scheduling across different time zones. This resolves a potential issue impacting task planning accuracy.

The test `test_plan_task_in_calendar` failed with a one-hour difference in `planned_date_begin`.

The error occurred because the work intervals were computed using the resource's timezone (`Europe/Brussels`) instead of `UTC`, leading to a shifted planned date.

Setting the resource timezone to `UTC` ensures consistent interval computation and resolves the test failure.

[RB-227059](https://runbot.odoo.com/odoo/error/227059)

Forward-Port-Of: odoo/enterprise#100580

This update fixes an issue where the Quality Control module's list view was incorrectly loading data. The system has been reverted to using the correct view definition, ensuring accurate display of control points when accessing the Quality Control section. This ensures the Quality Control functionality operates as intended.

Since odoo/enterprise#94012, when loading the quality.point list view from the main menu, `quality_point_routing_view_tree` is used instead of `quality_point_view_tree`. This is not correct.

To reproduce :
 - Install quality_control and mrp_workorder
 - In Quality Module, go to Quality Control / Control Points

[opw-5253899](https://www.odoo.com/odoo/project/966/tasks/5253899)

Forward-Port-Of: odoo/enterprise#101098

This update corrects a bug in the Belgian payroll module that prevented a minimum wage warning from appearing when an employee record lacked a job assignment. The fix removes a redundant condition within the payroll calculation, ensuring the warning is displayed correctly for all employee types. This ensures accurate payroll reporting for Belgian companies.

Steps to reproduce:

- Open an employee on the Employees app for a Belgian company
- On the payroll tab, set the salary to lower than the minimum wage for an employee that has no job
- The warning will not show unless the employee has a job set to him

Cause of the bug:

- Condition inside _compute_l10n_be_is_below_scale function returned false if an employee had no job

Fix done:

- Removed unneccessary condition

task-5424012

This update fixes a visual issue in the Swiss Master Data Report, specifically the PDF visualization and list view formatting. The changes remove a comma from the 'Year' field display and update the display names of report entries, ensuring accurate and professional reporting for Swiss payroll data.

. Corrected the generated Wage Type Report PDF visualization by modifying the external layout

. Fixed the Year field display in the list view: removed the comma

. Updated the display name of record "Month + Year"

task-5130155

This update corrects a bug in the Belgian payroll module that prevented a minimum wage warning from appearing when an employee record lacked a job assignment. The fix removes a redundant condition within the payroll calculation, ensuring the warning is displayed correctly for all employee types. This ensures accurate payroll reporting for Belgian companies.

Steps to reproduce:

- Open an employee on the Employees app for a Belgian company
- On the payroll tab, set the salary to lower than the minimum wage for an employee that has no job
- The warning will not show unless the employee has a job set to him

Cause of the bug:

- Condition inside _compute_l10n_be_is_below_scale function returned false if an employee had no job

Fix done:

- Removed unneccessary condition

task-5424012

This update resolves a technical issue within the Enterprise edition's spreadsheet functionality. Specifically, a missing configuration setting was preventing proper sheet identification, which could have caused errors when creating or managing spreadsheets. This fix ensures the spreadsheet feature operates reliably for all users.

…SHEET command

This update fixes a minor issue where the live chat window wasn't consistently opening in the user's current browser tab. The change ensures that when a user initiates a chat, the window automatically appears in their browser, improving the user experience and streamlining communication.

task-5408790

https://github.com/odoo/odoo/pull/240384