Friday, January 19, 2024
11 changes · master
Enhancements to existing features
Spreadsheet edition templates were updated to match the newer way Odoo applies template inheritance in the browser. This keeps spreadsheet chart menu behavior compatible with the platform change and avoids future template loading issues.
Original PR description
The PR https://github.com/odoo/odoo/pull/145602 brings several changes in the way inheritance of static templates is applied. One of which is that for a template which inherits from a template with t-name=template_name, the value of t-inherit should be exactly template_name. This means we no longer accept implicit references to modules names (in any ways). Here we adapt the code of spreadsheet_edition to that particular change.
Code cleanup and technical improvements
This update reorganizes how several Odoo apps load messaging-related information by combining multiple server requests into one. It should make startup behavior more consistent and easier to maintain, with little direct change for everyday users.
Original PR description
\* = account_accountant, documents, voip, web_studio,
website_helpdesk_livechat
In particular, init_messaging and failures are now done in a single RPC.
Time control tests have to be adapted to take into account the extra delay that is introduced before fetching data.
Discuss action is made to render even if messaging is not initialized in order to resolve the action promise, to know when to advance time.
The new async step helper is used to guarantee proper order between RPC.
Part of task-3605717
https://github.com/odoo/odoo/pull/149860Miscellaneous changes
Activate 'Budget Management' In Accounting>Configuration>Management>Budgetary Positions Create a new Budgetary Position Add some accounts Save Remove an account Save ValidationError: The budget must have at least one account This occurs because there was a change in the write commands sent Up to saas-16.4 we used to receive `{'account_ids': [[Command.set, False, ids]]}` We now have something like `{'account_ids': [[Command.unlink, id]]}` and the old way of checking the updated `a
Original PR description
Activate 'Budget Management'
In Accounting>Configuration>Management>Budgetary Positions
Create a new Budgetary Position
Add some accounts
Save
Remove an account
Save
ValidationError: The budget must have at least one account
This occurs because there was a change in the write commands sent Up to saas-16.4 we used to receive
`{'account_ids': [[Command.set, False, ids]]}`
We now have something like
`{'account_ids': [[Command.unlink, id]]}`
and the old way of checking the updated `account_ids` no longer works
opw-3633650
Forward-Port-Of: odoo/enterprise#54323Before this commit, the report Finished Product PDF (mrp.label_production_view_pdf) was editable. Though this report really doesn't play well in the report editor as the xml contains a lot of code and the model on this report is wrong, meaning that "docs" does not refer to the actual data that report contain eventually. After this commit, this report cannot be edited via studio as it is too specific. opw-3650049 Forward-Port-Of: odoo/enterprise#54487
Original PR description
Before this commit, the report Finished Product PDF (mrp.label_production_view_pdf) was editable. Though this report really doesn't play well in the report editor as the xml contains a lot of code and the model on this report is wrong, meaning that "docs" does not refer to the actual data that report contain eventually. After this commit, this report cannot be edited via studio as it is too specific. opw-3650049 Forward-Port-Of: odoo/enterprise#54487
This commit aims at adding the status indicator buttons that are present in most other Odoo Form views to Knowledge. These indicators enables the user to know when changes has been taken into account and can be saved inside the DB, either using the buttons or using other methods. This also enables the user to discard any changes he'd done to the article quickly. task-3609594 COM PR: odoo/odoo#145928 Forward-Port-Of: odoo/enterprise#54396 Forward-Port-Of: odoo/enterprise#51579
Original PR description
This commit aims at adding the status indicator buttons that are present in most other Odoo Form views to Knowledge. These indicators enables the user to know when changes has been taken into account and can be saved inside the DB, either using the buttons or using other methods. This also enables the user to discard any changes he'd done to the article quickly. task-3609594 COM PR: odoo/odoo#145928 Forward-Port-Of: odoo/enterprise#54396 Forward-Port-Of: odoo/enterprise#51579
Steps to reproduce: - Install the planning app and Studio. - Go to the planning app and trigger studio to edit. - Change the `Day Precision` to `Quarter Hour`. - Close and now click on `Week` and change the view to `Day`. The issue is that since the gantt is generated based on the screen size of the user in order to fit the whole gant in that width, when we divide the cell in 4 or even 2, the totals are going to overlap in smaller screens since there's no space for that division to disp
Original PR description
Steps to reproduce: - Install the planning app and Studio. - Go to the planning app and trigger studio to edit. - Change the `Day Precision` to `Quarter Hour`. - Close and now click on `Week` and…
Steps to reproduce: - Install the planning app and Studio. - Go to the planning app and trigger studio to edit. - Change the `Day Precision` to `Quarter Hour`. - Close and now click on `Week` and change the view to `Day`. The issue is that since the gantt is generated based on the screen size of the user in order to fit the whole gant in that width, when we divide the cell in 4 or even 2, the totals are going to overlap in smaller screens since there's no space for that division to display the totals horizontally. But in the other hand If we display the totals vertically and make them have a responsive fontsize, it will be visible for pretty much every screen size. Before:  After:  Note: It will also change for when we don't need to divide the cells, but I'm not sure of an easier solution to this. opw-3538039 Forward-Port-Of: odoo/enterprise#50763
Turns out we don't want to pollute Runbot instances with these demo data Forward-Port-Of: odoo/enterprise#54615 Forward-Port-Of: odoo/enterprise#54555
Original PR description
Turns out we don't want to pollute Runbot instances with these demo data Forward-Port-Of: odoo/enterprise#54615 Forward-Port-Of: odoo/enterprise#54555
This commit moves the embedded actions `Open` and `Rename` to the cog menu of the embedded views so that it doesn't interfer with either the top of the article or, in later versions, with comments. task-3635780 This commit is a FW of c3e83668bf9953aea361fb6e3e461bb65c83316c Forward-Port-Of: odoo/enterprise#54598
Original PR description
This commit moves the embedded actions `Open` and `Rename` to the cog menu of the embedded views so that it doesn't interfer with either the top of the article or, in later versions, with comments. task-3635780 This commit is a FW of c3e83668bf9953aea361fb6e3e461bb65c83316c Forward-Port-Of: odoo/enterprise#54598
- Create an invoice with account 151000 - Create an asset with this account as Depreciation Account - Sell this asset with the invoice => You have a weird error talking about remaining value In case of disposal with same accounts, the computation of depreciation_value is wrong. We should instead take the right line to compute it. Forward-Port-Of: odoo/enterprise#54430
Original PR description
- Create an invoice with account 151000 - Create an asset with this account as Depreciation Account - Sell this asset with the invoice => You have a weird error talking about remaining value In case of disposal with same accounts, the computation of depreciation_value is wrong. We should instead take the right line to compute it. Forward-Port-Of: odoo/enterprise#54430
**Before this PR:** The "Delete" button was visible in all instances of the document form view, including documents, projects, etc even while creating a new record. This was not logical since the "Delete" button is only useful when editing a workspace, not while creating a new record. **Technical:** We have added an `attrs` having invisible with the condition `('id', '=', 'False')` to the delete button, so It won't be visible if the record is not created. **After this PR:** The Delete
Original PR description
**Before this PR:**
The "Delete" button was visible in all instances of the document form view, including documents, projects, etc even while creating a new record. This was not logical since the "Delete" button is only useful when editing a workspace, not while creating a new record.
**Technical:**
We have added an `attrs` having invisible with the condition `('id', '=', 'False')` to the delete button, so It won't be visible if the record is not created.
**After this PR:**
The Delete button will only be visible in the Documents app when editing a workspace.
**Task**-3607426
Forward-Port-Of: odoo/enterprise#54071
Forward-Port-Of: odoo/enterprise#51636### Before this PR: User was allowed to do the following operations: - User was able to change month/quarter/year once the GSTR was filed/received - User was able to delete GSTR Period after sending/receiving data ### After this PR: - We restrict the user from doing the above operations as it could be problematic task-3672403 Forward-Port-Of: odoo/enterprise#54103
Original PR description
### Before this PR: User was allowed to do the following operations: - User was able to change month/quarter/year once the GSTR was filed/received - User was able to delete GSTR Period after sending/receiving data ### After this PR: - We restrict the user from doing the above operations as it could be problematic task-3672403 Forward-Port-Of: odoo/enterprise#54103