Wednesday, August 9, 2023
1 change · master
Code cleanup and technical improvements
This update standardizes how email aliases are defined and displayed across several Odoo apps, reducing duplicated setup and making future changes easier. It keeps existing journal-specific behavior while preparing the platform for future multi-company alias support.
Original PR description
Cleanup alias usage and definition. Prepare code to ease future changes and improvements. Notably * add a 'alias_email' computed field on the mixin allowing to have the complete alias email when set,…
Cleanup alias usage and definition. Prepare code to ease future changes and
improvements. Notably
* add a 'alias_email' computed field on the mixin allowing to have the
complete alias email when set, and False in case it is inactive or linked
to an inactive alias domain;
* remove unnecessary alias_id field definition when just the help differs
from the standard definition coming from the 'mail.alias.mixin';
* use fields coming from 'inherits' instead of using alias_id and its sub-
fields; notably use 'alias_display_name' and 'alias_email' fields;
* remove useless custom code and management;
* improve alias parameters support code in configuration parameters;
Alias usage is now more standard on 'account.journal' model. Main specific
features of journal are still present: automatic alias name generation,
support of non-ascii characters, ... See community PR for more details.
LINKS
After odoo/odoo#130768 and odoo/enterprise#45204 this is another preparation
for multi-company aliases (see odoo/odoo#76734 and odoo/enterprise#20983).
Task-3453343 (Mail: Cleanup Alias Usage)
Prepares Task-36879 (Mail: Support MultiCompany Aliases)