Friday, November 4, 2022
8 changes · master
Enhancements to existing features
The Project app’s task and project views have been rebuilt on Odoo’s newer interface framework. This should make these screens easier to maintain and prepare them for future improvements, with minimal immediate change for everyday users.
Odoo can now group records in reports and list views using related fields without requiring duplicate stored database columns. This can reduce database size and maintenance work while keeping reporting capabilities available.
Original PR description
In most cases, the only reason to mark a related field as stored is a need to group records by such field. With this commit we can make grouping without making column copy. It allows to save database size as well as resources needed to create and keep such duplicate up-to-date. In fact, read_group supported non-stored related fields for ages, but it was limited to automatic related fields (inherits/delegate=True). So we only need to weaken constrain for groupby argument and add some extra joinings in _inherits_join_calc to give new feature to the world. --- task-2155109 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Event managers can now filter registrations based on the answers attendees selected during signup. This makes it easier to find specific attendee groups and review registration details without manually checking each record.
Original PR description
This PR adds the filter for users to see Selected answers given at the time of registration. taskID-2995250
The CRM leads and opportunities list is now less cluttered by hiding phone and company columns by default. Users can still show these fields when needed, but the everyday view is easier to scan and work with.
Original PR description
At the moment, the tree view is quite dense. In order to ease its use, make company and phone fields optional and hidden by default. This is done for crm.leads as both leads and opportunities. Task-3053159
Product option restrictions are now defined alongside the products they affect, instead of being split across the sales module. This reduces the risk of installation failures or data inconsistencies when modules are installed in different orders.
Original PR description
Following recent changes in stable deleting/archiving product variants forbidden by attributes exclusions, installing some modules after the sale app failed because the product `product_product_4d` specified in `product` was deleted by the attributes exclusions of the `sale` module. This has been fixed in stable by removing all references to this xml_id. Nevertheless, this bug showed us that the definition of attributes exclusion for a product in another module than the one creating it is a bad idea, as it modifies what's allowed or not with that product, leading to potential database inconsistencies. This commit moves the exclusions targeting products from the `product` module to the `product` module, to reduce the risks of other modules using/referencing the deleted/modified products in a way conflicting with the exclusions.
Fleet users can now access all documents related to a vehicle directly from its vehicle record. A new setting lets companies link fleet attachments with the Documents app, making vehicle paperwork easier to organize and find in one place.
Original PR description
The purpose of the task is to integrate fleet and documents so we will get all the documents of the vehicle in one place. So in this commit, Added a stat button to have documents on the vehicle - if documents is installed and the user has the document right then, it leads to the document app - if the document is not installed it leads to a kanban with documents - added a setting in the document to link the attachment of a fleet to a the document app task-2144780
Social media post previews now load images more efficiently by using cached attachment links instead of embedding image data directly. This should make preview screens faster and smoother across Facebook, Instagram, LinkedIn, and Twitter, with an additional layout improvement for Twitter previews.
Original PR description
It improves the performance of the post preview. Technical note: the preview rendering of the post image has been changed from inline to a simple URL to the attachment (by default stored in the file system in a resized and compressed form). This removes the encoding process and allows the browser to cache the file. Note that the icon for push notification still use the inline image encoding because icon are small and it would have been hard to modify as the icon is stored in a binary field (in that case, the attachment is written after the post creation and is not available during the creation). Task-2674439
Project side panels, sharing screens, and field service kanban behavior were modernized to improve maintainability and keep the user experience consistent. An unused field service date widget was removed, reducing obsolete code without affecting active workflows.