Wednesday, October 18, 2023
5 changes · master
New functionality added to Odoo
Odoo now supports Spain's mandatory Modelo 390 annual tax report, which consolidates Modelo 303 VAT information and adds required annual details. Spanish tax reports were also adjusted to better support tax-unit reporting across companies and clearer report sequencing.
Original PR description
In Spain, the modelo 390 is a mandatory annual tax report that compiles the modelo 303 informations, while adding extra informations. Introduced said report, while adapting to account recent changes made to the reporting engine. task-2894615
Odoo now adds a reusable history feature for HTML fields, letting users see recent content changes and restore earlier versions when needed. This helps teams recover from accidental edits and compare document versions directly in the interface.
Original PR description
Create a new model mixins that allow other model to activate the history feature on html fields. This history automatically track the changes on the related html field and allow the user to revert to a previous version at any time. This also introduce a new widget that can be used in Odoo view to display the recent changes directly, with option to revert to specific recent changes directly in the UI. Enterprise PR: odoo/enterprise#37211 task-3039787 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Self-order kiosks can now generate and print customer receipts, initially using Epson printers over HTTP. Receipt printing was also simplified and standardized across Point of Sale, making it easier to support new sales environments and maintain consistent receipt layouts.
Knowledge articles now keep a history of body changes, making it easier for users to review edits and restore earlier versions when needed. The Knowledge interface also shows recent changes directly, improving confidence and control when collaborating on important content.
Original PR description
Use the new Field HTML history feature to have history on knowledge article. This history automatically track the changes on the article body and allow the user to revert to a previous version at any time. This also use the new html field history widget to display the recent changes directly in the Knowledge UI. Community PR: odoo/odoo#112957 task-3039787
Spanish accounting now supports the annual Modelo 390 tax report and its official BOE export file, helping businesses meet mandatory year-end VAT reporting requirements. The update also improves multi-company tax unit handling and report sequencing for Spanish tax forms.
Original PR description
In Spain, the modelo 390 is a mandatory annual tax report that compiles the modelo 303 informations, while adding extra informations. Introduced said report, while adapting to account recent changes made to the reporting engine. task-2894615
Original PR description
### [REF] pos*: use /report for qr code generation pos*: point_of_sale, pos_online_pay In this pr we remove the custom generation of qr codes and adapt the codebase to rely on the `/report/barcode`…
### [REF] pos*: use /report for qr code generation
pos*: point_of_sale, pos_online_pay
In this pr we remove the custom generation of qr codes and
adapt the codebase to rely on the `/report/barcode` api.
Task: 3550015
### [REF] pos*: simplify receipt printing
pos*: l10n_co_pos, l10n_fr_pos_cert, l10n_gcc_pos,
l10n_in_pos, l10n_sa_pos, point_of_sale,
pos_epson_printer, pos_loyalty, pos_mercury,
pos_online_payment, pos_restaurant, pos_sale
There is a need to print pos receipts in new environments,
such as the kiosk. In this commit we simplify the steps to
generate the receipt data and introduce a portable mechanism
for printing.
Changes:
- removed the `getOrderReceiptEnv` method; this method
was returning a lot of data that the receipt was not
actually using; we now simply use the data from
`Order.export_for_printing`. This means that it will be much
easier to recreate this data in other environments, such
as in the kiosk.
- removed the error prone `generate_wrapped_product_name` method.
It's aim was to split the orderline name, but this task is much
better accomplished by declarative css.
- removed the `Orderline.export_for_printing` method; instead,
we simply use the existing `Orderline.getDisplayData`;
- removed the `AbstractReceiptScreen` component and replaced
it's functionality with the new `printer` service;
- using this service means that we were free to remove
the `pos-receipt-print` div from the root of the pos app;
- made the receipt be a standalone component. It thus benefits
from all the advantages of components, such as prop validation
and usage of slots;
- replaced the `OrderLinesReceipt` template with the generic
`OrderWidget` component'; this greatly simplifies the code;
- created the `renderer` service. It's goal is to do for components
what `renderToElement` does for templates; we use this service to
render the receipt component for printing;
- removed jquery from the EpsonPrinter class, such that it can be
imported into projects that do not rely on jquery;
- created the `ReceiptHeader` component. This unifies the header
between all the different receipts; ( before, each receipt was
implementing it's own header )
Task: 3547597
### [IMP] pos_self_order: enable kiosk receipt
*point_of_sale, pos_self_order, pos_self_order_epson_printer
In this commit we introduce the functionality that allows
the pos_self_order module to generate receipts.
At the moment, this is possible by using Epson Printers via HTTP.
This is done through the use of the newly added bridge module
`pos_self_order_epson_printer`.
In order to generate the data required for the receipt we add more data
on the first load of the kiosk ( such as company information ) and
also in the `_export_for_self_order` method.
Printing is done through the `printer` service from POS.
Task: 3487638
https://github.com/odoo/enterprise/pull/48304
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr