Wednesday, November 22, 2023
3 changes · 17.0
Enhancements to existing features
This update improves how the Mail app creates sample data used for testing and demonstrations. It makes user and notification data generation faster and better balanced, reducing wait times while keeping the generated data useful.
This update removes outdated warning functionality from tax closing forms that was no longer working properly since version 16.4. Warning messages about tax control failures are now displayed only on the tax report itself, which is the standard workflow users follow anyway. This simplifies the system and ensures users see warnings in the right place.
Original PR description
The field tax_report_control_error defined on account.move was previously used to display a warning message on the tax closing's form view when some of the controls defined on the report failed. This…
The field tax_report_control_error defined on account.move was previously used to display a warning message on the tax closing's form view when some of the controls defined on the report failed. This was only used in l10n_be_reports at this point. From 16.4 on, this feature did not work anymore, because of the introduction of sections, and the fact the options dict is generated separately from the lines, and hence cannot be modified while these are being generated. https://github.com/odoo/enterprise/commit/9b3bb03f27a142d367310e6def856efd194b3006 already removed such a warning on the Belgian XML export wizard, and introduced a warning banner directly on the report to replace it. With this commit, we make the choice to remove the wanring on the closing move as well ; any regular tax closing flow should anyway go through the report, and then view the warning displayed there. Another PR will follow in master to finish removing the unneeded fields. Forward-Port-Of: odoo/enterprise#50910
The WhatsApp template variables are now displayed in a logical, organized sequence instead of appearing randomly. Variables are now sorted by type (Location, Header, Buttons, Body) making the interface cleaner and easier to use when setting up WhatsApp message templates.
Original PR description
Before This Commit: Currently, the variables are not populating in the proper sequence. It makes the variable tab look untidy. After This Commit: Sequence the variables with variable type in the sequence Location Defaults > Header > Buttons > Body Variables Solution: used the _order attribute to sort the variables in the order of variable type and placeholder 1. location - address 2. location - latitude, longitude 3. location - name 4. header 5. button 6. body Task - 3516187 Forward-Port-Of: odoo/enterprise#48526