Thursday, February 1, 2024
5 changes · 17.0
Enhancements to existing features
This update adds a helpful guide next to the visibility field in website pages to clarify how to restrict access by groups. Previously, when users selected "Restricted Groups" as the visibility option, there was no clear indication of where to specify which groups should have access. The improvement directs users to the groups field located in the Access Rights tab, making the feature more intuitive and reducing confusion.
Original PR description
Commit [1] introduced a way to "hide" an ir.ui.view through a new visibility field. That field has multiple possible values to restrict the access. One of those is "Restricted Groups", but when selected it's really hard to figure what to do next because nothing happens on screen: there is no "groups" field where to add the groups. Those groups should actually be added a bit below, in the groups_id field which is "hidden" inside the "Access Rights" second tab. This is because the groups_id field already existed (in base module) before introducing the website visibility feature which just relied on that field when set to "Restricted Groups". Note that another possible value for visibility is "Password", and in this case a password field appear below the visibility field as one would expect. [1]: https://github.com/odoo/odoo/commit/e239934abe456257c9dc285d1ad9829c0353900c 
This update adds a new feature to the Point of Sale system that allows users to show or hide product and category images in the POS interface. Users can now toggle this setting on demand, giving them more control over the display layout and potentially improving performance or reducing visual clutter based on their preferences.
Original PR description
In this commit we add the ability to toggle between showing and not showing product and category images in the pos ui. Because this change is done in stable, we store the user's selection in `ir.config.parameter`. In the forward port, this will be removed and the settings will be stored in `pos.config` Task 3704416 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update adds support for two missing payment statuses from Mercado Pago: "Authorized" (for bundle payments awaiting capture) and "Cancelled" (for payments that expire). These changes prevent confusing payment records and ensure customers can properly manage transactions that would otherwise get stuck in draft status.
Original PR description
Although the lack of these statuses does not block the flow of a transaction, they create confusing records for the user. The new states are: Authorized: it is returned by Mercadopago when it authorizes payments by bundle. It should behave as a pending payment as it's not yet captured and could still be canceled by timeout. Cancelled: It is returned by Mercadopago when a payment is not made within the expected timeframe. This prevents odoo from leaving payment transactions in draft that cannot be cancelled by the customer. adhoc ticket = 68407 Forward-Port-Of: odoo/odoo#151828 Forward-Port-Of: odoo/odoo#150435
This update improves the stock management system by preventing redundant data writes that were triggering unnecessary background processes. The change adds checks to avoid rewriting values that haven't actually changed, resulting in faster and more efficient inventory operations without affecting user-facing functionality.
Original PR description
As long as the framework is not able to avoid rewriting values that are already set, we must add checks to avoid triggering multiple processes linked to that value assignment. Example: https://github.com/odoo/odoo/blob/66c11acdbedf8d1bcae6deb8ec54c5da5a3ae16d/addons/stock/models/product_strategy.py#L111 https://github.com/odoo/odoo/blob/11d81b2145e95c50481101a63d3ad1d244279af4/addons/stock/models/stock_move.py#L302-L341 https://github.com/odoo/odoo/blob/daea3d4e10b8fc2c4840fff30474a1203eff55c2/addons/sale_stock/models/sale_order.py#L402-L418 It may be unusual for a field to compute stored depending on a non-stored, but the reality is this. @Tecnativa TT45883 TT45999 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#142309
This update adds official Kenyan states to the system based on ISO standards. This enhancement enables the upcoming eTIMS OSCU integration for Kenya, which is a tax compliance feature required for version 17.0.
Original PR description
This is a backport, with the original commit occurring in master: e80f5e3. The motivation for backporting these states is that they're useful in the upcoming eTIMS OSCU integration for Kenya, which targets version 17.0. Added Kenyan states as per https://www.iso.org/obp/ui/#iso:code:3166:KE Task ID: 3665315