Monday, October 10, 2022
8 changes · master
Enhancements to existing features
Invoices now show bank statement information when a manually registered payment has been reconciled through a posted bank statement. This helps users open the right bank reconciliation view directly instead of being sent to the payment record, making follow-up and review clearer.
Original PR description
When a payment is registered manually and reconciled with a bank statement, the payment widget on the invoice still displays payment data. Clicking the "View" button also redirects to the `account.payment` form. Once a bank statement is posted, it is preferred to show the bank statement information and redirect to a bank reconciliation widget view, filtered by the bank statement line reconciled with the payment. In a very unlikely case that a payment is reconciled with more than one bank statement line, we display the last statement's data and filter the reconciliation widget by the last statement line posted. task-2928299 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Companies can now be archived when they are no longer in use, such as after closing a subsidiary, without needing to delete historical business records. This keeps past invoices, payments, and related data intact while removing inactive companies from everyday use.
Original PR description
It is technically nearly impossible to delete a company when it actually dealed with customers (emitted invoices, received payments, ...). Hence, if you want to get rid of a company, for instance because you closed one of your subsidiaries, giving the possibility to archive your company, thanks to an active field, would be the best way to go. We are hesitating to do a related field to the `partner_id.active`, but we are a bit afraid some people archive the partner linked to their company for other valid reasons than get rid of their subsidiary (such as avoid changing the address of their company by mistake through the Contacts app), while still wanting the company itself to be active. So, we make it an independant column at the moment, so we have the actual stored column in case we need it, and will do a related stored to the partner later on if we change our mind. *edit*: manual forward-port of https://github.com/odoo/odoo/pull/102801
The spreadsheet component was updated to make common actions smoother and more reliable. Users can now adjust filters in read-only mode where allowed, clear cell contents with Backspace, and benefit from an internal safeguard that prevents duplicate data access names.
Original PR description
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/1af8ad34 [IMP] filters: allow to update a filter in readonly mode https://github.com/odoo/o-spreadsheet/commit/706cc8ee [FIX] model: ensure that two getters cannot have the same name https://github.com/odoo/o-spreadsheet/commit/96067749 [IMP] grid: allow to remove content of a cell with backspace
This update streamlines how Odoo's messaging-related modules manage internal links between related records. It helps reduce maintenance complexity and supports more consistent behavior across Discuss, Live Chat, Mail, and Snailmail without introducing a visible workflow change for users.
Original PR description
\* = im_livechat, snailmail task-2741402 https://github.com/odoo/enterprise/pull/27282
This update streamlines how chat channel memberships are retrieved, reducing database work and improving performance. It mainly benefits Discuss and Live Chat behind the scenes, with no expected change to user workflows.
Original PR description
* = im_livechat, test_discuss_full Code cleanup, reduce query count, improve query performance. task-2818809
The mail app no longer allows default values on fields used to identify records, removing unnecessary work during record creation. This simplifies internal handling of sound effects and should slightly improve performance without changing normal user workflows.
Original PR description
There is no strong need to have default values on identifying fields, while allowing it adds overhead to every insert. The trade-off is not worth it, therefore this commit removes the support for identifying field default values and simplifies the code of `findFromIdentifyingData` accordingly. Enterprise: https://github.com/odoo/enterprise/pull/32634
VoIP sound effect records now use a single full-path value instead of separate path and filename fields. This internal cleanup reduces unnecessary default-value handling during data creation, helping keep insert operations simpler and more efficient.
Original PR description
Context: We want to get rid of default values on identifying fields, and `SoundEffect/path` is currently the only field to present this pattern. Merging `path` and `filename` fields together makes the default value no longer meaningful, as there is no full path that is shared by multiple records and which would therefore consist of a relevant default value. The point of removing default values from identifying fields is to simplify the code of `findFromIdentifyingData`, which is called by every single insert, so that we no longer have the overhead of looking for default values. This commit adapts the Enterprise code, and especially the VoIP code, to the changes made to the SoundEffect model. Community: https://github.com/odoo/odoo/pull/102912
This update improves how related messages, notifications, previews, approvals, and signing activities stay connected behind the scenes. It helps keep communication and workflow data more consistent, reducing the risk of missing or incorrectly linked activity information.
Original PR description
\* = approvals, sign task-2741402 https://github.com/odoo/odoo/pull/91229