| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2020-01-10 | [MOV] (website_)event(_sale/_question/_track): split main model files | Thibault Delavallée | |
| PURPOSE As event will soon evolve (onchange -> compute, code improvements, addition of new features) cleaning and improving tests is necessary to help avoid issues. SPECIFICATIONS As event model grow in complexity and features, it is easier to find its way through the application with having registration model lying in its own file to separate it from event-specific models (event.type, event.event). Ticket (event_sale) and sponsor (website_event_track) models are also extracted in their own file. LINKS LINKS Side effect of Task ID 2089156 (event onchange to compute) Community PR odoo/odoo#43127 Enterprise PR odoo/enterprise#7656 | |||
| 2019-07-25 | [ADD] event_sms: allow to schedule SMS in event communication | Thibault Delavallée | |
| PURPOSE Allow the user to schedule SMS communication on events SPECIFICATION In event.event form view: * rename tab 'Email Schedule' to 'Communication' * add a selection field at the beginning of event_mail_ids with label 'Send' and values 'Email' and 'SMS Text Message' (required with default value 'Email'); * add support of SMS template and SMS sending in event communication; When sending SMS on event registrations, keep a log of what has been sent. Use mobile or phone field of event registration as both may contain valid values, like partner model. Add SMS template data * Name: Event: Registration (see data) * Name: Event: Reminder (see data) Improve registration model * add a mobile field to the attendees form view: https://nimb.ws/p0VvyS Technically this task uses the newly-introduced API methods allowing to send and schedule SMS. LINKS Task 1922187 Part of PR #34705 | |||
