Issue 11426
- Title
- Unsubscribe from scenario
- Priority
- feature
- Status
- resolved
- Superseder
- 'not where' operator on many2many returns too much records (issue 11425)
- Nosy list
- ced, reviewbot, roundup-bot
- Assigned to
- ced
- Keywords
- review
Created on 2022-04-21.21:34:38 by ced, last changed 3 weeks ago by roundup-bot.
Messages
New changeset 66dd643620da by Cédric Krier in branch 'default': Allow party to be unsubscribed from scenario https://hg.tryton.org/tryton-env/rev/66dd643620da
New changeset 1f606673f56a by Cédric Krier in branch 'default': Allow party to be unsubscribed from scenario https://hg.tryton.org/modules/marketing_automation/rev/1f606673f56a
For some scenario when the user unsubscribes, he wants to be unsubscribed not only for the current record but for any future one created by the scenario.
So I propose to add an option on the scenario and if activated when a record is blocked, the scenario is registered on the linked party as unsubscribed.
This will require to depend on party module but I do not think it is a problem as mainly the module has mainly no feature without it. Also marketing is mainly about exchanging with party.
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-06-07 18:05:01 | roundup-bot | set | messages: + msg76989 |
| 2022-06-07 18:04:44 | roundup-bot | set | messages:
+ msg76988 nosy: + roundup-bot status: testing -> resolved |
| 2022-04-21 21:58:39 | reviewbot | set | messages:
+ msg76119 nosy: + reviewbot |
| 2022-04-21 21:35:50 | ced | set | keyword:
+ review reviews: 403391045 status: in-progress -> testing superseder: + 'not where' operator on many2many returns too much records |
| 2022-04-21 21:34:38 | ced | create | |
Showing 10 items. Show all history (warning: this could be VERY long)