Thursday, May 15, 2025
4 changes · saas-18.3
Enhancements to existing features
The live chat demo content has been expanded to show sessions that require specific expertise. This helps business users and evaluators better understand how support routing and chatbot scenarios can work in realistic examples.
Original PR description
Purpose of this commit: To add demo data related to the expertise that the session required. task-4762961
This update adds new ISO-based date options for sequence numbers, helping businesses generate order or document references with internationally recognized week numbers. Existing sequence formats continue to work unchanged, reducing disruption while allowing more accurate configuration where needed.
Original PR description
Steps ----- 1. Configure the sale order sequence to use `%(woy)s` as suffix; 2. confirm a new sale order in 2025. Issue ----- The week number used in the generated name is off by one from the…
Steps ----- 1. Configure the sale order sequence to use `%(woy)s` as suffix; 2. confirm a new sale order in 2025. Issue ----- The week number used in the generated name is off by one from the expected ISO 8061 week number. Cause ----- The date interpolation used for sequences, passes `%W` to `strftime` to get the week of the year. This uses a non-standard method, starting with the first monday located in the year (2025-01-06)[^1]. The ISO 8061 method starts counting from whatever week has January 4 in it (i.e. first week with at least 4 days), with weeks starting on Monday (2024-12-30). To get this result from `strftime`, `%V` needs to be used in the format string. Solution -------- In order to not break existing week-based sequences, add ISO 8061-based format specifications alongside the current ones: - ISO 8061 week number `%V` → `%(isoweek)s` - ISO 8061 week-based year w/ century `%G` → `%(isoyear)s` - ISO 8061 week-based year w/out century `%g` → `%(isoy)s` opw-4606876 [^1]: https://www.man7.org/linux/man-pages/man3/strftime.3.html
Portal profile updates now check whether a new login is already in use through a simpler lookup instead of creating an extra database checkpoint. This improves performance for a rare validation scenario while keeping the uniqueness check in place.
Original PR description
When updating the login in the form, the code creates a savepoint, that we want to remove for performance reasons, to check if the login is unique. Since it is improbable that 2 concurrent transactions would want to use the same login, we remove the savepoint and do the check using a search. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Accounting and Ecuador localization screens now use the standard tax display format after related platform changes. This keeps tax names consistent across forms and search fields, reducing confusion for users working with invoices, products, reimbursements, and withholding flows.
Original PR description
With the removal of custom tax components in the corresponding community commit, views need to be updated to use the standard display_name and markdown formats now available. No Task