Daily updates from Odoo
Monday, April 12, 2021
11 changes
Enhancements to existing features
SEPA direct debit payments now consistently use the recurring payment status instead of marking initial payments separately. This aligns payment files with current banking rules and helps avoid unnecessary processing differences for French direct debit transactions.
Original PR description
## The issue: 'FRST' is the code use for the first transaction. Every following transaction should have the code 'RCUR'. Moreover, since 2016, 'FRST' isn't even required anymore. ## The fix: Simply replace 'FRST' by 'RCUR' ### Ticket: \#2490238
Payslip creation now prevents users from selecting a cancelled employee contract, even when the payslip dates would otherwise match it. This helps payroll teams avoid processing pay based on invalid contracts and reduces the risk of payroll mistakes.
Original PR description
Currently, when creating a payslip, if the dates allow it, you can select a cancelled contract to base your payslip on. This shouldn't be the case. Task ID: 2501310
Resolved issues and error corrections
The Belgian POS certification module has been updated to use the current asset declaration approach. This keeps the module aligned with platform changes and helps prevent asset loading issues during upgrades or deployment.
Original PR description
Community: https://github.com/odoo/odoo/pull/68706
Approval activities can no longer be created manually from the scheduling wizard. This avoids users creating approval tasks that cannot be actioned, ensuring approvals are only generated by the intended automated process.
Original PR description
Initially it was possible to create approval activity manually by selecting Approval in Activity Type of Schedule activity. But after archiving Approval option (Inside data/mail_activity_data.xml) there is no way to create approval activity manually through Schedule activity. TaskID: 2439015
Code cleanup and technical improvements
This pull request reorganizes how several accounting-related app resources are registered and loaded. The change supports a broader assets conversion effort, helping keep the system easier to maintain without introducing major visible changes for end users.
Original PR description
Example of full assets conversion.
Miscellaneous changes
'to_check' 1. Reconcile of a bank statement, checking the "To check" box on the manual operation before validation 2. Go to accounting dashboard The statement line will not be counted in the "to check" action. This occur because the action only filter on reconciled moves opw-2475663 Forward-Port-Of: odoo/enterprise#17376
Original PR description
'to_check' 1. Reconcile of a bank statement, checking the "To check" box on the manual operation before validation 2. Go to accounting dashboard The statement line will not be counted in the "to check" action. This occur because the action only filter on reconciled moves opw-2475663 Forward-Port-Of: odoo/enterprise#17376
The last step of `hr_contract_salary_tour_2` test tour navigates to `/web/` but does not wait for the page to be fully loaded. In rare cases, it leads to a race condition and makes the test fails (see build error ID 1386 on runbot). The race condition happens when the ChromeBrowser clear method is called while the `web` page starts to load. Forward-Port-Of: odoo/enterprise#17618
Original PR description
The last step of `hr_contract_salary_tour_2` test tour navigates to `/web/` but does not wait for the page to be fully loaded. In rare cases, it leads to a race condition and makes the test fails (see build error ID 1386 on runbot). The race condition happens when the ChromeBrowser clear method is called while the `web` page starts to load. Forward-Port-Of: odoo/enterprise#17618
PURPOSE Purpose of this merge is to provide various improvements in Online related features overhauled in 14.0. SPECIFICATION Remove the old "wishlist" terminology. Use favorite when possible. Allow to trigger a new push notification request when user favorite tracks, instead of waiting 7 new days before asking again. Remove default date for the track form as it bloats the db and view. See sub commits for more details. LINKS Task-2347597 COM PR odoo/odoo#69102 ENT PR
Original PR description
PURPOSE Purpose of this merge is to provide various improvements in Online related features overhauled in 14.0. SPECIFICATION Remove the old "wishlist" terminology. Use favorite when possible. Allow to trigger a new push notification request when user favorite tracks, instead of waiting 7 new days before asking again. Remove default date for the track form as it bloats the db and view. See sub commits for more details. LINKS Task-2347597 COM PR odoo/odoo#69102 ENT PR #17612 Forward-Port-Of: odoo/enterprise#17612
Since the name field of data_merge.model is required and copy=False, duplicating it gives you an error: """ The operation cannot be completed: - Create/update: a mandatory field is not set. - Delete: another model requires the record being deleted. If possible, archive it instead. """ That is not very friendly since the name is removed on copy. With this changeset, we add ` (copy)` next to the previous name so it is still possible to duplicate. opw-2490990 Forward-Port-Of: odoo/enterprise#1
Original PR description
Since the name field of data_merge.model is required and copy=False, duplicating it gives you an error: """ The operation cannot be completed: - Create/update: a mandatory field is not set. - Delete: another model requires the record being deleted. If possible, archive it instead. """ That is not very friendly since the name is removed on copy. With this changeset, we add ` (copy)` next to the previous name so it is still possible to duplicate. opw-2490990 Forward-Port-Of: odoo/enterprise#17604
When creating a payslip, after having a valid input, changing the employee will render the payslip unusable, this change aims to fix this issue. Some fields related to the employee also weren't removed properly when necessary. Impacted versions: - 14.3 Steps to reproduce: 1. create a new payslip 2. select an employee with a valid contract for this payslip 3. select any other employee Forward-Port-Of: odoo/enterprise#17579
Original PR description
When creating a payslip, after having a valid input, changing the employee will render the payslip unusable, this change aims to fix this issue. Some fields related to the employee also weren't removed properly when necessary. Impacted versions: - 14.3 Steps to reproduce: 1. create a new payslip 2. select an employee with a valid contract for this payslip 3. select any other employee Forward-Port-Of: odoo/enterprise#17579
…tests Forward-Port-Of: odoo/enterprise#17567 Forward-Port-Of: odoo/enterprise#17558
Original PR description
…tests Forward-Port-Of: odoo/enterprise#17567 Forward-Port-Of: odoo/enterprise#17558