Odoo Changelog — 2025-01-10

Friday, January 10, 2025

2 changes

Refactoring(2)

Code cleanup and technical improvements

[REF] mail, various: improve find / create partners in mail flows

Enterprisemasterappointmentdocumentshelpdeskhelpdesk_fsmhr_appraisalhr_contract_signsignweb_studiowebsite_appointmentMEDIUM

Mail-related flows now use a shared approach to find or create contacts from email addresses, reducing duplicated behavior across apps. This should make suggested recipients and customer contact creation more consistent in areas like Helpdesk, Appointments, Documents, Sign, HR, and Studio.

Original PR description

In order to unify methods searching or creating partners, let us create
yet another one. Introducing '_partner_find_from_emails' that should
act as the main find, sort and create partner record-based tool method.

This leads to cleaning various mail methods, notably some often inherited
in modules like '_get_customer_information' and '_message_get_suggested
_recipients'.

See community PR for more details.

Task-4332797  [mail] Partner from emails 3.0
Prepares Task-4273479: [mail] Email-like recipients

#mail#contacts#recipients#customer-communication

[REF] pos_iot: make payment providers independent

PR #75729

Enterprisemasteriotpos_iotpos_iot_ingenicopos_iot_sixpos_iot_worldlineMEDIUM

The point-of-sale IoT payment terminal integrations have been reorganized so each provider is handled separately. This makes the system easier to maintain and reduces the risk of provider-specific changes affecting other terminals.

Original PR description

Community PR: https://github.com/odoo/odoo/pull/190853
Upgrade PR: https://github.com/odoo/upgrade/pull/6943

Before this PR, `pos_iot` contained the
Worldline and Ingenico payment providers.
A further module `pos_iot_six` contained the Six
payment provider. On the JS side, there was a long chain of inheritance:

`PaymentSix` extends `PaymentWorldline` which
extends `PaymentIngenico` which extends
`PaymentInterface`.

This made it difficult to reason about the code
that was actually being run for each payment
terminal.

After this PR, each payment provider is in a
separate module:

- `pos_iot` provides the framework but doesn't add any payment providers
- `pos_iot_ingenico`
- `pos_iot_worldline`,
- `pos_iot_six`

The JS code has undergone a refactor at the same
time as they no longer inherit from each other.

task-4398016

#point-of-sale#iot#payments#payment-terminals

In order to unify methods searching or creating partners, let us create yet another one. Introducing '_partner_find_from_emails' that should act as the main find, sort and create partner record-based tool method. This leads to cleaning various mail methods, notably some often inherited in modules like '_get_customer_information' and '_message_get_suggested _recipients'. See community PR for more details. Task-4332797 [mail] Partner from emails 3.0 Prepares Task-4273479: [mail] Email-like recipients

Community PR: https://github.com/odoo/odoo/pull/190853 Upgrade PR: https://github.com/odoo/upgrade/pull/6943 Before this PR, `pos_iot` contained the Worldline and Ingenico payment providers. A further module `pos_iot_six` contained the Six payment provider. On the JS side, there was a long chain of inheritance: `PaymentSix` extends `PaymentWorldline` which extends `PaymentIngenico` which extends `PaymentInterface`. This made it difficult to reason about the code that was actually being run for each payment terminal. After this PR, each payment provider is in a separate module: - `pos_iot` provides the framework but doesn't add any payment providers - `pos_iot_ingenico` - `pos_iot_worldline`, - `pos_iot_six` The JS code has undergone a refactor at the same time as they no longer inherit from each other. task-4398016