Thursday, May 30, 2024
8 changes · master
New functionality added to Odoo
This update makes it easier to create products from barcode lookup data in Point of Sale and stock barcode workflows. It enriches new products with more available details such as images, dimensions, volume, and attributes, while limiting creation to administrators and adding API key authentication checks.
Original PR description
*: product_barcodelookup, stock_barcode_barcodelookup pos_product_barcodelookup: - Added a barcode_scanner widget inside create product form view. stock_barcode_barcodelookup: - Added a create product button inside toaster. product_barcodelookup: - Set multi-images if available. - Set volume (based on the 3 dimensions). - When creating the product based on the barcode, created all attribute values for which the attribute is defined. - Removed module stock_barcode_account_barcodelookup. - For attributes of type color, only created if color is valid - Added a functionality to check authentication of the api key. Only user with administration rights can create the product both in pos_product_barcodelookup and stock_barcode_barcodelookup. task: 3911024 Related: https://github.com/odoo/odoo/pull/166796 Upgrade: https://github.com/odoo/upgrade/pull/6087
Enhancements to existing features
Barcode users now hear a confirmation sound when a scan is successful, in addition to the existing screen flash. This makes it easier for warehouse and manufacturing staff to confirm scans immediately, especially in fast-paced environments.
Original PR description
Before this PR =============== When a barcode was scanned successfully, the screen flashed to indicate the successful scan, but there was no sound. This lack of auditory feedback could sometimes make it difficult for users to be sure the scan was successful. After this PR =============== Along with the flashing screen, a sound now plays when a barcode scan is successful. This provides clear and immediate feedback to users, ensuring they are aware that the scan was successful. TaskId: 3685476
When VAT units are created or updated, matching horizontal groups are now created automatically. These groups are enabled on relevant tax reports, making VAT-unit reporting more consistent while removing a debug-only menu entry that business users did not need.
Original PR description
This Pr will do multiple things: - Remove the Horizontal Groups menu items from the debug mode. - Create the horizontal group that corresponds to each VAT UNIT each time a VAT Unit is created/modified. - Activate the horizontal groups on the generic Tax Report, the EC Sales List, and the Tax reports whose company belongs to the country of the VAT Unit. task: 3918305
Shift templates can now define editable start and end hours plus a duration in days, making planned schedules more flexible. When templates are assigned, Odoo uses the resource or company calendar to calculate working dates and allocated hours more accurately.
Original PR description
This commit updates the method for calculating planned dates using shift template values. It introduces the ability to modify the start and end hours, as well as the duration in days, for which a shift template is scheduled. The allocated hours is then determined using either the user's or the company's calendar. When assigning a shift template to a resource, the planned dates are calculated according to the resource's calendar. The start and end hours from the template are retained, along with the original start date. The end date is generated based on the duration in days specified in the template. The planned dates are arranged over a timeframe that ensures the total working days match the specified days duration. taskid:3624669
Australian payroll now has more detailed payroll input and attachment categories, including clearer treatment for payment type, superannuation, and PAYG withholding. This helps payroll calculations and reporting align more consistently with Australian payroll requirements.
Original PR description
This commit revamps the input types and attachments for the l10n_au_hr_payroll module. The input types have selection fields for payment type, superanuation and paygw treatment. There are new input types added. Salary Rules have been updated to use the new input type fields. Task# 3769675
The MPS creation wizard no longer automatically picks the first bill of materials when a product is selected. This helps prevent large numbers of component records from being added unintentionally, giving users more control over planning setup.
Original PR description
The creation wizard computes the bom from the selected product by selecting the first bom available. The issue is that the MPS will add the components of the bom to the records. If a bom has 100+ components, that's a lot of records. We want the user to make that a conscious decision instead of an automated behavior.
Customers are now alerted when they already have an upcoming appointment before booking another one. This helps prevent accidental duplicate bookings while still allowing users to view the existing appointment or continue with a new booking if needed.
Original PR description
Add an "extra" step to tell the user that he already had an upcoming appointment. The idea is to be sure that the user knows that he already booked an appointment before booking another one. The upcoming appointment info is based on the info stored in the localStorage when an appointment is taken and landing on the validation page and the sale confirmation if website_appointment_sale is installed. In case it's not the public user, we don't use the list of access_token from the local storage and just check the appointments based on the appointment_booker_id. There are 2 buttons, the first one allows to reach the upcoming appointment details and the other to display the calendar to book another appointment. Clicking on the button "Add another" add a value in the local storage to ignore and don't show the upcoming block info for a day. We also add the upcoming events info of the appointment booker in the mail template. task-3773579
Australian payroll now calculates tax withholding on unused leave at termination using the employee's normal scheduled gross earnings, instead of a potentially reduced final payslip amount. This helps produce more accurate termination payments, especially when employment ends partway through a pay period, and allows manual adjustment of the gross unused leave amount when needed.
Original PR description
The amount withheld from the unused leaves payment at the time of termination depends on the normal gross earnings of an employee during their schedule pay period. This commit implements withholding variations for unused leaves. Also adds the option to assign the gross unused leaves manually. Issue: The salary rules use the gross salary computed on a regular payslip. This raises the issues when the employee is terminated in the middle of a pay period and the gross salary for the payslip changes. task# 3821959