Thursday, November 28, 2024
4 changes · 18.0
Enhancements to existing features
Odoo now initializes messaging and live chat data through a read-only startup route, reflecting that messaging setup no longer needs to change user settings. This reduces unnecessary write access during web client loading while preserving chat, onboarding, and notification behavior.
Original PR description
* = im_livechat, mail_bot, test_discuss_full Backport of https://github.com/odoo/odoo/pull/179352 OdooBot onboarding needs to be moved to webclient load. Write access is not useful since settings were moved out of the init messaging. See https://github.com/odoo/odoo/pull/150625
The email template previously labeled for portal signup is now named for inviting new internal users, reducing confusion for administrators. The mail template editor also adds a reminder that dynamic email values can be inserted with the `/field` command.
Original PR description
The mail template "Settings: New Portal Signup" has been renamed to "Settings: New User Invite" to reduce confusion. The previous name implied the creation of a new portal user account, which was misleading since the template is intended for creating new internal user accounts. Its new name should now better reflect its purpose. Additionally, this commit adds a small placeholder beneath the mail template editor. This placeholder serves as a helpful reminder for users to insert dynamic values into emails using the `/field` command. task-4273520 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This change separates unrounded and rounded tax values when preparing Mexican electronic invoicing and point-of-sale documents. It reduces ambiguity in tax calculations, helping make invoice and receipt totals more reliable and easier to maintain.
Original PR description
Before `_add_tax_details_in_base_line` populated tax details like `tax_amount_currency` directly, and `_round_base_lines_tax_details` subsequently moved these values to new keys prefixed with `raw_` while rounding the originals. The problem with that is the meaning of certain dictionary keys like `tax_amount_currency` changed depending on the method that processed them Now, `_add_tax_details_in_base_line` only adds raw values (e.g., `raw_tax_amount_currency`), and `_round_base_lines_tax_details` separately adds the rounded values This simplifies state management and makes sure that raw and rounded values are clearly separated. related pr: https://github.com/odoo/odoo/pull/187780 task: 4277573
This update adjusts automated tests to match a recent change in how messaging is initialized. It helps keep accounting and studio test coverage reliable without changing day-to-day user workflows.
Original PR description
Backport of https://github.com/odoo/enterprise/pull/69565