Daily updates from Odoo
Friday, December 20, 2024
11 changes · master
New functionality added to Odoo
Businesses can now include WhatsApp messages as part of customer payment follow-up levels and manual reminders. This gives teams another direct communication channel for overdue invoices, while also improving WhatsApp template links so they correctly point back to the company database.
Original PR description
Added the option to send WhatsApp message to make follow-up. task-4241442
Enhancements to existing features
Intrastat reports can now include services as well as goods, helping businesses meet service declaration requirements such as Belgian F01DGS and F02CMS. Users can filter reports by goods or services, assign service codes on products, and export the new service reporting formats where applicable.
Original PR description
Currently, the Intrastat report is restricted to products whose product type is different than services. Though, statistics report can also be required on Services, such as Declarations F01DGS & F02CMS (Manual : https://www.nbb.be/doc/dq/e_pdf_bb/f01dgs-f02cms_manual_en.pdf) This commit intend to improve the Intrastat report to also include services. Since commodities and services share a lot of similarities, we didn't create a new report but rather added a filter inside the current Intrastat report. It also adds a new column for the service categories and all the service codes. On the product, the string of the commodity code changes if the product is a commodity or a service (and become Service Code in that case) Initial PR : https://github.com/odoo/enterprise/pull/54942 task-2835786
The Mexican electronic invoicing flow now keeps the payment policy as a saved choice on customers, sales orders, invoices, and proforma documents. This improves consistency for reinvoicing, subscriptions, and related sales flows, reducing manual corrections and document errors.
Original PR description
Previously, the payment policy was a computed non-stored field. This causes some issues when reinvoicing, on subscriptions and other specific flows such as making Proforma. To fix these problems we: 1. Make the payment policy a stored selectable field. 2. Add the field on sale order (populates invoices). 3. Add the field on partner (populates sale order/invoices). 4. Add filters. 5. Add the field in Proforma. task-4245032
The Knowledge article index has been visually updated to match the style of embedded clipboard elements. This creates a more consistent and polished reading experience for users working with Knowledge articles.
Original PR description
This commit updates the look of the article index in a knowledge article. This embedded component now uses the same style as the embedded clipboard. Task-4314480
Gantt popovers can now reuse familiar Kanban card layouts, making schedule details clearer and more consistent across apps. This improves the user experience in planning-style views while preserving existing custom popover content when configured.
Original PR description
A new attribute "kanban_view_id" is introduced. If set, the kanban card template of the specified kanban view is used to render the body of the gantt popovers. If not set, the kanban view (if any) in the gantt view config (e.g. the kanban view in the curent action) will be used. If no kanban view is found, a default view based on display_name, date_start, and date_stop (from the gantt arch) will be generated and used. Note that this happens only if no content for the popover body has been specified in a template "gantt-popover" in the gantt arch. In that case the popover body is constructed using that template. Kanban view used or not, customization of the popover footer can still be done via the mechanism introduced in https://github.com/odoo/enterprise/pull/54292. Note that we cannot use the footer tag in the kanban card to do that since it has a different usage. Task ID: 4350860
The partner/contact form has been adjusted to match recent accounting layout changes and improve related actions such as customer statements and follow-up contact visuals. It also removes use of partner titles, helping simplify contact data management across affected business flows.
Original PR description
This commit will do multiple things: - Changing the image of the followup contact form - Adapting xpath since accounting entries group has been removed in the community pr - Adapting xpath since banks group has become a general group - Customer Statement stat button change - Removing for res.partner.title and all the use of the model task: 4306429
The Sign module interface has been refined to make everyday actions clearer and faster for users. Settings labels are more consistent, the template view is easier to use, selection options can be edited directly, and demo data helps users understand selection fields more easily.
Original PR description
### Purpose This PR improves the usability and user experience of the Sign module by addressing inconsistencies, refining UI elements, and adding functionality for better interaction with selection…
### Purpose This PR improves the usability and user experience of the Sign module by addressing inconsistencies, refining UI elements, and adding functionality for better interaction with selection fields. --- ### Before this PR - Labels in the Settings section had inconsistent punctuation. - The Validate button name did not seem meaningful name in the items popover - The Kanban view lacked refinement in terms of visuals and usability. - The selection sign item popover used a basic Many2Many field for tag selection, with limited customization and no option to edit existing tags. - Demo data for selection fields were absent. --- ### After this PR - All labels in the Settings have been updated to remove '.' for consistency. - The Validate button in the item popover has been renamed to save. - The kanban view has been visually and functionally improved to enhance usability. - The selection popover now uses a custom Many2ManyTagsField that allows editing tags directly in the UI. Users can switch to edit mode via an Edit button, make changes, and save or undo them seamlessly. Updates are synchronized with the backend in real time. - Demo data has been added for the selection field, providing ease of use. --- task- 3911221
Field service stock actions now open in a Kanban-style view on small devices instead of a list. This makes task selection easier and more practical for mobile users working in the field.
Original PR description
Currently, the list view opens on small devices, which is not ideal. In this commit, we have added a mobile view mode in the action. Now, when a user picks an action, the default Kanban view will open instead of the list view. task-4255387
Salespeople can now use route planning directly from the CRM map view when organizing customer visits. This makes it easier to plan efficient visit schedules and reduce time spent arranging travel between leads.
Original PR description
Allows salesperson to use the routing feature when planning their visits. Task-4247829
The Sign app can now auto-fill signing fields using data from any linked business record, not only the current contact. This reduces manual entry and makes signing templates more useful across different business processes.
Original PR description
Before this commit, the auto-complete feature only worked on the current partner. This commit ensure auto-completion is possible with any kind of model. If the sign.request is linked to that model, the field will auto complete his value. taskid: 4267478
Subscription reporting now records an effective date on each log entry so revenue calculations can distinguish invoiced activity from future or pending changes. This helps business teams filter out subscription changes that have not been invoiced yet, improving the accuracy of MRR reporting.
Original PR description
Before this commit, all logs were used to compute MRR. As a result it was not possible to filter out logs not invoiced yet. taskid: 4391586