Daily updates from Odoo
Tuesday, February 4, 2020
2 changes · master
New functionality added to Odoo
Studio now includes a guided model configurator that helps users create new apps and menu items with common business features already set up. It can automatically add useful fields, views, menus, and access settings so new applications are faster to build and more immediately usable.
Original PR description
Studio usability and user experience improvement with an emphasis on the creation of new applications and menu items. The main improvement provided by this task is the introduction of a 'Model…
Studio usability and user experience improvement with an emphasis
on the creation of new applications and menu items.
The main improvement provided by this task is the introduction of a
'Model Configurator', as new dialog that can be accessed when creating
new models in Studio, either through the App Creator or through the
edition of a menu.
This model configurator allows user to select pre-determined behaviours
on their newly-created models. The possible behaviours include:
- m2o to a `res.partner` record ('Customer') which will enable
the map view on the model
- m2o to a `res.users` record ('Responsible')
- date fields ('Date', 'Date Start', 'Date Stop') which will enable
the calendar and gantt views on the model respectively
- monetary field ('Value'), which will enable the pivot view on the model
- stage field, which will create a model for this purpose and which will
enable the kanban view
- image field
- tags field which will create a model for this purpose
- text field ('Notes')
- m2o to a `res.company` field ('Company') - this option is enabled
by default and is only visible in a multi-company environment; it will
also create a record rule for the created model to restrict access
based on the company field.
Along with these, several behaviours are enabled by default and
can only be disabled when in debug mode:
- archiving behaviour
- sequencing of record through a `sequence` field
- inheritance of `mail.thread` and `mail.activity.mixin`
The selected behaviours will be used to automatically generate
views and menu entries (for tags and stages models) in the app.
The enabled view types will depend on the selected behaviours
and will include all relevant fields according in a 'best practice' way
(e.g. images are included in the kanban card, etc.).
Other changes in this task:
- default access rules are more lax than before (CRUD for internal
users by default)
- small UX improvement in the Studio tabs at the top right
Task 2091654
Community PR: odoo/odoo#42055Enhancements to existing features
Event organizers get clearer event reporting, easier invitation tools, and better registration handling. The update also improves ticket sale visibility, attendee payment status, and speaker proposal formatting, making event operations smoother across sales, marketing, and website workflows.
Original PR description
PURPOSE Improve global event usability by adding a graph view as well as various changes on the ticket sale flow. We also improved the track proposal layout, added a handy button to invite partners to your event and prepared some data for the event_barcode module. SPECIFICATIONS - Add a "Invite" button on the event, that allows sending invitations though the mass_mailing / mass_sms features - Add a graph view for the event.event model - Allow styling the description and the biography when sending a track proposal with basic plaintext2html usage - Improve event and sale views integration in the event_sale module (stat buttons and next activity generation) - General improvements to the "auto confirm" flow of registrations - Prepare data for the event_barcode module, to make it "event agnostic" More details in underlying commits LINKS Task ID : 2093336 Enterprise PR: odoo/enterprise#7760