Archived Knowledge articles are no longer reachable through shared article links, helping ensure users only see content that should be available. The update also hides actions that do not apply to archived articles and makes the public not-found message clearer.

The method _fetch_article was using browse instead of search. That means that
archived articles could be retrieved when accessing the route of the article.

As we don't make any difference between Forbidden and Not Found error, this
commit replaces the browse by search method that will automatically check access
rules but also filter out archived articles.

Task-2950423

Helpdesk teams can now add customizable properties to tickets, making it easier to adapt ticket workflows to each team's needs. Supporting spreadsheet-related changes move a model selection tool into a shared area so the new properties feature can work securely across relevant apps.

Purpose
=======
Add a properties field to allow to customize the helpdesk work flows

Task-2852259

The payroll contract list view has been modernized to use Odoo's newer interface framework. This should help keep the payroll experience consistent and easier to maintain, with limited visible change for day-to-day users.

Convert hr_contract_tree list view to owl

task-2954524

This update reorganizes Inventory reporting menus with clearer naming, removes an obsolete forecasted inventory report, and consolidates duplicate Purchase reporting entries. Users should see a cleaner reporting experience with less confusion and fewer overlapping menu options.

Enterprise branch of COM PR: odoo/odoo#97109 (i.e. many small back2basics changes):
Upgrade PR: https://github.com/odoo/upgrade/pull/3819

---

[IMP] stock_enterprise: update inventory menus

Enterprise equivalent of menu renaming/reordering for "Reporting":
 - rename Warehouse Analysis => Performance and place at bottom of menu
   dropdown (i.e. this view aggregates all Warehouses together => name
   could be better)

"menu" part of b2b task: 2882539

---

[IMP] purchase_enterprise: remove duplicated reporting menuitem

The existing "Purchase > Reporting > Purchase" showed the same thing as
the "Purchase > Reporting > Dashboard" menuitem with the exception of
view order and filtering. Therefore we merge them into one by letting
Odoo do the name/order/filter replacing via inheritance.

"other" part of b2b task: 2882539

---

[REM] stock_enterprise: remove Forecasted Inventory view

The Forecasted Inventory view has become obsolete, this is the
equivalent enterprise code deletion of the community removal.

"forecast inventory" part of b2b task: 2882539
Upgrade PR: https://github.com/odoo/upgrade/pull/3819

This update removes an older, little-used way of controlling who sees parts of backend screens and replaces it with a clearer approach. The change simplifies future development and enables better performance by making screen layouts easier to cache.

The goal of this revision is to get rid of the `groups_id` field of the model `ir.ui.view`.

- This feature wasn't really known or used by most developers,
   and not straight-forward to understand.
   Removing it allows one less complicated thing to learn for developers.
   Besides, thanks to odoo/odoo#95729,
   changing the behavior of the `groups=` attribute, 
   we can easily get rid of this `groups_id` feature
   by simply adding `groups=` in the elements of the views
   using the `groups_id` field, it will have the same effect:
   adding the elements in the view only for the users part of the specified group.

- By getting rid of the groups_id many2many field on ir.ui.view,
   it makes possible to cache the view architecture without
   requiring to use the groups in the cache key.
   Currently, if we want to cache the view architecture,
  it would be required to use the intersection of the user
  groups with the groups_id groups of the view,
  making it costly to compute the cache key,
  therefore altering the performance point to cache the view
  architectures.

The data cleaning and data merge list screens have been updated to a newer interface framework. This keeps these tools aligned with the rest of Odoo, improving maintainability and supporting a more consistent user experience over time.

New validation prevents creating account records or templates with codes that the reporting engine cannot process. This reduces the risk of accounting reports failing because of unsupported characters in account codes.

The new account report engine requires account codes to only contain
alphanumeric characters and dots.
(see https://github.com/odoo/enterprise/blob/f435654f70f3d6a1fec7fa696945f2c0eb9a7056/account_reports/models/account_report.py#L2523)
Add two new constrains on account_account and account_account_template
to block the creation of accounts with codes that would cause issues
in account reports.

Task id #2960486

Account codes are now restricted to letters, numbers, and dots so they work reliably with the newer reporting engine. This helps prevent report failures caused by unsupported characters when users create or configure accounts.

The new account report engine requires account codes to only contain
alphanumeric characters and dots.
(see https://github.com/odoo/enterprise/blob/f435654f70f3d6a1fec7fa696945f2c0eb9a7056/account_reports/models/account_report.py#L2523)
Add two new constrains on account_account and account_account_template
to block the creation of accounts with codes that would cause issues
in account reports.

Task id #2960486

This update removes an unused internal method from the asset accounting area. It has no expected day-to-day impact for users, but it simplifies maintenance and reduces obsolete code in the system.

Follow up on 6cb107c42c1e3a679f7c7b2f41466f39d042bd16

Method `create_asset_move` is not called from anywhere.

A signing workflow test was updated so it continues to work after a small change to the copy button layout. This helps keep automated checks reliable and prevents false test failures, with no expected change for end users.

This commit follows community fix in PR odoo/odoo#98340. The tour
test fails without this change as the CopyButton component
now uses one more div in its template.

This fix removes fragile internal dependencies that could cause issues when payroll or electronic stock document records were searched or processed. It helps keep related HR payroll and localization workflows more stable without changing day-to-day user behavior.

Companion of https://github.com/odoo/odoo/pull/98562

The settings page no longer allows swipe actions on large screens, preventing accidental or unintended behavior for desktop users. Swipe behavior remains available on smaller mobile screens where it is appropriate, with tests added to protect this behavior.

This commit fixes the settings form view. Since its
Owl conversion, the ActionSwiper component is used
in the template. Before this commit, it was used even
when we don't want the settings to allow the swipe.

It now only activate the swipe behavior on smaller
screens

This fix ensures that cash-basis tax reporting labels are correctly carried into journal entries created during bank reconciliation with manual tax operations. It helps accounting teams keep tax reports accurate and avoids missing tax information after reconciliation.

Have a CABA tax
Create a Bank statement with a line
Reconcile with manual operation adding the CABA tax

After reconciliation check the journal entries: the tags will be missing

opw-2865789

X-original-commit: 2b2735d0eff809b26002ef7cb34e662aa5a0c2ad

The Chilean electronic receipts module no longer includes the daily sales book because it is no longer legally required. This simplifies related scheduled tasks, views, templates, permissions, and translations, while also refreshing outdated module icons.

[RM][WIP] l10n_cl_edi_boletas: removal of daily sales book (to test)
[FIX] l10n_cl_edi, l10n_cl_edi_boletas, l10n_cl_edi_stock: removal of old icon

This update adapts the Documents and Appraisal Skills areas to recent platform changes that make list and related-record displays easier to customize. It simplifies internal code while keeping the user experience consistent and easier to maintain over time.

Adaptation of some molules to the changes brought by https://github.com/odoo/odoo/pull/97984

The formula, domain and special date changer are incorrect for the lines 'Report à nouveau' and 'Résultat de l'exercice' in the french BS. Reverting the changes introduced by commit c30d1e1bd3800ffb70522a00b6a2547b9a3cd9fa for these 2 lines. task-2889690 Forward-Port-Of: odoo/enterprise#29766

The formula, domain and special date changer are incorrect for
the lines 'Report à nouveau' and 'Résultat de l'exercice' in the
french BS. Reverting the changes introduced by commit
c30d1e1bd3800ffb70522a00b6a2547b9a3cd9fa for these 2 lines.

task-2889690

Forward-Port-Of: odoo/enterprise#29766

- demo data for companies no longer needed because a specific company in Mexico is already added. - partner VATs removed because it's not required for foreign partners Forward-Port-Of: odoo/enterprise#30102

- demo data for companies no longer needed because a specific company in Mexico
  is already added.
- partner VATs removed because it's not required for foreign partners

Forward-Port-Of: odoo/enterprise#30102

Before this commit: If you try to ship within the same country with EasyPost, you would receive an error from EasyPost API: `Easypost returned an error: 1100683: International Information cannot be specified for Domestic Shipments.` According to: https://www.easypost.com/customs-guide ``` When shipping internationally, you go through the same steps as shipping domestically, except that you need to add customs information to your shipment. [...] You need to pass customs information whenever

Before this commit:
If you try to ship within the same country with EasyPost, you would receive an error from EasyPost API:
`Easypost returned an error: 1100683: International Information cannot be specified for Domestic Shipments.`
According to:
https://www.easypost.com/customs-guide
```
When shipping internationally, you go through the same steps as shipping domestically, except that you need to add customs information to your shipment. [...] You need to pass customs information whenever you are shipping between two countries.
```

After this commit:
The custom information process is skipped if it is a domestic shipping.
So it goes through as intended

Note: This issue did arise recently probably due to this other recent fix:
https://github.com/odoo/enterprise/pull/30042
which was probably not tested with domestic shipping

OPW-2949124

Forward-Port-Of: odoo/enterprise#30706

opw-2871127 Forward-Port-Of: odoo/enterprise#30798 Forward-Port-Of: odoo/enterprise#30699

opw-2871127

Forward-Port-Of: odoo/enterprise#30798
Forward-Port-Of: odoo/enterprise#30699