Thursday, November 7, 2024
6 changes · master
Resolved issues and error corrections
This fixes an issue in Odoo Studio exports where built-in system fields could be handled incorrectly. Exports should now use the proper field names, making exported data more reliable for users.
Original PR description
Use the name instead of the field instance.
Belgian payroll now shows the eco voucher action only for the relevant holiday termination payslip batches. When used, the wizard creates or updates the correct monthly payslip structure so eco vouchers are included accurately without disrupting payslip presentation.
Original PR description
Problem ---------- - The eco voucher button should be only displayed when a holiday termination payslip is in the batch. (N or/and N-1) - When payslips are generated with the eco-voucher wizard, all…
Problem ---------- - The eco voucher button should be only displayed when a holiday termination payslip is in the batch. (N or/and N-1) - When payslips are generated with the eco-voucher wizard, all payslips have the wrong structure : CP200HOLN. The eco voucher button should generate or regenerate a monthly payslip with the eco voucher inside. Objective ---------- - Display the button for the good structures. - Change the filtered employee in the eco-voucher wizard to match the structs - Use the good struct for payslips generated from eco-voucher wizard : CP200MONTHLY - Add new rule in the structure to display a line in the payslip if an eco-voucher is add as "other fields". (But hide it in the payslip) Solution ---------- - Condition on structure code changed from CP200HOLN and CP200HOLN1 for the visibility of the eco voucher button. - Employees filter changed for the eco-voucher action - Payslip structure changed for payslips generated from the eco-voucher wizard. - New record added in the CP200MONTHLY structure. Test ---------- Python test added to test if an eco-vouchers line is added to payslips in the batch when the user validate the payslip generation from the eco-vouchers wizard. 3 cases are covered : - generated payslips - existing payslips - edited existing payslips (edited with the edit payslip wizard in cogmenu) task-3598939
This fix improves the wording of an error shown when users scan a barcode that is not found during receipt operations. It makes the message clearer and more professional, reducing confusion for warehouse staff.
Original PR description
Barcode --> Operations --> Receipts --> NEW Scan a barcode that doesn't exist in the DB ie: "5449000000996" The current error message's spelling and grammar are off. opw-4307102
Installing the Payroll Accounting module on a new database will now also install the required Accounting app. This prevents setup gaps and ensures payroll accounting features work as expected from the start.
Original PR description
When installing hr_payroll_account on an empty DB, we expect the Accounting app to be installed. But that is not the case. hr_payroll_account should depend on the accountant app.
The commission plan form now uses the standard date range selector, making start and end date selection work better on mobile devices. This reduces friction for users managing commission plans from phones or tablets.
Original PR description
before this commit, commission plan form date field selector seems broken in mobiles devices because we did not directly used widget available. after this commit, use daterange widget.
The sale commission plan list view no longer shows the status field twice. This removes duplicate information from the screen, making the list cleaner and easier for users to read.
Original PR description
in this PR, fixed an issue where the status of the sale commission plan was being displayed twice. This fix ensures that the status information is shown only once.