Thursday, December 12, 2024
7 changes · 18.0
Enhancements to existing features
Currency translation adjustments now use the exchange rate from the end of the fiscal year instead of the current rate, making balance sheet reporting more accurate for past periods. The update also corrects average exchange rate calculations when a period begins without a recorded currency rate, preventing understated values.
Original PR description
The way we initially implemented CTA, it was using the current rate for all the balance sheet accounts. Instead, we actually want to consider the closing rate ; that is, the rate of each currency at the end of the fiscal year the operation was made in. Current rate currency translation is still applied like before when CTA is not enabled on the report. task-4270102 ================================= [FIX] account: currency table: fix average rate for a period starting with no res.currency.rate If a period containing some res.currency.rate object starts by some sub-period without any range, the average rate computation considered this sub-period as having a rate of 0. It's wrong; it should be 1.
The messaging menu now presents notifications with clearer wording, better spacing, and more readable previews. Users can more easily distinguish installation prompts, push notification requests, chat messages, and delivery failures, especially on mobile.
Original PR description
Before <img width="480" alt="Screenshot 2024-12-12 at 12 53 27" src="https://github.com/user-attachments/assets/31e6def5-5899-4947-b3e2-5fddd73284d1" /> After <img width="481" alt="Screenshot 2024-12-12 at 12 58 59" src="https://github.com/user-attachments/assets/055cd267-fbc1-407b-b544-72b9cfcebb53" />
Opening the mail template list is now more reliable for companies with very large numbers of templates. The filtering process has been optimized to avoid memory issues and improve performance.
Original PR description
Before this commit, databases with thousands of mail templates could trigger a MemoryError when opening the mail template list. This issue occurred because the default filter on base templates required processing all records batch by batch in Python. With this commit, the computation is rewritten to use domain / SQL, eliminating the Python overhead.
When users open the full email composer from the chatter, their email signature is now automatically added to the message. This lets users review and adjust their signature before sending, improving consistency and control over outgoing emails.
Original PR description
When the user opens the full mail composer from the chatter, their signature will now automatically be inserted at the end of the email. This change allows the user to view and edit the signature when writing an email. task-4273520 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Sales commissions can now be calculated from invoices and recurring subscription plans, not only from subscription MRR logs. This helps ensure salespeople can receive commission for renewals or unchanged contracts even when no new subscription log is created.
Original PR description
Before this PR, it was not possible to override achievement report sql request.
Before this PR, subscription achievements were only available
throught MRR (sale.order.log) analysis. It would prevent to provide
commission when no log was created during a period. This could happen
when an important contract is renewed at the same conditions.
This commit allows to compute commissions based on
invoices and recurring plans.
Task 4398351Financial reports now use the year-end exchange rate for CTA calculations, making balance sheet currency translation more aligned with accounting expectations. Additional checks improve rate handling and Trial Balance consistency so report figures remain reliable across periods.
Original PR description
The way we initially implemented CTA, it was using the current rate for all the balance sheet accounts. Instead, we actually want to consider the closing rate ; that is, the rate of each currency at…
The way we initially implemented CTA, it was using the current rate for all the balance sheet accounts. Instead, we actually want to consider the closing rate ; that is, the rate of each currency at the end of the fiscal year the operation was made in. Current rate currency translation is still applied like before when CTA is not enabled on the report. task-4270102 ========================================================================== [IMP] account_reports: currency table: add test case If a period containing some res.currency.rate object starts by some sub-period without any range, the average rate computation considered this sub-period as having a rate of 0. It's wrong; it should be 1. The fix itself is in the corresponding community commit ; this one adds a check ensuring this doesn't break again in the future. Fixing this also revealed an issue in the Trial Balance, where the initial balance column group was computed with different rates than the rest of the report, which is not what we want for this instance. We fix that by properly setting the period_key on all of its column groups and ensuring the initial balance dates have no impact on the currency table.
Businesses can now choose whether UrbanPiper point-of-sale requests go to the live production service or the integration testing environment. This makes it safer to test setup changes before using them with real orders.
Original PR description
In this commit: === - Added `pos_urban_piper.is_production_mode` parameter to toggle between production and integration environments.