Tuesday, November 13, 2018
7 changes · master
Enhancements to existing features
Payslip lines with the same sequence are now displayed in a predictable order by using their code as a secondary sort value. This removes confusing random-looking line order changes and makes payroll reviews easier to follow.
Original PR description
Improve payslip line sorting from some how random in same sequence to be exact Description of the issue/feature this PR addresses: Current behavior before PR: Random sorting in same sequence Desired behavior after PR is merged: Payslip line sorting from some how random in same sequence to be exact. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Employee leave requests now automatically recalculate the number of days when they are created or edited. This helps keep leave balances and request details accurate without requiring manual updates.
Original PR description
Currently if we want to have the number of days up to date at creation or at write, we need to pass it explicitly. To allow the number_of_days to be updated, we manually trigger the onchange in the create and in the write methods Related to task 1908575 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The HR contract type form now uses a standard sheet layout, making it display more consistently with other Odoo forms. The change also removes unnecessary layout settings that did not affect the form's appearance, keeping the view simpler to maintain.
Original PR description
Description of the issue/feature this PR addresses: Not perfectly created view with not used element settings Current behavior before PR: The contract type form view has no `<sheet>` set. Desired behavior after PR is merged: The contract type form view has a `<sheet>` set and doesn't have the `col` elements set as the view renders identically without them. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Event invitation emails now use a standard calendar file link instead of an Outlook-specific link. This makes it easier for recipients to add events to their preferred calendar application, improving compatibility and reducing friction.
Original PR description
Task : https://www.odoo.com/web#id=1853063&action=327&model=project.task&view_type=form&menu_id=4720 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resource calendars can now be marked as full time or part time. This helps businesses apply employee leave rules correctly when eligibility depends on working schedule status, such as certain parental leave policies.
Original PR description
Purpose
=======
Add a checkbox on a resource calendar to know if the resource calendar is full time or part time.
This is useful because some rules for leaves can be different for full time and part time employees
(e.g. parental leaves in Belgium cannot be part time if the employee is not full time).
Specification
=============
Add a Boolean field 'full_time' on 'resource.calendar'
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prResolved issues and error corrections
Server-side forms now prepare nested one-to-many editing areas consistently, preventing errors when automated field updates involve records inside records. This improves reliability for complex business forms without changing normal user workflows.
Original PR description
Currently the SSF only sets up an edition view on top-level o2ms. This can apparently be an issue in some cases involving onchanges on o2ms which contain o2m, as _cleanup_onchange tries to get the sub-o2m's fields (`subfields`) before processing any command, and this blows up as there is no `"edition"` key in the views dict. Recursively set up edition views as part of the fvg preprocessing to fix the issue. Also avoid recursing into fields as processing a sub-field as a field seems problematic (incorrect views, …).
The Debian installation package now requires two small supporting libraries that were previously only suggested. This helps Odoo modules that depend on QR codes or vCard/contact data work out of the box in official Docker images, without extra container customization.
Original PR description
As stated in issue #27752, some Debian packages are only recommended. As a consequence, these packages are not installed on the Official Docker image. In that case, if the user wants to install an Odoo module that needs one of these package, the Docker container has to be modified. python3-qrcode and python3-vobject are now part of the latest Debian stable (stretch) and the latest Ubuntu LTS (Bionic Beaver). Also, they are pure python, and very small. Thus, the Debian package can depends on them.