Wednesday, June 29, 2022
9 changes · master
Enhancements to existing features
Payroll screens and workflows have been refined to make everyday payroll management easier and clearer for users. The update also standardizes payroll accounting setup by requiring a journal on payroll structures, helping reduce setup mistakes.
Original PR description
This commit aims to improve the usability of payroll with various modifications on views and behaviors. taskID 2783013
This update simplifies internal automated tests for the enterprise mail features by removing an older test helper. It does not change how users experience the product, but it helps keep the test suite easier to maintain and aligned with the community codebase.
Original PR description
task-2871066 community: https://github.com/odoo/odoo/pull/94691
VoIP phone system configuration is now handled directly within the VoIP area instead of a separate setup component. This simplifies maintenance and helps ensure users receive the right calling configuration when messaging starts.
Original PR description
Model and move the PBX configuration to the Voip model. Part of task-2804807. Community: https://github.com/odoo/odoo/pull/94569 Upgrade: https://github.com/odoo/upgrade/pull/3625
Resolved issues and error corrections
When the Documents app is installed, the related spreadsheet features will now be installed automatically as well. This prevents users from missing expected spreadsheet functionality and reduces manual setup steps.
Original PR description
Auto install `documents_spreadsheet` as soon as `documents` is installed.
Features or functions removed from Odoo
The attachment preview no longer offers a manual resize option. This removes reliance on an outdated component with minimal business impact, helping keep the system easier to maintain.
Original PR description
* = account_accountant The resize of the attachment viewer still uses jquery ui, which we need to remove. Considering the low impact of this feature, we decided to remove it. task-2897273
Miscellaneous changes
## Goal: The aim of this commit is to take into account the legacy data of Odoo in order to have correct results reported. ## Context: Odoo set a partner_id on the account.move.line. Currently, the partner is always the commercial_partner_id A.K.A. the "ultimate parent partner". In the past, that hasn't always been the case and it was possible that Odoo sets the partner directly. ## Previous to this commit: 281.50 feature only take care of the parent and doesn't consider the accoun
Original PR description
## Goal: The aim of this commit is to take into account the legacy data of Odoo in order to have correct results reported. ## Context: Odoo set a partner_id on the account.move.line. Currently, the partner is always the commercial_partner_id A.K.A. the "ultimate parent partner". In the past, that hasn't always been the case and it was possible that Odoo sets the partner directly. ## Previous to this commit: 281.50 feature only take care of the parent and doesn't consider the account move line on which the children has been set and thus doesn't even report those amount. There isn't any form 281.50 created for the child and the amounts relative to this child are "lost". ## After this commit: 281.50 feature takes those account.move.line into account. All the amounts are gathered on the parent partner. PR: task-id: 2871601 Forward-Port-Of: odoo/enterprise#28948 Forward-Port-Of: odoo/enterprise#28065
Contract addendums now use the salary and benefit details linked to an employee's new job position when their function changes. This prevents outdated contract information from carrying over and makes payroll contract templates easier to use.
Original PR description
When an addendum to an existing contract is made with a changes of function, the addendum will take details from the new function (through the default contract of the new job position). Previously, the details didn't change and were based on the current contract details. taskID 2783059 [Payroll] Addendum to contract doesn't take good values
Forward-Port-Of: odoo/enterprise#28862
Original PR description
Forward-Port-Of: odoo/enterprise#28862
When importing a CAMT file, we are filtering statements using the journal currency. However, if a wrong currency is set on the journal, no statements are imported and an unclear error message is raised in _check_parsed_data. We should adapt so the account number is displayed correctly in that generic error message instead of False, and we should also add a new specific message so the user knows he has to check the journal currency in order to possibly fix his issue. opw-2845404 Forward
Original PR description
When importing a CAMT file, we are filtering statements using the journal currency. However, if a wrong currency is set on the journal, no statements are imported and an unclear error message is raised in _check_parsed_data. We should adapt so the account number is displayed correctly in that generic error message instead of False, and we should also add a new specific message so the user knows he has to check the journal currency in order to possibly fix his issue. opw-2845404 Forward-Port-Of: odoo/enterprise#28921 Forward-Port-Of: odoo/enterprise#27917