Thibault DelavalléeandJeremy Hennecart
643df62f12
RATIONALE Merge two phone-related field on registration as they overlap. Having only one is sufficient for contact-oriented model like registration. SPECIFICATIONS Registration model currently holds two phone field, phone and mobile. This leads to having records with sometimes phone, sometimes mobile being filled. This makes phone flows not easy: we have to define fallbacks (use phone or mobile), data is not always synchronized, ... in the end what event users need is one phone field to be able to communicate with attendees. Having only one field is sufficient and simplifies the model. Keep only one phone field, instead of two. Merge phone and mobile into a single one, keeping phone as first value when having both available e.g. when synchronizing with the partner. Task-3366899 Part-of: odoo/odoo#128232 Co-authored-by: "Jeremy Hennecart" <jeh@odoo.com>
32 lines
954 B
Python
32 lines
954 B
Python
# -*- coding: utf-8 -*-
|
|
# Part of Odoo. See LICENSE file for full copyright and licensing details.
|
|
|
|
{
|
|
'name': "Events Booths Sales",
|
|
'category': 'Marketing/Events',
|
|
'version': '1.2',
|
|
'summary': "Manage event booths sale",
|
|
'description': """
|
|
Sell your event booths and track payments on sale orders.
|
|
""",
|
|
'depends': ['event_booth', 'event_sale'],
|
|
'data': [
|
|
'security/ir.model.access.csv',
|
|
'data/product_data.xml',
|
|
'data/event_booth_category_data.xml',
|
|
'views/sale_order_views.xml',
|
|
'views/event_type_booth_views.xml',
|
|
'views/event_booth_category_views.xml',
|
|
'views/event_booth_registration_views.xml',
|
|
'views/event_booth_views.xml',
|
|
'wizard/event_booth_configurator_views.xml',
|
|
],
|
|
'auto_install': True,
|
|
'assets': {
|
|
'web.assets_backend': [
|
|
'event_booth_sale/static/src/**/*',
|
|
]
|
|
},
|
|
'license': 'LGPL-3',
|
|
}
|