Wednesday, September 27, 2023
3 changes
New functionality added to Odoo
A new restaurant display lets customers see current orders grouped by preparation status. This helps staff keep customers informed using the same preparation tracking data already used by the kitchen display.
Original PR description
In this Pr we introduce a new module that enables restaurants to show their customers a display with all the current orders, filtered by their preparation state. In order to know the preparation state of the orders, we rely on the information provided by the `pos_preparation_display` module. Task: 3514516 https://github.com/odoo/odoo/pull/136065
Enhancements to existing features
Users can now choose the required cancellation reason for Mexican electronic invoices, including a guided flow for replacement invoices when reason 01 is needed. The update also adds retry actions for failed CFDI operations and prevents changes that could make signed or cancelled invoice data inconsistent.
Original PR description
task: 3102918
Features or functions removed from Odoo
New customers will no longer be able to install the Taxcloud integration, while existing customers who already use it can continue doing so. The change supports a planned deprecation path and allows the modules to be released under LGPL so others can maintain or migrate them if needed.
Original PR description
This commit stops new users from installing Taxcloud. Taxcloud will keep working for customers who already had it installed in a previous version. Our Taxcloud modules will be released under LGPL,…
This commit stops new users from installing Taxcloud. Taxcloud will keep working for customers who already had it installed in a previous version. Our Taxcloud modules will be released under LGPL, giving everyone the opportunity to migrate and maintain these modules for future versions if they have a need. This commit follows a similar approach to odoo/odoo@c9072dfe798d658246ca6fc255f95eb884a6d389. Using the installable flag in the manifest was considered but doesn't have the desired result: - module installation doesn't error, instead it remains in the “to install” state - this leads to errors when loading the registry [1], - this prevents crons from running The current approach still allows command-line manipulation which is needed for migration and allows us to keep the modules installed on runbot for support. Dependencies of account_taxcloud don't get this hook, this allows existing customers to still install the right bridge module if needed. If account_taxcloud is not installed, then installing a dependency of it errors as expected. An upgrade script isn't needed because upgrading any module will automatically sync the auto_install field from the manifests via ir.module.module's update_list(). [1] Some modules have inconsistent states, some dependencies may be missing: ['account_taxcloud'] task-3516826