Daily updates from Odoo
Monday, October 21, 2024
8 changes
1 change
Enhancements to existing features
Users now see one consolidated warning when invoice lines or products have missing or invalid HSN codes, instead of repeated alerts. This makes E-waybill creation smoother and easier to correct, including for service products and inventory flows.
Original PR description
Before this PR: - If the HSN code was missing or invalid in multiple lines, an alert message was displayed multiple times with the product label. Additionally, the HSN warning wasn't displayed for service-type products in invoices. - In the inventory module, HSN validation occurred twice when creating an E-waybill. After this PR: - The alert message is displayed only once. A single button allows the user to list view of invoice lines with invalid or empty HSN codes and an HSN warning will be displayed for all types of products in invoices. - HSN validation will occur only once during the final generation of the E-waybill in inventory, with the error message showing only once for all invalid or empty HSN products. A single button redirects to the list view of all those products. **task**-3660731
3 changes
Enhancements to existing features
Payment terminal credentials can now be stored once and reused across multiple point-of-sale terminal methods from the same vendor. This reduces duplicate setup work, saves time when adding payment methods, and makes terminal configuration easier to maintain.
Original PR description
Before this commit: ========== - Previously, there was no model for storing mandatory credentials for different terminal methods. - So, it was necessary to enter the same credentials with different terminal IDs for various payment terminal methods provided by the same vendor. - This resulted in the duplication of credentials. After this commit: ========== - So, we are introducing a new 'pos.payment.provider' model for storing the same mandatory credentials in one model. - We allow credentials to be entered once and used across multiple terminal payment methods. This enhancement streamlines the function of payment terminals and saves time when new payment methods are created. Related PR: - Community: odoo/odoo#172471 - Upgrade: odoo/upgrade#6248 task-3506646
Knowledge now uses database indexes better for article permissions and hierarchy lookups, while removing indexes that were not useful. This should reduce server response times, especially when opening large Knowledge article lists or checking access rights.
Original PR description
This PR aims to optimize Knowledge by appropriately setting SQL indexes on the fields that are frequently used to join tables and filter out records. The new indexes should help reducing the server…
This PR aims to optimize Knowledge by appropriately setting SQL indexes on the fields that are frequently used to join tables and filter out records. The new indexes should help reducing the server response times. For the `knowledge.article` model: 1. Remove the `is_article_item` index Setting an index on a boolean field is generally speaking not recommended as the field has only two possible values and does not allow us to discriminate the records efficiently. Indeed, the index will be used only when searching for an uncommon boolean value. In the other cases, the index does not provide much benefit compared to a full table scan. PostgreSQL will then favor another index that will better reduce the search space of the query. 2. Remove the `category` index The index set on the `category` column is almost never used as we never search for articles based on their categories and we never join tables based on that value. The index could be used when the user applies a search filter in the list view but, in that case, PostgreSQL could use another index that better discriminate the records. 3. Add index on `parent_id` The `parent_id` field is heavily used in the user's permission computation. Adding an index for that field will ensure that we can quickly explore the article hierarchy and compute the user's permissions efficiently. For the `knowledge.article.member` model: 1. Add index on `article_id` The `article_id` field is heavily used in the user's permission computation. Adding an index for that field will ensure that we can quickly compute the user membership on the article. task-4046060
Missed call notifications for VoIP are now shown directly on the phone icon in the top bar instead of as separate top-bar text. This makes call alerts easier to find while keeping the interface cleaner, and the call dropdown no longer opens automatically by default.
Original PR description
<h3>PURPOSE</h3> - Move missed call notifications in the top bar text to the top icon <h3>SPECIFICATION</h3> - Move the VOIP missed called counter to the systray item, like as discuss. - Stop opening the dropdown by default. Task-3392951
3 changes
Enhancements to existing features
Point of Sale now warns users when customer account payments may not show due balance tracking because the needed settlement module is missing or the order is not invoiced. This helps cashiers understand why balances are not visible and what needs to be done to track them correctly.
Original PR description
If a user uses the "customer account" payment method without having the `pos_settle_due` module installed or w\o invoicing the order, they will not be able to observe the due balance computation. In this pr we add a notification that explains this to the user. Task: 4251746 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Product and combo configurator logic was moved into reusable model-level behavior so Odoo customizations and subscription-related overrides are applied consistently. This improves reliability for sales and website sales flows and also corrects crossed-out price displays in configurators.
Original PR description
This allows to rely on the framework's inheritance instead of python's inheritance. Indeed, there was an issue where `sale_subscription` overrides were ignored by the framework. This change applies to both the product and combo configurators (and extracts any duplicated logic into shared methods). This change also fixes the strikethrough price in combo and product configurators. task-4263961 Enterprise PR: https://github.com/odoo/enterprise/pull/70533 Closes https://github.com/odoo/odoo/issues/179816
Product and subscription configurator logic has been moved into the standard business model layer so module-specific rules are applied consistently. This fixes cases where subscription-specific behavior could be skipped, improving reliability for sales, rentals, and website subscription flows.
Original PR description
This allows to rely on the framework's inheritance instead of python's inheritance. Indeed, there was an issue where `sale_subscription` overrides were ignored by the framework. This change applies to both the product and combo configurators (and extracts any duplicated logic into shared methods). task-4263961 Community PR: https://github.com/odoo/odoo/pull/181135
1 change
Enhancements to existing features
Odoo now supports Chinese Yuan (CNY) currency exchange rates from the Banxico provider. Previously, only USD, EUR, JPY, and GBP were available. This expansion allows businesses operating in or with China to access live currency conversion rates through the same Banxico data source.
Original PR description
Currently, Odoo supports several currencies (USD, EUR, JPY, GBP) for Banxico data parsing, but CNY (Chinese Yuan) is missing. This commit adds support for CNY in the list of currencies retrieved from Banxico’s API (through iap proxy). related pr: https://github.com/odoo/iap-apps/pull/912 task-4205613