Thursday, December 19, 2024
8 changes
6 changes
Enhancements to existing features
Users can now preview a Sign template before starting the signing process, helping them verify the document layout and fields in advance. This also makes it easier to review and adjust completed template content, reducing mistakes and rework.
Original PR description
Before this commit, it wa snot possible to preview a template before signing it. And once filled, it wasnot posible to edit it easily. taskid: 4283945
Payment numbering can now be managed separately for each payment method within the same journal, instead of using only one sequence per journal. This gives finance teams clearer tracking and reporting when a journal handles multiple payment types.
Original PR description
Currently, the sequencing ganularity for payments is set at journal level. With this commit, the granularity is moved down to the payment method of a journal. Now, one journal can have several sequences (1 for each payment method and a default one for the journal itself). odoo/odoo/pull/175330 odoo/upgrade/pull/6334 task-3925608
Point of Sale and preparation display screens get several usability improvements for restaurant workflows, including clearer order timing, better ticket navigation, and easier access to actions. Staff can also reprint the last preparation ticket and adjust the preparation display zoom, helping teams work more comfortably during service.
Original PR description
Point of sale: - Adding margin left on preset time on product screen. - Replacing ActionPad button "action" by 3 vertical dots - Allow to reprint the last prepration ticket - Adding number of orders by pages on ticket screen. - Removing seconds on the time of the order. - Resizing search bar on ticket screen. Preparation display: - Adding zoom parameter on the navbar - Removing waiter name. - Adding order floating name. - Adding preset name and time on orders. taskId: 4398826
Users can now sort spreadsheet pivot tables by right-clicking any pivot cell and sorting based on that column. This makes pivot analysis more flexible and easier to use, especially when comparing values across multiple columns.
Original PR description
This commit allows the user to right click on a pivot cell to sort the pivot on that column. We now stopped using the sorting from the web's `pivot_model` and use the sorting that is in `o-spreadsheet/SpreadsheetPivotTable` instead. Task: [3989395](https://www.odoo.com/web#id=3989395&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form)
The Trial Balance report now uses a dedicated reporting engine, making it easier to extend, localize, and audit report figures. Users will see clearer balance columns, better comparison handling, and improved country-specific variants for Colombia and Spain.
Original PR description
This update replaces the dynamic lines generator in the Trial Balance report with a custom reporting engine, offering enhanced flexibility and integration. Key benefits include support for…
This update replaces the dynamic lines generator in the Trial Balance report with a custom reporting engine, offering enhanced flexibility and integration. Key benefits include support for non-standard groupbys, seamless compatibility with the report engine, and risk-free combination with specific filters and horizontal groupbys. The custom engine also simplifies localization-specific customizations and allows for easier extensions. Additionally, this refactor fully decouples the Trial Balance from the General Ledger, resulting in independent, streamlined codebase for both reports. Cell-level auditing has been introduced, further enhancing report accuracy and traceability. Functionally, the report has minor changes. The initial and end balance columns are now displayed in a single column instead of two. In addition, an initial and end balance columns are displayed when comparing periods that are either non-adjacent or part of different fiscal years. The Colombian Trial Balance has seen significant improvements, now implemented as a Trial Balance variant with custom groupby keys. This refactoring has drastically reduced the custom code needed for the localization, making maintenance easier and the report more robust. Spain also see the introduction of a new variant for the trial balance. This variant simply adds a column "Period Total" which equals to Debit-Credit. Task-4256374 -> Spain new variant Task-3748928 -> General refactoring of the Trial Balance
Field Service task and reporting views now stay aligned with recent Project app view changes. The update ensures task analysis and task lists show the intended Field Service tasks instead of including unrelated subtasks.
Original PR description
Also, change "all_task", which was also falsy, for "my_tasks" with a truthy value. Related: https://github.com/odoo/odoo/pull/185912 task-4295713
2 changes
Enhancements to existing features
This update strengthens Odoo's mail testing around realistic email conversations on lead-like records, helping protect current behavior before upcoming email changes. It also prevents notification failures when a customer has an inactive language setting, improving reliability for multilingual customer communication.
Original PR description
PURPOSE
Add an email discussion like flow, on a lead-like model. This allows to
test a full discussion with some real-life use cases and see how it
behaves in current codebase.
Improve tools and asserts while doing so.
Fix an issue when having customer having a lang that is inactive.
NEXT
This is done in 18 in order to assert behavior and also ease future
changes. Indeed email flow is going to change in between Odoo 18 and
19 and it is a good practice to have a flow for the "current behavior"
not only the new one.
Prepares Task-4281157: [mail] Allow to alter email.message To
Prepares Task-4332797: [mail] Partner from emails 3.0
Prepares Task-4286232: [mail] Store email{cc/to} on mail.message
Prepares Task-4273569: [mail] Reply, Quotes, Expand and Forward
Prepares Task-4273479: [mail] Email-like recipientsCommission plans now take their active dates into account when comparing plans for the same user. This makes it easier for sales teams to spot overlapping or conflicting plans and keeps commission target totals aligned when target lines are manually updated.
Original PR description
Before this commit, other plans were not computed according to dates. As a result, it ws difficult to see when two plans were conflicting for one user.