Thursday, March 14, 2024
5 changes · saas-17.1
Enhancements to existing features
This update enhances the user experience by ensuring that POS categories are consistently accessible throughout the Point of Sale interface. Previously, categories were hidden, making it less convenient for users to manage products. This change improves workflow efficiency and simplifies product organization within the POS system.
Original PR description
POS categories should be accessible at all times. Back-port of: fd30d8220c7bb6a399aa18654322a20b53ddd76c Task-3673139 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
This update improves the speed of spreadsheet evaluations, particularly for the 'BE Timesheet' dashboard on odoo.com. By returning error values instead of throwing errors during loading, the initial evaluation time has been reduced by approximately 20%, leading to a smoother user experience.
Original PR description
At the initial evaluation of a spreadsheet with pivots/lists, almost all cells are in error because they are loading. But throwing errors is slow. With this commit, instead of throwing loading errors for every single cell, the error is returned. This commit improves the first evaluation time of spreadsheet the "BE Timesheet" dashboard on odoo.com by ~20%, from ~1716ms to ~1365ms (master) Task: 3736190 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update resolves an issue where time-off reports were missing details for leave allocations. A recent change removed a key field, preventing the system from correctly linking to the allocation record. This fix ensures that all time-off reports accurately display the associated allocation information.
Original PR description
Steps to reproduce: ------------------- - go to time-off analysis (by type); - group by "Requet Type" and use list view; - click on an allocation; Issue: ------ We don't have the record for this allocation. Cause: ------ Commit [^1] removes the `allocation_id` field, so it is no longer possible to retrieve a record from the `hr.leave.allocation` model. Solution: --------- Place the allocation id in the `leave_id` field and use the `leave_type` field to determine the model (`hr.leave` or `hr.leave.allocation`). opw-3748884 [^1]: a1949ca541d760462add25995f139d1fb59f27d8 Forward-Port-Of: odoo/odoo#157204
This update resolves issues with the karma wheel's display, specifically addressing text overflow and incorrect rank calculations. The fix adjusts the wheel's size and text formatting to ensure accurate and consistent presentation across languages, improving the user experience.
Original PR description
How to reproduce: - Install "French" for the website - log out and log in as demo - Go to the front-end and click on "Courses" The design of the karma wheel is broken because the translation for "Get…
How to reproduce:
- Install "French" for the website
- log out and log in as demo
- Go to the front-end and click on "Courses"
The design of the karma wheel is broken because the translation for "Get 7.5k< xp to level up!" displayed in the wheel is too large ("Obtenez 7.5k xp pour passer au niveau supérieur"). While in French the text go outside the wheel and it appears clearly broken, it is also the case in English as the rank name is hidden due to the length of the text (for example when gaining one karma: 7.49k is displayed instead of 7.5k which takes more place).
To avoid modifying the template "profile_next_rank_card" that could break community overrides, we solve this problem in css by increasing the karma wheel size and the precentage of width occupied by the text inside the wheel. We also reduce the vertical margin between the rank name and the descriptive text and reduce the line height to avoid the text to overlap with the wheel. And if the text is still too large for some language it will be truncated and an ellipsis will be used.
Technical note: we do the change in website_profile.scss (and not in website_slides.scss) because it applies to both karma wheel: the one on course home page and the one in the profile page.
[FIX] gamification: fix incorrect next rank
How to reproduce:
- Install website_slides with demo data
- Connect as admin
- Go to the front-end and click on "Courses"
The karma wheel shows 100%, "master" and a karma of 2.5k xp while it should be: 4% on the wheel, "Doctor", 2.5 / 10k (karma_min for master is at 20k and next level is doctor at 10k).
We solve that issue by fixing the method that determine the next rank (see technical note for more details).
Technical note: the problem occurs because the admin user has the rank 4 but its field next_rank_id is null while there is a level 5. In that condition, the method _get_next_rank returns an empty recordset while it should return the rank 5. We simplify that method to always return a rank if there is one suitable (if you reach the last level, there are no next level).
(Initial PR in saas-16.1: odoo/odoo#151372)
Task-3617054
Forward-Port-Of: odoo/odoo#157585This update prevents users from completely removing the l10n_mx_edi module within Odoo's settings. This ensures continued compliance with Mexican tax regulations and avoids potential disruptions to financial reporting. The change maintains the integrity of our Mexican tax functionality.
Original PR description
--- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#157439