Daily updates from Odoo
Monday, September 23, 2024
3 changes · master
Code cleanup and technical improvements
The Print & Send flow now lets businesses define a preferred invoice delivery channel per customer, such as email, post, manual download, or Peppol. This reduces duplicate invoice delivery, supports required government declarations, and makes batch invoice sending more reliable and easier for accounting teams.
Original PR description
Refactoring of the Print & Send: Why ? Invoicing communication channels have multiplied with the advent of electronic invoicing. Clients want to receive PDF and electronic formats (UBL, Factur-X,…
Refactoring of the Print & Send: Why ? Invoicing communication channels have multiplied with the advent of electronic invoicing. Clients want to receive PDF and electronic formats (UBL, Factur-X, Factura-e,...) in different ways (email, peppol, post, ...), depending on the localization and their needs. Mandatory B2G declarations of invoices are also multiplying. The current Print & Send allows for that flexibility, but at the cost of becoming: - quite messy: you have many checboxes that you can chose at the same time with different meaning (B2B, B2G, sending method,...) - hard to use in batch: as you can't setup invoice channel by partner, you need to chose each time you click on Print & Send. Then some magical things happen to apply the right checkbox to the right invoices. - technically complicated: because some options are about format, some about how to send, about one or more invoices. - the current solution invites the user to "multiply the channels", by clicking everything and send his invoices to his customers via all the channels possible. This creates a situation where E-Invoicing creates a mess for accountants that receive the same invoice via multiple sources, further causing potential duplicates, double payments, etc. How ? - Choose ONE channel of communication per partner to send his invoice (by Post, manual (download), by Email, by Peppol) - Synchronize mandatory B2G declaration with invoice sending - Choose if a B2B E-invoice format needs to be generated (UBL, Factur-X, Factura-e,...) - Make invoice batching sending easy by applying selected defaults, this also mean B2G declarations will be applied by default if relevant. - We also added at partner level the possibility the select an invoice report template, as well as mail templates. task-4070132
This update standardizes internal naming used by kanban-style views across several Odoo apps. It helps keep the interface framework consistent and easier to maintain, with little expected change for day-to-day users.
Original PR description
Kanban templates have been reworked. In the new API, the main template is named kanban-card instead of kanban-box. The Activity and Hierarchy views follow a similar API, with their main templates being activity_box and hierarchy_box, respectively. The goal is to standardize these three views by defining a similar rendering context available in the arch. As part of this effort, we have renamed kanban-card to card and kanban-menu to menu. Task-4169388
This update removes an unused internal styling marker from Kanban action buttons across several Odoo apps. It helps simplify the user interface code without changing how users interact with the affected screens.
Original PR description
Action buttons (i.e. `<a>` or `<button>` tags) automically came with two classnames: `oe_kanban_action` and `oe_kanban_action_${tagName}`. The latter wasn't really necessary, so this commit removes it.
Part of task~3992107 aiming at simplifying kanban views