Aurélien Warnon
1e25946a76
PURPOSE This commit consolidates UTM usage across all applications. Global purpose is to avoid having undesired side-effects, such as unlinking an utm.source/utm.medium/utm.campaign and at the same time cascading the deletion to various records without noticing. SPECS ALLOW MORE PEOPLE TO CLEAN UTM RECORDS Currently, not even the system administrator can delete utm.mediums and utm.sources (he can only delete campaigns). These were considered as "technical records", but allowing some cleanup is a good idea since these records are often automatically generated and can create a lot of unnecessary noise in the database. That's why we now allow the following groups to delete all UTM records (sources, mediums and campaigns): - group_system - group_mass_mailing_user - group_social_manager (enterprise) PREVENT DELETION For some use cases, removing an utm.source/utm.medium/utm.campaign would cascade delete the related record, which was unintended / hidden side effect. These combinations were secured by preventing to unlink: - mailing.mailing source_id field Trying to delete the utm.source will throw an error message - mailing.mailing medium_id field Trying to delete the utm.medium will throw an error message - hr.recruitment.source source_id field Trying to delete the utm.source will throw an error message ADDING CLEAN ERROR MESSAGES When trying to delete an UTM record that is linked with ondelete="restrict", we improved the error message to give a clear explication to the user, e.g: "You can't delete these UTM sources as they are linked to the following mailings in the Mass Mailing APP, and deleting the source would break the statistics: Newsletter" SPECIFY 'ondelete' strategy For a lot of uses of sources/mediums/campaigns, the 'ondelete' strategy was not specified, leading to the confusion of "is this really how we want to handle this?". A lot of ondelete="set null" have been added in various field definitions to ensure that this is the desired and logical strategy we want for that specific model. PREVENT REMOVING HARDCODED UTM RECORDS In some functional flows, UTM records are hardcoded using their direct record reference. This is notably the case for the recruitment process and its creation of aliases, and for the Email / SMS Marketing flows. As deleting them would break these flows, we prevent their deletion in a "api.ondelete" method. ENFORCE NEW RULES WITH TESTS A lot of python tests have been added to make sure we enforce the decisions taken here above. LINKS ENT PR odoo/enterprise#19048 Task-2459480 closes odoo/odoo#72239 Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>
1.1 KiB
1.1 KiB
| 1 | id | name | model_id:id | group_id:id | perm_read | perm_write | perm_create | perm_unlink |
|---|---|---|---|---|---|---|---|---|
| 2 | access_utm_campaign_user | access_utm_campaign_user | model_utm_campaign | base.group_user | 1 | 1 | 1 | 0 |
| 3 | access_utm_campaign_system | utm.campaign.system | model_utm_campaign | base.group_system | 1 | 1 | 1 | 1 |
| 4 | access_utm_medium_user | access_utm_medium_user | model_utm_medium | base.group_user | 1 | 1 | 1 | 0 |
| 5 | access_utm_medium_system | utm.medium.system | model_utm_medium | base.group_system | 1 | 1 | 1 | 1 |
| 6 | access_utm_source_user | access_utm_source_user | model_utm_source | base.group_user | 1 | 1 | 1 | 0 |
| 7 | access_utm_source_system | utm.source.system | model_utm_source | base.group_system | 1 | 1 | 1 | 1 |
| 8 | access_utm_stage_user | mail.utm.stage | model_utm_stage | base.group_user | 1 | 0 | 0 | 0 |
| 9 | access_utm_stage_system | mail.utm.stage | model_utm_stage | base.group_system | 1 | 1 | 1 | 1 |
| 10 | access_utm_campaign | access_utm_campaign | model_utm_campaign | 1 | 0 | 1 | 0 | |
| 11 | access_utm_medium | access_utm_medium | model_utm_medium | 1 | 0 | 1 | 0 | |
| 12 | access_utm_source | access_utm_source | model_utm_source | 1 | 0 | 1 | 0 | |
| 13 | access_utm_tag_user | utm.tag | model_utm_tag | base.group_user | 1 | 0 | 0 | 0 |
| 14 | access_utm_tag_system | utm.tag | model_utm_tag | base.group_system | 1 | 1 | 1 | 1 |