Monday, June 2, 2025
7 changes
5 changes
Enhancements to existing features
When a commission plan start date is moved later, linked salesperson start dates that fall before the new plan date are updated automatically. This reduces manual cleanup and keeps commission eligibility dates aligned with the active plan period.
Original PR description
Before: - Changing the plan start date didn't update linked salespersons' from dates. - Users had to manually update each salesperson's from date. After: - Whenever the commission plan’s start date is changed — whether to an earlier or later date — the start date of all salespersons linked to it will be updated to match the new plan start date. task:4601225
The Sign and itsme signing modules now use the newer testing approach, replacing older test cases. This improves confidence in electronic signing workflows while keeping the change internal and not altering day-to-day user features.
Original PR description
Hootfication of Sign Modules task-4452228
This update adds coverage to ensure HTML content used by AI fields is properly sanitized, helping reduce the risk of unsafe or malformed content. It also raises the API call timeout, making related AI operations more tolerant of slower responses.
Original PR description
Task-4712395
The Indian localization Balance Sheet no longer opens with the horizontal split option enabled by default. This gives users a simpler default report view while still allowing them to enable the split manually when needed.
Original PR description
- before this commit: split horizontally is ticked by default on Balance Sheet. - after this commit: split horizontally is unticked by default. - Task ID: 4836667
The Planning Holidays test coverage has been updated to match the newer email-based notification flow for leave requests. This helps ensure the right responsible person is still notified when leave is created, reducing the risk of unnoticed absences in planning workflows.
Original PR description
This PR improves the test cases related to notifying the responsible person when a leave is created. Previously, the notification triggered an activity, which also invoked the compute function during the process. Now, since the notification is sent via email instead of creating an activity, the compute function is no longer automatically triggered — so it needs to be called explicitly. task-4681107
2 changes
Enhancements to existing features
This update speeds up processing of historical point-of-sale orders when upgrading to Odoo 18 or enabling French POS certification on an existing database. Large databases that previously spent close to an hour preparing order links can now complete the same step in about a minute, reducing upgrade downtime and deployment risk.
Original PR description
**Patch description:** - This commit addresses a perf issue in the `_compute_previous_order` compute of the `pos.order` model, which is particularly noticeable during db upgrade from `v17.0` to…
**Patch description:** - This commit addresses a perf issue in the `_compute_previous_order` compute of the `pos.order` model, which is particularly noticeable during db upgrade from `v17.0` to `v18.0` because field `previous_order_id` got introduced in `v18.0` or when installing the `l10n_fr_pos_cert` module on an existing db with many POS orders in `v18.0`. - In both cases, the compute method is triggered for all `pos.order` records to assign the `previous_order_id`, causing significant delay due to per-record lookups. **Example from a real DB with ~113k orders:** ```sql apan_2840187=> select count(*) from pos_order; count -------- 113342 (1 row) ``` **Observation:** - Before the fix (compute took nearly 50 minutes): ```py 2025-05-29 06:31:12,587 28 INFO apan_2840187_18.0 odoo.modules.registry: module l10n_fr_pos_cert: creating or updating database tables 2025-05-29 06:31:12,799 28 INFO apan_2840187_18.0 odoo.models: Prepare computation of pos.order.previous_order_id 2025-05-29 07:17:37,855 28 INFO apan_2840187_18.0 odoo.modules.loading: loading l10n_fr_pos_cert/views/pos_views.xml ``` - After the fix (completed within 1 min): ```py 2025-05-30 06:56:59,510 24 INFO apan_2840187_18.0 odoo.modules.registry: module l10n_fr_pos_cert: creating or updating database tables 2025-05-30 06:56:59,584 24 INFO apan_2840187_18.0 odoo.models: Prepare computation of pos.order.previous_order_id 2025-05-30 06:57:12,531 24 INFO apan_2840187_18.0 odoo.modules.loading: loading l10n_fr_pos_cert/views/pos_views.xml ``` **Note:** The issue reported in the OPW was not originally about perf, but it was clearly exposed during the upgrade of the mentioned db. opw-4812874 upg-2840187 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The accounting dashboard now shows the "Fetch from CodaBox" action as a link-style button. This improves spacing and alignment with nearby actions, making the dashboard look cleaner and easier to use.
Original PR description
The "Fetch from CodaBox" link displayed on the accounting dashboard had no gap between it and the button at the left of it, and wasn't aligned horizontaly with the other buttons next to it making it look out of place. It is now displayed as a link button, which solve both problems. task-4671468 Purpose The fetch from CodaBox is too sticky to the upload button  After this commit : 