Friday, November 30, 2018
6 changes · master
New functionality added to Odoo
Payroll managers can now generate, review, validate, and use monthly attendance, extra hours, and leave records as payroll benefits. This makes payroll preparation more accurate and gives managers a clearer view of employee schedules before payslips are created.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Adds a new Benefits view so payroll managers can review monthly attendance, extra hours, and leave records before validating them and generating payslips. It also streamlines payslip creation and validation, removes unused payroll inputs and reports, and fixes a crash when creating payslips without a selected journal.
Original PR description
Purpose ======= For payroll purpose, we need to manage attendances. For instance, someone is working only mondays, tuesdays and fridays, but works exceptionally an other day. It must be recorded.…
Purpose ======= For payroll purpose, we need to manage attendances. For instance, someone is working only mondays, tuesdays and fridays, but works exceptionally an other day. It must be recorded. Specification =========== The new models are used to represent attendances, extra hours and leaves (as `hr.benefit`s) in a new window called "Benefits". The schedule of employees for the full month is visible in that view (calendar view). First the benefits needs to be generated (via a button) based on the calendar attendances and leaves. The manager can then check benefits, delete or add some. Only the benefit name and type can be edited (not start and end dates). Once benefits are correct, they can be validated. Validation will fail if they are some leaves to approve or if some benefits overlap on the same day. Benefits cannot be deleted or edited once validated. When benefits are all validated, a button appears to generate payslips. Additional development ================== Most of the time we don't what is the next action that should be done when creating payslips or payslip batches. - Improve the layout, the buttons of the payroll object. - Refactor a little the code to reuse existing chunks of code instead of reinventing the wheel in several methods. - Remove the hr.rule.input model. - Remove an useless report. See each individual commit for more information. TaskID: 1912944, 1903239
Enhancements to existing features
The web client now avoids doing unnecessary work when checking field display rules such as read-only, hidden, or required states. This can improve perceived speed, especially on larger records with many related lines, without changing what users see or how they work.
Original PR description
Before this commit, the web client evaluated all modifiers (readonly/invisible/required) in some cases, even if it only needed one of them. This is clearly not optimal, and I even suppose that for large o2m, it could even have a noticeable effect on web client perceived speed This commit simply make sure that we evaluate only what we need in those cases. Note that it is not really a testable improvement, hence the lack of tests. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
This change restores HS code information to the main Delivery app after it was unintentionally separated in an earlier version. Businesses using delivery and customs workflows can keep managing product tariff codes directly where they expect them, helping avoid migration or shipping documentation gaps.
Original PR description
hs code was dropped in 12.0 however it shouldn't have been (commit 2d738f8563212fbdf10924468b1fcd865524e6d7) commit 498dbc548b2d01bcb16a82e3ed510761000b350e created a new module in order to avoid losing hscode for existing database during migration. This commit set it back as before. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Products now automatically assign their creator as the responsible person, helping route stock-related exceptions to the right user. If no responsible person is set for an activity, Odoo falls back to the system user to prevent errors and keep workflows moving.
Original PR description
…obot as responsible. Task ID - 1913168 Description of the issue/feature this PR addresses: Issue ID - https://www.odoo.com/web#id=1913168&action=327&model=project.task&view_type=form&menu_id=4720 Pad - https://pad.odoo.com/p/r.291190377e3e719ce4a0486436d82b78 Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The salary contract flow was adjusted to align with payroll changes that remove the older rule input mechanism. This helps keep contract salary handling compatible with the current payroll process and reduces reliance on outdated payroll components.