Thursday, April 11, 2024
6 changes · 17.0
Enhancements to existing features
This update adds comprehensive unit tests for the document activity view feature, ensuring that document archiving works correctly. The changes also improve code efficiency by consolidating service loading into a shared utility function, reducing duplication across multiple test files.
Original PR description
Purpose ======= Add unit tests for the document activity view Test the fix of document archiving in the activity view PR: odoo/odoo/pull/151741 Task: 3704340 Load the services in a utils function to remove code redundancy. Task-3714544
This update enhances Chilean electronic point-of-sale receipts by adding a bidimensional (2D) code and displaying the requirements needed for valid electronic document compliance. This improvement ensures receipts meet Chilean regulatory standards for electronic documents and provides customers with a verifiable digital receipt.
Original PR description
This is a backport of odoo/enterprise#58479 This commit adds the bidimensional code on the receipt, it also adds to the receipt header the requirements for considering the receipt as a valid electronic document. task-id: 3747828 Community PR: odoo/odoo#161342
The German tax number (Steuernummer) validation has been moved from the tax report generation process to the company form, where it now triggers immediately when users enter the information. This ensures data quality at the point of entry rather than later during report generation, preventing invalid data from being saved in the first place.
Original PR description
Steuernummer was being validated at tax report xml generation. The check was moved to the company form view. It should be a constraint raising when trying to set the steuernummer to the company; there is no point in only checking it at XML generation. task-3809218 Forward-Port-Of: odoo/enterprise#60479 Forward-Port-Of: odoo/enterprise#59348
This update improves how Odoo handles shipping methods when databases are copied for testing or staging. Previously, all shipping methods were disabled during this process. Now, only shipping methods that connect to external providers (like real courier services) are disabled, while internal shipping methods based on fixed prices or custom rules remain active. This allows teams to continue testing order fulfillment workflows without losing their standard shipping options.
Original PR description
Only delivery carriers that can communicate with the outside should be deactivated. Every time a database is neutralized, all delivery carriers are deactivated. In staging or test databases this should not be the case, only delivery carriers with an external connection, i.e. delivery carriers with an external provider should be deactivated. Delivery carriers with fixed price or based on rules should not be deactivated with every neutralization. This way Odoo can continue to operate with shipping methods without prejudice to the users in neutralized databases. @moduon @yajo @Shide MT-5612 Description of the issue/feature this PR addresses: Current behavior before PR: Deactivated every delivery carriers. Desired behavior after PR is merged: Deactivated only delivery carriers with external provider. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#160443
This update enhances the Point of Sale receipt functionality for Chilean businesses by adding support for bidimensional codes. This improvement aligns with Chilean regulatory requirements for receipts, making the system more compliant with local standards and improving the receipt documentation process.
Original PR description
This is a backport of odoo/odoo#159671 This commit adds the requirements in order to add the bidimensional code on the receipt of the point of sale for the Chilean localization. task-id: 3747828 Enterprise PR: odoo/enterprise#60451 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The German tax number (Steuernummer) validation has been moved from the tax report generation stage to the company form, where it now validates immediately when the field is updated. This ensures invalid tax numbers are caught early and prevents errors during report generation. The field is now also visible for multi-VAT company configurations.
Original PR description
Steuernummer was being validated at tax report xml generation. The check was moved to the company form view. Moreover, the field was set visible in the company form view for multivat. It should be a constraint raising when trying to set the steuernummer to the company; there is no point in only checking it at XML generation. task-3809218 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#161395 Forward-Port-Of: odoo/odoo#159057