Monday, January 30, 2023
5 changes · master
New functionality added to Odoo
Vendor bills imported from documents can now be automatically linked to the related purchase order when the system finds a matching supplier, reference, and amount. This reduces manual work for accountants and helps keep bill lines aligned with purchase order records, even when document imports lose that connection.
Original PR description
When a vendor bill document is uploaded (EDI, PDF,..) the link with the purchase order is often lost. We want to reuse the purchase.order OCR' matching logic to enhance vendor bill extracted from documents. To sum up the logic; - if we find a partner or reference match (invoice_origin) AND the same amount, we use autocomplete and replace the line in the vendor bill with the purchase order one. - if we find a match with the reference and some line in the purchase order sum up to the vendor bill total, we add those line in the vendor bill but we set the qty to zero (the accountant can manually remove the XML line and link the new one afterwards). task-id: 2828521 [community](https://github.com/odoo/odoo/pull/109093) [enterprise](https://github.com/odoo/enterprise/pull/35436)
Enhancements to existing features
The subscription list view now shows key details like order number, order date, recurrence, and related subscription context. This makes it easier for users to identify the right sales orders and take bulk actions with confidence.
Original PR description
Before this commit, when a user wanted to act on multiple SOs (through the action menu) in the subscription app, it wasn't intuitive to find those records in the list view because the 'order number' field wasn't being shown. Also, key information that gives subscription context such as 'order date', 'recurrence', etc weren't being shown either.
This commit adds new fields to the list view and change to 'optional' some previous inserted fields ('Customer Reference', 'To Renew').
Task id: 3128511Resolved issues and error corrections
Website navigation now more reliably identifies the current page, including dropdown menu items and links written as full URLs. This improves visitor orientation by highlighting the right menu item while correctly handling query options and ignoring page anchors that cannot be checked by the server.
Original PR description
- `clean_url` method was wrongly flag as `api.model` - the `unslug_url` was not called for the URL comparison in the dropdown case, meaning that `/shop/prod-1` would not match `/shop/product-1` as it should (and as it does for regular non dropdown menu) - the `active` class was actually never working for the dropdown case, as the class was added on the wrong element (`li` instead of `a`) The code was hard to read (mainly because huge python conditions in XML) and kinda redundant, going through an util method should be clearer and help reading the template XML. - Ignore anchors, those are not sent to the server anyway, no way to compare even if we wanted to - Ensure query string (qs) are the same to be considered equals On top of that, it also fixes the case when the user inserted an absolute URL instead of a relative one, it will now match. task-3096367 opw-3091427
Payroll administrators can now turn payslip PDF previews on or off in the payslip form. This gives companies more control over the payroll screen experience and can reduce unnecessary on-screen document previews when they are not useful.
Original PR description
Add a new setting to enable / disable the preview of PDF payslip in the form view. task-3143632
Vendor bills created from OCR or document imports can now benefit from the same purchase order matching logic already used elsewhere. This makes automated bill processing more consistent and reduces duplicated logic across modules.
Original PR description
We want to reuse the purchase.order matching logic to enhance vendor bill created for the OCR in documents (EDI, PDF,..). This code has been move to the purchase module. task-id: 2828521 [community-pr](https://github.com/odoo/odoo/pull/109093)