Odoo Changelog — 2023-01-27

Friday, January 27, 2023

3 changes · master

Refactoring(3)

Code cleanup and technical improvements

[REF] web_tour,*: use the registry in collecting the tours

Coremasteraccountauth_totpauth_totp_mailauth_totp_portalcontactscrmcrm_iap_mineeventevent_salehrhr_expensehr_holidaysweb_tour

This change reorganizes how Odoo’s guided tours and related test flows are registered behind the scenes. It supports a more reliable technical foundation for future development without changing day-to-day user behavior.

Original PR description

This is a step closer to a goal of avoiding dependence on asynchronous
modules. Starting from this commit, new tour definition should be
registered to `registry.category("web_tour.tours")` registry.

So, instead of the following:

```js
import tour from "web_tour.tour";
tour.register(name, options, steps);
```

We now do:

```js
import { registry } from "@web/core/registry";
registry.category("web_tour.tours").add(name, optionsWithSteps);
```

Notice the `options` and `steps` params are merged when registering
the tour definition. It should look something like so:

```js
registry.category("web_tour.tours").add("account_tour", {
  test: true,
  steps: [ ... ],
});
```

And if the `TourManager` instance is needed, one can get it from the
registry like so `registry.get("tourManager")`. Note however that
this instance is only available when the `TourManager` has been
instantiated -- so it's not available at top level of the module.

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

#guided tours#tests#internal cleanup

[REF] web_tour,*: use the registry in collecting the tours

PR #36335

Enterprisemasteraccount_accountantaccount_accountant_batch_paymentaccount_avatax_saleaccount_reportsapprovalsdocumentsdocuments_accountdocuments_spreadsheetdocuments_spreadsheet_crmhelpdeskhr_contract_salary_payroll

This change updates how automated product tours are collected across several Odoo apps, aligning them with a shared internal registry. It should not change day-to-day user workflows, but it improves maintainability and consistency of testing infrastructure.

Original PR description

Related to: https://github.com/odoo/odoo/pull/111103

#web_tour#testing#maintainability

[REF] documents_spreadsheet, spreadsheet_edition: remove m2o widget

PR #35964

Enterprisemasterdocuments_spreadsheetspreadsheet_edition

The spreadsheet document tools now use Odoo’s standard menu selection component instead of a custom field widget. This keeps the user experience more consistent across Odoo and reduces maintenance risk for future updates.

Original PR description

This commit remove our custom widget do display a many2one field and replace it by the web Many2XAutocomplete component.

Odoo task [3103695](https://www.odoo.com/web#id=3103695&menu_id=4720&cids=1&action=333&active_id=2328&model=project.task&view_type=form)

#spreadsheet#documents#menu selection#maintenance

This is a step closer to a goal of avoiding dependence on asynchronous modules. Starting from this commit, new tour definition should be registered to `registry.category("web_tour.tours")` registry. So, instead of the following: ```js import tour from "web_tour.tour"; tour.register(name, options, steps); ``` We now do: ```js import { registry } from "@web/core/registry"; registry.category("web_tour.tours").add(name, optionsWithSteps); ``` Notice the `options` and `steps` params are merged when registering the tour definition. It should look something like so: ```js registry.category("web_tour.tours").add("account_tour", { test: true, steps: [ ... ], }); ``` And if the `TourManager` instance is needed, one can get it from the registry like so `registry.get("tourManager")`. Note however that this instance is only available when the `TourManager` has been instantiated -- so it's not available at top level of the module. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

This commit remove our custom widget do display a many2one field and replace it by the web Many2XAutocomplete component. Odoo task [3103695](https://www.odoo.com/web#id=3103695&menu_id=4720&cids=1&action=333&active_id=2328&model=project.task&view_type=form)