Friday, June 14, 2024
8 changes
2 changes
Enhancements to existing features
Portal dashboard cards now avoid repeated counting during a user session once related records are known to exist. This reduces page refresh work and flickering, making the customer portal feel faster and more stable.
Original PR description
The counters are primarily used as boolean to determine whether or not to display the card. Therefore, as soon as you have one record, we can show the card without needing to recheck it later. In the…
The counters are primarily used as boolean to determine whether or not to display the card. Therefore, as soon as you have one record, we can show the card without needing to recheck it later. In the worst-case scenario, you might see a card pointing to an empty list view. This approach helps us avoid recalculating whether there is a record for this card on each refresh. The approach is to cache the counter in the session as soon as there are more than 0 records. This way, if there are no invoices but a sale order is validated, the invoice counter will be recomputed, and you will see the invoice card the next time. For the duration of the same session, we won't recompute it and will always display the invoice card. We only re-request the computation if the counter in the session was 0 or if we need to show the counter, as in this case, we want to display the most precise number. This approach will also avoid flickering when the view is updated. Since we already know the count, we can display the card immediately without waiting for the RPC callback. To further reduce flickering, we have moved the spinner to the bottom, preventing the content from shifting upwards once the loader disappears. On another note, we've updated the policy for the parallel RPC requests made to /my/counter. Instead of splitting the counter into 3 RPC calls, we now allow 5 counters per RPC, with a maximum of three RPCs. An update of the view portal.portal_docs_entry is required to benefit from this cache for /my/counter,
Deferred reports can now be grouped by product or product category, giving finance teams clearer ways to analyze deferred revenue and expenses. The underlying deferral generation remains grouped by account, preserving existing accounting behavior while improving report visibility.
Original PR description
We now allow grouping by other fields that account_id in the report, namely product_id, and product_category_id. However, for the deferral generation, we continue grouping by account_id. task-id 3925943 https://github.com/odoo/enterprise/pull/62534
6 changes
Enhancements to existing features
Payroll contract data now supports entering home-to-work distance with a selectable unit, allowing users to work in miles or kilometers where needed. Existing payroll calculation logic continues to use kilometers internally, while demo data and payroll tests across localizations were updated to use the new input field.
Original PR description
*= l10n_be_hr_contract_salary, l10n_be_hr_payroll, l10n_be_hr_payroll_account adding new selection field distance home-work unit for changing between miles and km changing field name from km_home_work to distance_home_work in data files,demo data and test case files of various l10n files km_home_work will be use for calculation in km and distance_home_work will be use for input Task-3888505
Users can now rearrange records directly in the map view when the view is configured for sequencing. This helps teams plan routes in the right stop order, making map-based routing easier and more flexible.
Original PR description
This commit allows to re-order records from the map view. It is useful for routing, which takes you from the first item to the last and uses intermediary ones as stops. With this commit, the map view displays a handle on each record when: - `default_order` is set on the map arch - `allow_resequence` is set to `true` on the map arch - the map view is not grouped by a field  Community PR : https://github.com/odoo/odoo/pull/168876 task-3636577
Employees can now share referral links more easily, including by SMS, and copy links directly without opening an extra sharing window. The referral page also has a cleaner, wider card layout and updated social sharing visuals, making the experience smoother and more modern.
Original PR description
This PR adds the ability to send a referral link via SMS by the use of a wizard, it improve the ux by making the referral cards take the full width of the screen, improve the looks of the button by the use of logos and update the twitter logo with x. Finally, this PR also remove completely the use of the referral link to share wizard and embed the link directly in the button (that was opening the referral link to share) to copy it directly to the clipboard.
This update refreshes how kanban-style cards are handled across several Odoo apps, including Accounting, Appointments, Documents, Sign, Marketing Automation, Field Service, Subscriptions, Rentals, and Social. It should make these card-based screens more consistent and reliable for users while supporting future interface improvements.
Indian payroll accounting is now linked with the accounting setup, helping payroll-related financial entries align with company accounts. This improves consistency between payroll processing and accounting records for businesses operating in India.
Original PR description
Add link with the accounting task-3387234
The spreadsheet locale indicator now appears in a neutral blue instead of red when the spreadsheet locale differs from the user's locale. This keeps users informed about date and number formatting expectations without implying that something is wrong.
Original PR description
there's currently a small globe on the top-right corner displayed when the spreadsheet locale is different than the user's locale. The goal is to draw attention of the user that he needs to write numbers and dates accordingly. The globe is currently red, which might be scary. The user might think something is wrong. This task changes the globe color to a more neutral "info" blue. Task: 3989485