This fixes a recent issue that caused automated checks to fail when web views handled monetary and date fields. It helps keep the user interface stable and prevents disruptions from incompatible field types.

Build errors in click all since #183882:
see: https://runbot.odoo.com/runbot/build/70474087
build-error: 106152

A field used for links in the base system profiling area now uses the right format so URL links display and behave correctly. This helps users open related links reliably without changing business workflows.

This commit, change the field type from text to char to correctly use the url widget.

This fixes how certain money and date fields are handled in approval requests and rental sales orders. It helps ensure users see and enter these values consistently, reducing confusion and potential mistakes in day-to-day workflows.

This update renames internal unit-of-measure fields so sales, purchasing, pricing, and reporting records use consistent naming. The change reduces custom workarounds and makes future shared processes, such as EDI handling, easier to build and maintain without changing day-to-day business workflows.

Purpose of this PR to have name of field according to guidelines so it
can be consistent with other models and we don't have to add some hacks
if they are not like in invoice lines `product_uom_id` is properly named
according to guidelines and in other modules it's not so if we want to
add generic method which will work for invoice lines and sale order lines
then we have to remove `product_uom_id` from data and add `product_uom`
and it can get ugly if we want to do more complex operations.

This commit rename field `product_uom` on SOL to `product_uom_id` to be
consistent with other models specifically with `account.move.line` in order
to properly extract common logic from EDI for invoice and have consistent
name across file so it'll make future code simpler.

We also have to change purchase line `product_uom` field to `product_uom_id`
because in generic accounting code they create sale or purchase order
depending on condition so Sale order line and Purchase order line should
have same field names also there is task to add EDI import for purchase
order 4286172 so it can be useful for that task also

Following uom field names updated to follow guideline and proper naming:
(Related to SOL and POL `product_uom` field)
- Rename `product_uom` to `product_uom_id` in {`sale.order.line`,
`purchase.order.line`, `sale.report`, `purchase.report`  , `project.milestone` ,
`product.supplierinfo`}   models.
- Rename `product.pricelist.item` model's field `product_uom` to
`product_uom_name` as it was related to product's `uom_name` field and
it was char type field.

task-4206350

See also:
https://github.com/odoo/enterprise/pull/73293
https://github.com/odoo/upgrade/pull/6732

This update reorganizes internal test helper tools and clarifies their naming so development teams can write and maintain automated tests more reliably. It also fixes timing and service-mocking issues that could cause small inconsistencies in test results, reducing noise and improving confidence in quality checks.

This PR moves some helper functions away from the main
'web_test_helpers' file and rename the `step` and `assertStep` functions
to reduce confusion.

Enterprise: https://github.com/odoo/enterprise/pull/73569

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

This update aligns enterprise modules with a broader naming cleanup by changing product unit references to a clearer, consistent field name. It reduces technical inconsistency across sales, rental, subscription, delivery, field service, purchasing, stock, and accounting-related workflows without changing business functionality.

This commit adept changes done in community PR to rename
`product_uom` field to `product_uom_id` also rename
related fields in following models:
- sale.subscription.report
- sale.rental.schedule
- sale.rental.report

task-4206350

See also:
https://github.com/odoo/odoo/pull/186250
https://github.com/odoo/upgrade/pull/6732

This update reorganizes and renames internal testing helper functions so automated tests are easier to understand and maintain. It affects test code only, helping developers reduce confusion without changing business workflows or user-facing behavior.

This PR moves some helper functions away from the main
'web_test_helpers' file and rename the step and assertStep functions
to reduce confusion.

Community: https://github.com/odoo/odoo/pull/186636

This draft change appears to reorganize internal code and automated walkthroughs for field service reporting, external tax sales flows, and document signing. It is not expected to change day-to-day behavior for users, but should help keep these areas easier to maintain and test.

Debugging websocket can be tough as we don't know when a session is downgraded. Some messages can be received, giving the impression that everything is working fine while the socket is actually linked to a public user. This PR introduces some logs to help debugging this scenario. opw-4218953 Forward-Port-Of: odoo/odoo#186911

Debugging websocket can be tough as we don't know
when a session is downgraded. Some messages can be
received, giving the impression that everything is
working fine while the socket is actually linked to
a public user.

This PR introduces some logs to help debugging this
scenario.

opw-4218953

Forward-Port-Of: odoo/odoo#186911

Fix a failing test that was incorrectly patching a class method, instead of patching the base object. Indeed, before this fix the test was only patching `account_edi_ubl_cii._get_ubl_cii_formats_info()` and not extensions such as `l10n_ro_edi._get_ubl_cii_formats_info()`). Therefore extensions could add data to the returned value of the method, and could make the test fail. Related runbot error id: 104916 task-no Forward-Port-Of: odoo/odoo#186935

Fix a failing test that was incorrectly patching a class method, instead of patching
the base object.
Indeed, before this fix the test was only patching
`account_edi_ubl_cii._get_ubl_cii_formats_info()` and not extensions such as
`l10n_ro_edi._get_ubl_cii_formats_info()`).
Therefore extensions could add data to the returned value of the method, and
could make the test fail.

Related runbot error id: 104916
task-no

Forward-Port-Of: odoo/odoo#186935

Steps to reproduce ================== - Use a mobile device - Enable analytic accounting - Go to Expenses - Open a record - Click on the analytic field - Search more on the project - Click on the search input => The popup closes Cause of the issue ================== There is a resize handler that closes the popup. When the keyboard appears, the window is resized to reserve space for it Solution ======== Dont close the popup when we are using a mobile OS opw-4174514

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

- Use a mobile device
- Enable analytic accounting
- Go to Expenses
- Open a record
- Click on the analytic field
- Search more on the project
- Click on the search input

=> The popup closes

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

There is a resize handler that closes the popup.
When the keyboard appears, the window is resized to reserve space for it

Solution
========

Dont close the popup when we are using a mobile OS

opw-4174514

Forward-Port-Of: odoo/odoo#186606

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-pr Forward-Port-Of: odoo/odoo#186456

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-pr

Forward-Port-Of: odoo/odoo#186456

Add a check on adyen callback when paying. Verify if the pending payment line exist before processing the callback. opw-4242322 Forward-Port-Of: odoo/odoo#186842 Forward-Port-Of: odoo/odoo#186580

Add a check on adyen callback when paying. Verify if the pending payment line exist before processing the callback.

opw-4242322

Forward-Port-Of: odoo/odoo#186842
Forward-Port-Of: odoo/odoo#186580

In large database, the compute of the field l10n_it_payment_method and l10n_it_document_type can raise a timeout. Step to reproduce: - On a large database (tested with +10M account.move), try to install the module l10n_it_edi_ndd - The installation will raise a timeout New behavior: The fields l10n_it_payment_method and l10n_it_document_type will no longer be computed during module installation. This will avoid the timeout. opw-4273165 Forward-Port-Of: odoo/odoo#186847 Forward

In large database, the compute of the field l10n_it_payment_method and
l10n_it_document_type can raise a timeout.

Step to reproduce:
- On a large database (tested with +10M account.move), try to install
  the module l10n_it_edi_ndd
- The installation will raise a timeout

New behavior:
The fields l10n_it_payment_method and l10n_it_document_type will no
longer be computed during module installation. This will avoid the
timeout.

opw-4273165

Forward-Port-Of: odoo/odoo#186847
Forward-Port-Of: odoo/odoo#185266

Before this commit, when loading the data for the point of sale, all the uom categories were not being loaded due to a wrong domain declaration. The domain was comparing uom categories ids with uom ids, which is wrong. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#185843 Forward-Port-Of: odoo/odoo#185807

Before this commit, when loading the data for the point of sale, all the uom categories were not being loaded due to a wrong domain declaration. The domain was comparing uom categories ids with uom ids, which is wrong.

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

Forward-Port-Of: odoo/odoo#185843
Forward-Port-Of: odoo/odoo#185807

There was `opacity-0` on muted item, but due to `opacity-50` being mistakenly present at all time, it had precedence over the `opacity-0` thus the unread indicator was always visible.  Forward-Port-Of: odoo/odoo#186843

There was `opacity-0` on muted item, but due to `opacity-50` being mistakenly present at all time, it had precedence over the `opacity-0` thus the unread indicator was always visible.

![Screenshot 2024-11-08 at 19 10 03](https://github.com/user-attachments/assets/f7253df8-c3e9-46e6-a109-114370a9de7d)

Forward-Port-Of: odoo/odoo#186843

Opening the corporate tax report more than once resulted in an error, making it impossible to open the report. The reason for this was an undefined comparison filter when opening the report for the second time. This was a result of setting the export mode to `file` when opening the report, which in turn makes the comparison undefined. This commit fixes this by temporarily setting the export mode to `file` when creating the entry. ticket: https://www.odoo.com/odoo/project/49/tasks/4288546 For

Opening the corporate tax report more than once resulted in an error, making it impossible to open the report. The reason for this was an undefined comparison filter when opening the report for the second time. This was a result of setting the export mode to `file` when opening the report, which in turn makes the comparison undefined. This commit fixes this by temporarily setting the export mode to `file` when creating the entry.

ticket: https://www.odoo.com/odoo/project/49/tasks/4288546

Forward-Port-Of: odoo/enterprise#73644

1. When an applicant (who doesn't have an employee record yet) signs a contract their name is shown as `simulation employee` instead of their actual name. 2. Dependent benefits are visible although the mandatory benefits aren't selected. For example: the dialog box showing the number of insured children under ambulatory insurance is visible although the abulatory insurance isn't selected on the salary configurator. 3. The dropdown menus on the salary configurator have a grey color which ma

1. When an applicant (who doesn't have an employee record yet) signs a contract their name is shown as `simulation employee` instead of their actual name.

2. Dependent benefits are visible although the mandatory benefits aren't selected. For example: the dialog box showing the number of insured children under ambulatory insurance is visible although the abulatory insurance isn't selected on the salary configurator.

3. The dropdown menus on the salary configurator have a grey color which makes the user think that they aren't editable.

These changes fixes the above issues.

task-4280657

Forward-Port-Of: odoo/enterprise#73000

Purpose ======= Create a new group, so admin don't see all document by default. Task-4313355 Forward-Port-Of: odoo/enterprise#73372

Purpose
=======
Create a new group, so admin don't see all document by default.

Task-4313355

Forward-Port-Of: odoo/enterprise#73372

The tour is failing because the test folder ("Folder1") is not always selected when starting the test with its access token. As the test is checking the folder deletion, we select the test folder manually by clicking on it. Task-4247011 Forward-Port-Of: odoo/enterprise#71653

The tour is failing because the test folder ("Folder1") is not always selected when starting the test with its access token. As the test is checking the folder deletion, we select the test folder manually by clicking on it.

Task-4247011

Forward-Port-Of: odoo/enterprise#71653

The test was using a common class from website while not depending on the module and turns out the class was not necessary. Runbot Error 69687 Forward-Port-Of: odoo/enterprise#73377

The test was using a common class from website while not depending on the module and turns out the class was not necessary.

Runbot Error 69687

Forward-Port-Of: odoo/enterprise#73377

Before this commit : - Glovo was selected as default delivery provider. - Extra Dot(Bullet Point) is visible in the Order notes  - Label to be changed under Food delivery connector field. Following this commit : - Default delivery provider is removed. - Extra dot is been removed in order notes. - Label is been updated to Food Delivery Platforms. task - 4315841 Forward-Port-Of: odoo/enterprise#73553

Before this commit :
- Glovo was selected as default delivery provider.
- Extra Dot(Bullet Point) is visible in the Order notes 
-  Label to be changed under Food delivery connector field.

Following this commit :
- Default delivery provider is removed.
- Extra dot is been removed in order notes.
- Label is been updated to Food Delivery Platforms.

task - 4315841

Forward-Port-Of: odoo/enterprise#73553

When the appointment duration is not a multiple of hours, ex: 2 hour 30 minutes it is not able to fit in one line. Thus change appointment duration format to short when duration exceeds a day or is not a multiple of an hour. And some other UI/UX changes. Task-4209912 Forward-Port-Of: odoo/enterprise#70645

When the appointment duration is not a multiple of hours, ex: 2 hour 30 minutes it is not able to fit in one line. Thus change appointment duration format to short when duration exceeds a day or is not a multiple of an hour.

And some other UI/UX changes.

Task-4209912

Forward-Port-Of: odoo/enterprise#70645

Limit calendar view to show only dates within the currently selected month. Task-4294202 Forward-Port-Of: odoo/enterprise#73637

Limit calendar view to show only dates within the currently selected month.

Task-4294202

Forward-Port-Of: odoo/enterprise#73637