Tuesday, August 16, 2022
9 changes · master
Enhancements to existing features
The SLA Policy option on product forms has been moved from General Information to the Sales tab. This makes the setting easier for users to find in the area where sales-related product configuration is managed.
Original PR description
… tab This commit just changes the location of the SLA Policy selection in the product form. Previously the SLA Policy selection was under the "General Information" tab but now the selection has been moved under the "Sales" tab. The imporvements in this commit aim at making the placement of the SLA policy setting more intuitive for the users. That, should increase productivity as it will be easier for the user to find the setting if their are looking for it. To implement this change, the product_views.xml file was modified and the new location for the setting was given. Task No: 2919785
Resolved issues and error corrections
Fixed an issue where right-clicking a spreadsheet cell without a pivot formula could cause an error. This improves spreadsheet reliability and prevents interruptions when users open cell context menus.
Original PR description
… crash Since a8eb01024fe6500922c0bb3e89d2fc831f5b2d77, trying to open the context menu of a cell which does not contains at least one pivot formula leads to a traceback. Task-id 2954345
Miscellaneous changes
How to reproduce: - Create a product and set some qty in a package; - For the internal transfer, enable "Move entire packages"; - Create a new internal transfer for the package containing the created product and confirm it; - Open the internal transfer in the Barcode App; - Scan the package -> Its qty. done is updated (0/1 -> 1/1); - Scan it a seconde time -> Its quantity is updated again (1/1 -> 2/1) which is an error (the transfer can't be valided from here). opw-2946401 Forward-
Original PR description
How to reproduce: - Create a product and set some qty in a package; - For the internal transfer, enable "Move entire packages"; - Create a new internal transfer for the package containing the created product and confirm it; - Open the internal transfer in the Barcode App; - Scan the package -> Its qty. done is updated (0/1 -> 1/1); - Scan it a seconde time -> Its quantity is updated again (1/1 -> 2/1) which is an error (the transfer can't be valided from here). opw-2946401 Forward-Port-Of: odoo/enterprise#30289 Forward-Port-Of: odoo/enterprise#30187
This update fixes a rare issue where automated checks for spreadsheet links could fail unpredictably. It improves confidence in the Documents Spreadsheet module's test results without changing how users work with spreadsheets.
Original PR description
…sheet Tests using `insertInSpreadsheetAndClickLink()` could (rarely) fail. Replace `await nextTick()` by `await nextRender()` to fix the issue. Odoo task [2946665](https://www.odoo.com/web#id=2946665&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form)
This update removes outdated form layout styling from parts of Odoo Enterprise so the interface remains compatible with the newer Bootstrap framework. Users should see no functional change, but these cleanup fixes help prevent visual issues in affected screens and keep the product easier to maintain.
As of now, the address validation button on res partner added by account_avatax is always showing in the form view, even when the setting is disabled. This leads to a button that only display an error unless the setting is enabled. Change this by hiding the button from the view if the setting is not enabled on the company of the partner (or the current company if it does not have one) Task id # 2858113 Forward-Port-Of: odoo/enterprise#29085
Original PR description
As of now, the address validation button on res partner added by account_avatax is always showing in the form view, even when the setting is disabled. This leads to a button that only display an error unless the setting is enabled. Change this by hiding the button from the view if the setting is not enabled on the company of the partner (or the current company if it does not have one) Task id # 2858113 Forward-Port-Of: odoo/enterprise#29085
Forward-Port-Of: odoo/enterprise#30319
Original PR description
Forward-Port-Of: odoo/enterprise#30319
Previous to the commit: If the journal is in manual mode, it unnecessarily validate the existence of CAF files. After the commit The commit skips the requirement of CAF in edi post validation method when the journal is not in online mode. Forward-Port-Of: odoo/enterprise#30325 Forward-Port-Of: odoo/enterprise#27165
Original PR description
Previous to the commit: If the journal is in manual mode, it unnecessarily validate the existence of CAF files. After the commit The commit skips the requirement of CAF in edi post validation method when the journal is not in online mode. Forward-Port-Of: odoo/enterprise#30325 Forward-Port-Of: odoo/enterprise#27165
This PR will make sure that the administrators will always be able to moderate the articles without having explicit "write" access on an article. Currently, the administrator will get access errors when doing the following actions: - When an article inherits its members from its parent and the user does not have "read" access on the parent article, the user gets an access error when opening the share panel of the child article. - When the administrator does not have 'write' access on an arti
Original PR description
This PR will make sure that the administrators will always be able to moderate the articles without having explicit "write" access on an article. Currently, the administrator will get access errors when doing the following actions: - When an article inherits its members from its parent and the user does not have "read" access on the parent article, the user gets an access error when opening the share panel of the child article. - When the administrator does not have 'write' access on an article, the administrator will get an access error when clicking on the 'invite' button (in the invitation wizard) of the share panel. - When the administrator does not have 'write' access on an article, the administrator will get an access error by trying to (1) restore the internal permission of an article, (2) set the internal permission of an article, (3) set the permission of a member, (4) add/remove a member from an article. task-2893614 Forward-Port-Of: odoo/enterprise#29447