This fixes an error that could occur when Viva Wallet payment responses were sent to the point of sale. The change helps ensure payment updates reach the POS reliably without disrupting the cashier workflow.

With commit [1], we removed the method ``_get_bus_channel_name``, but at
line [2], it's still referenced, which causes an error.

AttributeError:
``'pos.session' object has no attribute '_get_bus_channel_name'``

This commit will fix the issue by using ``_notify`` for calling the notification
bus.

[1]-https://github.com/odoo/odoo/commit/3836aad466c6c111f0f0d33c357a1c7a5150f3fd
[2]-https://github.com/odoo/odoo/blob/5633d590decc6e8989c0f454a355e965f072f967/addons/pos_viva_wallet/models/pos_payment_method.py#L133

sentry-5562979975

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

This fix prevents manufacturing order overviews from crashing when the same product is configured as both a component and a by-product in a bill of materials. Users will now be protected from a setup that could trigger an endless processing loop, improving reliability when reviewing manufacturing orders.

Steps to reproduce:
- Manufacturing > Products > Bills of Material > New
- Add any item as component then the same item as by-product
- Confirm
- Operations > Manufacturing Order > New
- Pick the product associated to your newly created BoM
- Confirm > Overview

What happens and why:
Odoo raises an RPC error due to an infinite recursion between _get_components_data and _get_replenishment_lines. Both calls are made before the manufacturing order line is flagged as processed so the functions are mutually dependent on the other finishing first.
The looping call is conditionally called when document_in and document_out are the same, which seems to be why the stock moves 'move_in' (component) and 'move_out' (by-product) need to be configured this way on the BoM.

Why is this an error:
This prevents the user from accessing the overview of a valid MO.

What this fix does:
Moves the flag to before the looping call can be made, so the recursive call does not propagate infinitely.

opw-4013371

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Specialized views such as cohort, grid, and map are now loaded only when needed, including in Studio. This reduces the initial loading work for users and should make opening the backend feel faster while keeping those views available when required.

We make studio to load the bundle "web.assets_backend_lazy" defined in https://github.com/odoo/odoo/pull/171073.
Thanks to that changes we are able to make the views cohort, grid, map and their extensions to be lazy loaded.

Task ID: `3546321`

WhatsApp conversations now continue in the existing channel when the same customer replies to templates sent by the same user, even if those templates are linked to different records. This avoids duplicate conversations and keeps customer communication easier to follow.

\* test_whatsapp

**PURPOSE:**

Currently if a channel is active on WhatsApp and the same user send a template using another model than on further conversation a new channel created. For the same user it does not make any use case.

**SPECIFICATION:**

If user sends a template and Customer / subscriber replies to that a channel is created and conversation is active.
After that a new template is send by the current user, post this if the customer replies it should not create a new channel and the conversation should continue in the same channel.

**task**-[3644180](https://www.odoo.com/web#id=3644180&menu_id=4720&cids=2&action=333&active_id=965&model=project.task&view_type=form)

Bank reconciliation now uses a saved action setup instead of temporary page state. This prevents reconciliation screens from losing context when users refresh the page or open links in a new tab.

Created an XML record for the bank reconciliation action. The created record was used in '_action_open_bank_reconciliation_widget' instead of a dictionary action.

Before this commit, the action state, which was not entirely encoded in the new URL, would be erased on refresh or on opening the reconciliation link in a new tab. Currently, the action state is stored in an XML record to avoid this problem.

task-4010694

The update aligns Enterprise screens with related community improvements and refreshes print-related controls in Gantt and Documents. Business users should see a more consistent interface when preparing or printing planning and document views.

community:
- https://github.com/odoo/odoo/pull/167747


task-3617770

List views in Studio, Helpdesk, and Appraisal were adjusted to work with updated column width behavior. This reduces unwanted horizontal scrolling and makes important list information display more consistently.

Users can now open individual payments from a batch payment directly in the main window instead of a limited pop-up. This makes important payment status information visible and improves navigation while keeping the payment list itself read-only to avoid accidental edits.

When inside a batch payment form view there is a O2M field `payment_ids` which when clicked is opening the payment form view inside a dialog.

The issue with that is that since [1], stat buttons were excluded from dialogs because in some flows, it was creating issues in the user flow, particularly in cases involving intermediary records that were not yet saved yet.

But in the batch payments form view, when clicking on a payment, it's important to see those stats buttons, otherwise it leads to bad UX and make people waste time.

This commit is making it so there is a "View" button appearing on the payment lines which will open the form view in the current window, adding itself to the breadcrumb.

It's possible since commit [2] but sadly for it to work the list need to be editable, which this commit is thus changing too.

The fields could receive a `readonly` attribute is judged necessary.

[1]: https://github.com/odoo/odoo/commit/473e629a099bfd4b5334951a54df48e37c8612c7
[2]: https://github.com/odoo/odoo/commit/258e6a019a21042bf4f6cf70fcce386d37afd50c

task-3973116

The Rooms app now guides new users more clearly when no rooms have been created yet. It shows a helpful prompt with a direct button to create the first room, making initial setup faster and less confusing.

Purpose
=======
Streamline the setup process for new users of the Rooms app.

Specification
=============
When there are no rooms, the action helper is visible with a button to create a new room.

Task-3927822

This update adds the ability to export Czech tax reports in XML format, making it easier for businesses to submit tax information to authorities in the required format. The feature streamlines tax compliance for companies operating in the Czech Republic by automating the export process.

Added XML export options of the czech tax report.
Most of the work in here was copied from the previous xml export implemented in this commit: https://github.com/odoo-dev/enterprise/commit/32c9a215a74123a2bf7f984421c729c89318e300

task-3127683

Belgium's tax authorities now require pro rata deduction to be included in VAT exports. This update adds the mandatory pro rata field to the VAT export wizard for businesses that qualify. A new module has been created to support this additional functionality in the export process.

Belgium now asks the pro rata deduction for the VAT export. 
Mandatory if the business is concerned.
Added new module to be able to add fields to the wizard.

task-3916995

Forward-Port-Of: odoo/enterprise#66171
Forward-Port-Of: odoo/enterprise#65442

The IoT module now loads the websocket connection information during the initial page load instead of making a separate request each time a view opens. This improves performance by reducing unnecessary network calls and provides a faster, smoother user experience when working with IoT devices.

`IoTWebsocketService` was making an RPC call every time the view loaded.  
Now, we load it in the session_info to provide it to the view while rendering html.

Task: 4037030

This update removes unnecessary action buttons that opened journal items from the GST Return Period report sections. By eliminating these extra actions, the GST return reporting process is now more focused and efficient, reducing clutter and helping users concentrate on the essential information they need.

With this PR, the actions to open all journal items have been removed from all GSTR sections of the GST return Period.

This change helps streamline the GST Return by eliminating unnecessary actions, ensuring a more focused and efficient reporting process.

**task**-3908555

This update improves how GST tax reports handle point of sale transactions in India by automatically setting the Place of Supply information on general journals when it's missing. The changes also fix issues with missing point of sale details in GST return reports, ensuring more accurate tax compliance reporting for Indian businesses.

In this PR:
- Set Place of Supply on 'general' journals with POS sessions if a country is
India and Place of Supply are not set.
- Adjusted state ID computation for account moves with POS sessions.
- Fixed handling of missing POS line details in GST return period report.


Task ID: 3935317

This fix ensures that sales order totals are correctly recalculated whenever tax rounding method settings are changed. Previously, the total amount displayed in list views would not update to reflect the new rounding method, even though the order form would show the correct amount. This resolves inconsistencies in how order totals are displayed across different views.

Steps to reproduce:
- Install "Sales" and "Accounting"
- Make a sale order with two order lines:
    - Product with price of 10.5 and tax of 7%
    - Product with price of 10.99 and tax of 7%
- Total will now depends on rounding_method used (22.99 as total or
  23.00)

Issues:
If you change the settings the total will be updated on the sale order
since it's computed by JS code however on the list view the field
`amount_total` will show the previous value. This is because the compute
is not triggered after changing the rounding method as it's missing in
it's dependencies.

opw-4035724

This update corrects how service accounts and export accounts are categorized in Chile's F29 tax report. The fix ensures services are properly included in the VAT base calculation and exports are correctly mapped to the exempt base, improving the accuracy of tax reporting for Chilean businesses.

vat base and change exempt base to exports account.

Fixed an issue in the Barcode app where scanning GS1 barcodes containing both packaging information and weight was calculating incorrect quantities. When a product uses Units as its measurement, the weight information is now properly ignored and only the packaging quantity is used, preventing incorrect multiplication of quantities.

Issue
=====

When a GS1 barcode contains both a packaging and a weight, the quantity is wrong because we use the weight as the quantity and multiply it by the packaging quantity.

How to reproduce
================

- Enable "Product Packagings" and "Units of Measure";
- Select GS1 nomenclature as the Barcode Nomenclature;
- Create a product with a packaging for multiple quantity (e.g.: 4 Units) and with a valid GTIN (e.g.: 12345600012349);
- In the Barcode app, create a new receipt;
- Scan a GS1 barcode containing both the packaging barcode and a weight (e.g.: 10123456000123493103001500) => The scanned weight is used as the quantity and is multiplied by the packaging quantity (in this example, the quantity will be 6, because 4 units x 1.5 kg = 6 units)

Expected Behavior
=================

Since the associated product uses Units as UoM, the scanned weight can't be converted into quantity (we can't convert g or kg into units), so this information should be ignored and the packaging quantity should be used alone instead.

Note that the packaging quantity will still multiply the scanned quantity if the share the same UoM category. This behavior is still supported to be able to scan multiple packagings at once. That said, this use case make sense for products using Units only.

[OPW-3988826](https://www.odoo.com/odoo/11258/tasks/3988826?cids=1)

Forward-Port-Of: odoo/enterprise#65073

This update removes action buttons that were incorrectly appearing on grouped summary lines in financial reports. When reports use prefix grouping to organize data, buttons now only appear on actual data lines where they can perform meaningful actions, preventing errors or unintended record creation when users click buttons on group headers.

*l10n_account_customer_statements,l10n_my_reports,l10n_us_reports

Currently some reports add buttons on their lines to perform some action on them. However, when prefix groups are used, the buttons are also shown on these lines, but refer to nothing and will thus either cause an error when clicked or lead to a new record.

This commit fixes that by providing a generic hook in the `line_name` template to inject buttons. This generic hook checks whether the line is a prefix group line and doesn't render the buttons if it is.

All other reports were adapted to use this hook now.

task-3932945

Fixed an issue where sample values in the WhatsApp Composer were not updating when users changed the WhatsApp template. Previously, the composer would display sample values from the initially selected template instead of reflecting the newly chosen template. This fix ensures that sample values now correctly update whenever a different template is selected, improving the user experience when composing WhatsApp messages.

## Before this PR
In WhatsApp Composer, the Sample Values do not update when changing the WhatsApp Template. Instead, it display the sample values from the initially selected template.

## After this PR
The Sample Values will now update according to the selected WhatsApp Template.

Task-3996935