Friday, August 26, 2022
9 changes · master
Enhancements to existing features
The appraisal module’s confirmation checkbox has been updated to use Odoo’s newer interface technology. This keeps the appraisal experience consistent with the modern platform and helps maintain reliability for future updates.
Original PR description
Convert the boolean confirm field widget to Owl. task-2928190
The predictive billing feature now avoids suggesting account types that do not fit the new bill being entered. This prevents old or incorrect database entries from causing confusing suggestions on future bills.
Original PR description
Sometimes there are existing errors in the database, but we don't want it to make noise for future entries.
Resolved issues and error corrections
The Helpdesk timesheet timer has been repositioned so it appears correctly in the ticket view. This restores the expected layout after a recent interface structure change and helps users track time without visual confusion.
Original PR description
This commit fixes the position of the timer in the helpdesk module. The timer is no longer correctly placed since the introduction of a div wrapper around legacy fields. This commit simply realign the timer correctly. Before: <img width="287" alt="image" src="https://user-images.githubusercontent.com/35101914/186584520-4347d6a1-5f5d-4601-a9d8-72b6d8307fc5.png"> After: <img width="272" alt="image" src="https://user-images.githubusercontent.com/35101914/186584450-979bdd28-9072-40b9-991a-38ba4bbb8092.png">
Code cleanup and technical improvements
This update simplifies styling for enterprise form views as part of a broader visual cleanup. It improves consistency in editable note fields and helps keep the interface easier to maintain, with minimal direct impact on day-to-day users.
Original PR description
Part of the overall v16 SCSS optimization/restyle, task-2704984 Requires: - https://github.com/odoo/odoo/pull/98101 task-2918464
Miscellaneous changes
For Bill/2022/08/002 (id:liaison_bill_1), the due date wasn't visible either from the bills list view or the journal items due date. This was due to a wrong field name. Used the task as an opportunity to remove useless lines. task-2930512 Forward-Port-Of: odoo/enterprise#30258
Original PR description
For Bill/2022/08/002 (id:liaison_bill_1), the due date wasn't visible either from the bills list view or the journal items due date. This was due to a wrong field name. Used the task as an opportunity to remove useless lines. task-2930512 Forward-Port-Of: odoo/enterprise#30258
The PLM notification button has been modernized without changing its intended business function. This helps keep the manufacturing product lifecycle interface maintainable and aligned with the current platform framework.
Original PR description
Updates the plm_toaster_button widget into OWL. Task-2885757
onlinesync.odoo.com domain name was never meant to be used for localisation. Replace it with a correct domain name. Forward-Port-Of: odoo/enterprise#30731 Forward-Port-Of: odoo/enterprise#30720
Original PR description
onlinesync.odoo.com domain name was never meant to be used for localisation. Replace it with a correct domain name. Forward-Port-Of: odoo/enterprise#30731 Forward-Port-Of: odoo/enterprise#30720
The issue: When validating the invoice, the Sunat checks that the `PriceAmount` of the xml is equal to the division of `InvoicedQuantity / LineExtensionAmount` This verification sometimes fails for invoices with unit price of more than 2 decimal places, because we are forcing to use 2 decimal places For example, take the following situation: - Decimal Accuracy for Product Price is 4 - Create a invoice with Quantity = 2000, Price = 0.0575, Taxes = 18% - The PriceAmount in the Xml is 0.0
Original PR description
The issue: When validating the invoice, the Sunat checks that the `PriceAmount` of the xml is equal to the division of `InvoicedQuantity / LineExtensionAmount` This verification sometimes fails for invoices with unit price of more than 2 decimal places, because we are forcing to use 2 decimal places For example, take the following situation: - Decimal Accuracy for Product Price is 4 - Create a invoice with Quantity = 2000, Price = 0.0575, Taxes = 18% - The PriceAmount in the Xml is 0.06, but it should be 0.0575 - When we multiply 0.06 * 2000 = 120 and 0.0575 * 2000 = 115. The difference is 5, so the check fails. The solution: - Round the unit_amount to the decimal accuracy of Product Price Latam Ticket: https://latam-localizations.odoo.com/web#id=864&cids=1&model=project.task&view_type=form Forward-Port-Of: odoo/enterprise#30454 Forward-Port-Of: odoo/enterprise#30194
Compute book value and value_residual on negative asset Steps: - Create an asset model AM - On AM.account_depreciation_id, set create_asset to 'draft' and asset_model to AM - Create a Vendor bill credit note CN, with invoice_date today - 1 month With invoice_line_ids: "account_id": AM.account_depreciation_id, "price_unit": 500 - Confirm CN, go to related asset newly created and validate it - book_value and value_residual should be 500 - Post the first asset's depreciation m
Original PR description
Compute book value and value_residual on negative asset
Steps:
- Create an asset model AM
- On AM.account_depreciation_id, set create_asset to 'draft'
and asset_model to AM
- Create a Vendor bill credit note CN, with invoice_date today - 1 month
With invoice_line_ids:
"account_id": AM.account_depreciation_id, "price_unit": 500
- Confirm CN, go to related asset newly created and validate it
- book_value and value_residual should be 500
- Post the first asset's depreciation move
-> book_value and value_residual are still 500, they should be 400
Compute the field debit/credit in _get_depreciation() regarding the
type of the original move.
opw-2848330
opw-2882049
Forward-Port-Of: odoo/enterprise#30707
Forward-Port-Of: odoo/enterprise#28373