Daily updates from Odoo
Navigate
Branch
Friday, October 22, 2021
12 changes
New functionality added to Odoo
Users can now turn eligible social media posts or comments into CRM leads directly from the Social app. The flow helps link the lead to an existing or new customer and records useful context from the original interaction, making social engagement easier to follow up commercially.
Original PR description
To allow user to generate a lead in the CRM, a 'Generate Lead' option has been added in the dropdown menu associated to each social comment and post. This option is available when the user has the…
To allow user to generate a lead in the CRM, a 'Generate Lead' option has been added in the dropdown menu associated to each social comment and post. This option is available when the user has the appropriate rights and when he is not the author of the post/comment. When clicked, the new option will open a conversion wizard that allows linking the created lead to an existing customer, or to a create one. We also try to find a matching existing customer using a name_search with the name of the author of the post/comment we are converting. Since the "description" field is now a Html field, we use a specific template to get a nice rendering containing the various information we have: - Author name - Post/comment content - Published date - Link to the post/comment Please note that for obvious privacy reasons, the social media platforms will not provide us with people's email, phone or address information, we only have the author name and the content of his post/comment. For that reason, end users will probably often only convert to leads based on existing clients, since otherwise they will not have any mean to contact the created lead. The generate lead feature has been implemented for: - Facebook - Twitter - LinkedIn - Instagram - YouTube But can be implemented for future media easily by following the same architecture. To enforce our lead creation logic, a few tests were added into the social_test_full module. In addition, we improved the name of the utm.source created for each social.post by including the few first characters of the message. It will ease the reading of statistics related to the posts. LINKS Task ID-2206496
Enhancements to existing features
Creating new models in Studio is now much faster, especially on databases with many installed apps. The change reduces repeated background setup work by creating related models and fields in batches, helping avoid long waits and timeouts.
Original PR description
related to odoo/odoo#78514
Adds a dashboard view for eLearning course reporting, making it the first view when users open eLearning > Reporting > Courses. This helps business users review course performance more quickly from a dedicated reporting entry point.
Original PR description
This module contains the dashboard view for the website_slides. This view is used for the reporting of courses as the first view when entering eLearning > Reporting > Courses. COM PR: /odoo/odoo#75646 UPGRADE PR: /odoo/upgrade#2784 task-2597345
Uninstalling Timesheet now also removes related timesheet functions from HR and Sales. This better matches user expectations that turning off Timesheet removes all connected timesheet capabilities, reducing leftover menus or features.
Original PR description
Uninstall the modules `hr_timesheet` and `sale_timesheet` upon uninstallation of `timesheet_grid`. When user uninstalls Timesheet they expect all timesheet related functions to be removed. TaskID: 2590291
Resolved issues and error corrections
This fix ensures field service sale products use the correct worksheet template when users switch between companies. It prevents company-specific settings from being mixed up, helping teams keep reports and workflows accurate in multi-company environments.
Original PR description
Fixes a multi company issue with the `worksheet_template_id` field on `product.template`, the field depends on a company_dependent field and it would not retrigger the compute upon changing the current active company. The field is now a company_dependent field aswell and is recomputed when writing/creating records. Task ID: 2613947
Signing documents on behalf of someone else now records the represented signer as responsible for edits made during signing. This keeps audit logs accurate and avoids showing the logged-in user when the action belongs to the token owner.
Original PR description
In sign, when a document is edited while signing, an update log is created with the partner who edited the template. If 'sign now' is used to sign a document in the name of other person, and an update log is created, it was being created in the name of the logged user who edited the template, however it should contain the token owner. task-2653064
Code cleanup and technical improvements
Manufacturing accounting report styling is now loaded only when those reports are used, rather than during regular front-end use. This reduces unnecessary loading for users and helps keep the interface lighter without changing business functionality.
Original PR description
Move some file to other asset bundle to be load less. task-2643681
Miscellaneous changes
The Timesheets > To Validate menus are created with a server action instead of directly being `act_window` but they copy most of their parameters from an existing view. When modifying the default view using studio, the change does not apply to the To Validate views, this commit aims to fix that issue. This is done by sorting the views according to the action's `view_mode` field. Task ID: 2612215 Forward-Port-Of: odoo/enterprise#21844 Forward-Port-Of: odoo/enterprise#19886
Original PR description
The Timesheets > To Validate menus are created with a server action instead of directly being `act_window` but they copy most of their parameters from an existing view. When modifying the default view using studio, the change does not apply to the To Validate views, this commit aims to fix that issue. This is done by sorting the views according to the action's `view_mode` field. Task ID: 2612215 Forward-Port-Of: odoo/enterprise#21844 Forward-Port-Of: odoo/enterprise#19886
The `Format Phone` rule would crash if the country_id was somehow missing on the record AND on the company. TaskID: 2674662 Forward-Port-Of: odoo/enterprise#21823
Original PR description
The `Format Phone` rule would crash if the country_id was somehow missing on the record AND on the company. TaskID: 2674662 Forward-Port-Of: odoo/enterprise#21823
In sign, while signing a document, it is currently possible to click multiple times on signature and initials sign items and this opens multiple signature wizards. This PR fixes this issue by debouncing the click event handler to make it sure it runs only once every 300ms at maximum. task-2653071 Forward-Port-Of: odoo/enterprise#21182
Original PR description
In sign, while signing a document, it is currently possible to click multiple times on signature and initials sign items and this opens multiple signature wizards. This PR fixes this issue by debouncing the click event handler to make it sure it runs only once every 300ms at maximum. task-2653071 Forward-Port-Of: odoo/enterprise#21182
"-0.0" may occur from roundings or multiplication. format_float may then return '-0.0' which is not allowed by the CFDI. Now '0.0' is returned for every value which is equal to zero. Ticket link: https://www.odoo.com/web#id=2668652&model=project.task opw-2668652 Forward-Port-Of: odoo/enterprise#21826
Original PR description
"-0.0" may occur from roundings or multiplication. format_float may then return '-0.0' which is not allowed by the CFDI. Now '0.0' is returned for every value which is equal to zero. Ticket link: https://www.odoo.com/web#id=2668652&model=project.task opw-2668652 Forward-Port-Of: odoo/enterprise#21826
On runbot 1. Insert the demo CRM lead pivot in a spreadsheet => F1 is a Total formula 2. Reload the spreadsheet => F2 has magically become a measure formula the command is mutated in place :( It's the mutated commands which is send over the network and becomes the accepted revision I would like to make the dispatched commands immutable (in o-spreadsheet), but I didn't find a proper way (yet). A simple deep copy with JSON stringify and parse would probably do it, but there's current
Original PR description
On runbot 1. Insert the demo CRM lead pivot in a spreadsheet => F1 is a Total formula 2. Reload the spreadsheet => F2 has magically become a measure formula the command is mutated in place :( It's the mutated commands which is send over the network and becomes the accepted revision I would like to make the dispatched commands immutable (in o-spreadsheet), but I didn't find a proper way (yet). A simple deep copy with JSON stringify and parse would probably do it, but there's currently one core command which is not serializable (the command is only internal, never sent on the network). In the mean time, this commit is a quick fix. See task 2667116 Task 2662680 Forward-Port-Of: odoo/enterprise#21802 Forward-Port-Of: odoo/enterprise#21625