Thursday, December 3, 2020
4 changes · master
Enhancements to existing features
Mailing list screens now show clearer health indicators, including total contacts, valid email and SMS contacts, mailings sent, opt-outs, blacklists, and bounce rates. This helps users quickly assess list quality and navigate to related contacts or mailings, with demo data updated to better showcase the views.
Original PR description
PURPOSE Improves various views related to the mass mailing lists to help the user to check the "health" of its lists at a glance. SPECS Introduce statistic fields on mailing.list: - Total number of…
PURPOSE Improves various views related to the mass mailing lists to help the user to check the "health" of its lists at a glance. SPECS Introduce statistic fields on mailing.list: - Total number of contacts (replaces the previous number of valid emails) - Number of valid email contacts - Number of valid SMS contacts - Number of mailings sent using the list - Percentage (and total count) of opted-out contacts - Percentage (and total count) of blacklisted contacts The statistics are shown on the kanban and also on the form view where they are used to quickly reached the associated mailings / contacts. Demo data were slightly adapted to show more interesting demos on views. On a technical point of view, the various counts of contacts are made in a single query using CASE WHEN syntax. We need some entry points in the query to be able to dynamically add fields and joins in the mass_mailing_sms app, but it's better than copy/pasting multiple times a very similar query. LINKS Task 2182622 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update improves how several marketing and communication-related apps create multiple records at once. It reduces processing overhead in bulk operations and lays groundwork for broader performance improvements in future releases.
Original PR description
SMS marketing campaigns now receive an automated performance recap by email 24 hours after sending. This gives teams better visibility into SMS campaign results, using the same reporting approach already available for email campaigns.
Original PR description
Added SMS KPIs analysis report. This report will be sent by email 24 hours after the campaign sms are sent. Modification of the digest_mail_layout to be able to use it to generate the KPI report for Email or SMS mass mailing campaigns. Task-2274770 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update improves how several Odoo apps create multiple records at once, reducing unnecessary one-by-one processing. It should improve performance in marketing, helpdesk, documents, sign, timer, and related workflows without changing the user experience.
Original PR description
SPECIFICATIONS
By default, ORM supports creation of records in batch (one SQL INSERT by
record but batching other operations). When a create override on a given
model is specified as api.model or api.model_create_single this ability
is disabled and records are created one by one. This leads to performance
losses.
In this merge we update create to support batch creation. This allows to
gain performances linked to batch code improvements. Note that some of the
changes done in this merge will not have much impact because some records
are always created one by one. Converting them
* encourages new overrides to support multi record creation;
* provides the basis for a potential future API change to enforce batch
creation support;
LINKS
Task ID-2330149
COM PR odoo/odoo#61246
ENT PR odoo/enterprise#14561SPECIFICATIONS
By default, ORM supports creation of records in batch (one SQL INSERT by
record but batching other operations). When a create override on a given
model is specified as api.model or api.model_create_single this ability
is disabled and records are created one by one. This leads to performance
losses.
In this merge we update create to support batch creation. This allows to
gain performances linked to batch code improvements. Note that some of the
changes done in this merge will not have much impact because some records
are always created one by one. Converting them
* encourages new overrides to support multi record creation;
* provides the basis for a potential future API change to enforce batch
creation support;
LINKS
Task ID-2330149
COM PR odoo/odoo#61246
ENT PR odoo/enterprise#14561