Odoo Changelog — 2025-01-13

Monday, January 13, 2025

2 changes

Refactoring(2)

Code cleanup and technical improvements

[REF] mail, various: stop autofollow madness !

Enterprisemasteraccount_followupappointmentcalendardata_cleaninghelpdeskhr_contract_salaryhr_payrolltest_appointment_fullMEDIUM

Odoo now avoids automatically adding every message recipient as a follower, so records should keep cleaner and more relevant follower lists. Customer-facing documents still keep the right customer access where needed, while notifications are handled more consistently across apps like appointments, helpdesk, payroll, and follow-up.

Original PR description

Autollow (adding explicit recipients, aka 'partner_ids) as followers when posting a message should be used only in some specific flows. It is notably done to ensure customer of portal-enabled…

Autollow (adding explicit recipients, aka 'partner_ids) as followers when
posting a message should be used only in some specific flows. It is notably
done to ensure customer of portal-enabled documents (SO, PO, ...) are able
to access it, as ACLs are notably based on followers.

Currently python code does not activate it by default, as it would create a
log of useless followers. JS does it once the composer is opened, mainly for
historical reasons.

Autofollow is now always turned off. Purpose is to have only relevant
followers, and mainly internal users once email-like flow is completely
implemented.

Some manual autofollow are also removed. SO and PO expect customer to be
follower of documents, notably for ACL purpose. We therefore set the new
'_mail_thread_customer' class attribute introduced in this change. It does
the same as 'mail_post_autofollow', but for the document customer only.

Task-4273479: [mail] Stop autofollow madness !
Prepares Task-4422660: [mail] Use external suggested recipients
Prepares Task-4273479: [mail] Email-like recipients

#followers#notifications#customer access#mail

[DRAFT][REF] web,*: cleanup DynamicModelFieldSelectorChar

PR #75649

Enterprisemasterwhatsapp

This update adjusts WhatsApp-related field selector usage to match a recent naming cleanup in the underlying platform. It keeps the Enterprise code aligned with the main Odoo framework and reduces maintenance risk without changing business workflows.

Original PR description

*: whatsapp: widget usages adaptations

Since [1], DynamicModelFieldSelectorChar field widget was introduced.

The related community commit renames it amongst other things. This commit adapts its usages in the enterprise repository.

[1]: https://github.com/odoo/odoo/commit/fe62bfeacb38e03cb94010f1f75ae301951ac9d1

task-4388736

#cleanup#alignment#whatsapp

Autollow (adding explicit recipients, aka 'partner_ids) as followers when posting a message should be used only in some specific flows. It is notably done to ensure customer of portal-enabled documents (SO, PO, ...) are able to access it, as ACLs are notably based on followers. Currently python code does not activate it by default, as it would create a log of useless followers. JS does it once the composer is opened, mainly for historical reasons. Autofollow is now always turned off. Purpose is to have only relevant followers, and mainly internal users once email-like flow is completely implemented. Some manual autofollow are also removed. SO and PO expect customer to be follower of documents, notably for ACL purpose. We therefore set the new '_mail_thread_customer' class attribute introduced in this change. It does the same as 'mail_post_autofollow', but for the document customer only. Task-4273479: [mail] Stop autofollow madness ! Prepares Task-4422660: [mail] Use external suggested recipients Prepares Task-4273479: [mail] Email-like recipients

*: whatsapp: widget usages adaptations Since [1], DynamicModelFieldSelectorChar field widget was introduced. The related community commit renames it amongst other things. This commit adapts its usages in the enterprise repository. [1]: https://github.com/odoo/odoo/commit/fe62bfeacb38e03cb94010f1f75ae301951ac9d1 task-4388736