Daily updates from Odoo
Thursday, February 8, 2024
8 changes · master
Enhancements to existing features
Frontdesk stations and visitor records now include company information in their main screens and search options. This helps teams identify visitor affiliations more easily and improves record organization, with demo visitor data also enriched with drink preferences.
Original PR description
The following things are done by this commit: --------- - Station and Visitors now have the company added to their list, form, and search view. - We add drink demo data to visitors task-3576984
When Payroll is installed, Odoo now automatically adds the payroll localization modules that match each company's country. This reduces manual setup and helps companies start with the correct country-specific payroll configuration.
Original PR description
Change auto installs l10n_**_hr_payroll module based on the country that the company is in. It's triggered by Payroll module instalation task-3530929
Point of Sale now uses the same notification system as the wider Odoo web interface. This creates a more unified user experience and reduces duplicated POS-specific code, making future maintenance simpler.
Original PR description
In this commit we remove the `pos_notification` service and the pos notification component and we replace them with the `notification` service from web. This makes the odoo experience more unified and greatly simplifies the pos codebase. https://github.com/odoo/odoo/pull/152830 Task 3725015
Helpdesk permissions were updated to match the renamed canned response feature, formerly known as shortcodes. This keeps access rules and live chat helpdesk behavior aligned with the new naming, reducing confusion for support teams.
The pull request updates internal activity property names used by the Sign and VoIP apps to align with broader platform naming changes. This helps keep activity displays consistent and maintainable without introducing noticeable workflow changes for users.
Original PR description
https://github.com/odoo/odoo/pull/152303
Studio-created related fields will no longer be stored by default, reducing performance issues and database growth when source values change. Users can still group, sort, and aggregate these fields in reports and views, with related test and reporting updates across several business apps.
Original PR description
#### [IMP] helpdesk: new groupable description on Field See community commit about related no-store becoming groupable/aggrable/sortable. #### [IMP] web_studio: by default related field is no-store…
#### [IMP] helpdesk: new groupable description on Field
See community commit about related no-store becoming groupable/aggrable/sortable.
#### [IMP] web_studio: by default related field is no-store
When we use studio to create related fields, these fields are store by default (expect for one2many/many2many). This behavior creates a lot of tickets (opw: 3670400, 3660059, 3665637, 3647978, 3632099, 3619270, ...), because it slows down Odoo for each related field created.
In the community version, we can now group/aggregate/sort by no-store related field. Then there is no reason anymore to store related field created by studio anymore. Related no-store fields cost much less than the store one: it is generally a little bit slower to read (you need to read the related complete path) but it avoids huge performance degradation when the source values are updated (+ reduce data disked used).
#### [FIX] *: fix related field search used in domain
In the community branch, we changed the behavior of the search method of related field.
`'resource_type', '!=', 'material'` was filterout record where `resource_id IS NULL`. It is not the case anymore, then to pass the `test_performance_recompute_shifts_in_leave_periods` test, we need to `('resource_id', '!=', False)`
#### [IMP] account_accountant: don't ask useless aggregatation in kanban views
Modify tests because now kanban view doesn't ask useless aggregation.
#### [REF] core: aggregates on many2many doesn't make lot of sense
The current version doesn't seem correct and also it quite complicate to understand. TODO: Check and add a test to show the issues
https://github.com/odoo/odoo/pull/127353
https://github.com/odoo/documentation/pull/5541The VoIP calling component was updated to a newer version of its underlying calling library. This brings recent bug fixes that help prevent crashes and improve reliability for users making calls in Odoo.
Original PR description
... so that we can benefit from the latest bug fixes, including onsip/SIP.js@f06939c, which [we already had to backport](https://github.com/odoo/enterprise/pull/53581) to prevent crashes in stable versions of Odoo. Changelogs: https://github.com/onsip/SIP.js/releases Task-3724836
The attendance Gantt view now shows hour values with the same precision as the left-side column. This reduces confusion for users by making attendance durations consistent across the screen.
Original PR description
For customer, it was confusing to have a difference between hours displayed on the left colum and in the gantt view task : 3695852