Daily updates from Odoo
Navigate
Branch
Friday, May 31, 2019
11 changes
Security fixes and vulnerability patches
Employee information is now split between private HR records and public profiles, so staff can view appropriate work information without exposing sensitive HR data. This improves privacy and clarity for HR, payroll, appraisals, and timesheet workflows while still allowing employees to manage their own profile details.
Original PR description
Purpose ======= 1/ Robustness & security: right now it is not easy to understand and do something clean in term of security (hr people vs employees, private info vs public). A HR officer doesn't know…
Purpose ======= 1/ Robustness & security: right now it is not easy to understand and do something clean in term of security (hr people vs employees, private info vs public). A HR officer doesn't know if he can write something on the chatter. Currently, a note will be visible for all the employees who have access to the employee form view for example. 2/ In term of business, it makes sense to let a hr manages payroll stuff (contract, employees private information, ... and other employee see public information (résumé and work information) Specification ============= Introduce 2 new models: - hr.employee.base (AbstractModel): This represents the basic skeleton model on which the shared fields and methods between the public and the private employees models. - hr.employee.public (_auto=False): This is a sql view based on the employee values, readable for an internal user (i.e. an employee). The model hr.employee is not readable anymore for an employee. There are now 3 ways to access the employee data: 1/ From the hr.employee views. HR officer access rights are required 2/ From the public profile. The public data for an employee are accessible but can't be modified. 3/ From the 'My Profile' menu. A classic employee can access its own data from there, and can modify them. TaskID: 1961151
New functionality added to Odoo
Purchase reporting now includes a dedicated dashboard with chart and pivot views, helping teams analyze purchasing activity more easily. The warehouse dashboard wording was also refined for clearer business reporting.
Original PR description
Task : https://www.odoo.com/web?#id=1857130&action=327&model=project.task&view_type=form&menu_id=4720 Pad : https://pad.odoo.com/p/r.ada054bb8e9125979836902bf646ec8a
Adds a localized Profit and Loss report for Vietnamese accounting reports, including Vietnamese translation support. This helps businesses operating in Vietnam produce financial statements that better match local reporting needs.
Enhancements to existing features
This update streamlines several HR workflows, including employee creation, time-off calendar visibility, team time-off management, and payroll ordering. It also removes a Belgium-specific contract field from the standard contract app and makes applicants explicitly choose their certificate during salary configuration, reducing mistakes.
Original PR description
1. hr_holidays: Clean manager form refs Purpose: Ease modification/addition of views and actions (in particular when inheriting actions in hr_holidays_gantt) Specification: Use `form_view_ref` in the…
1. hr_holidays: Clean manager form refs
Purpose:
Ease modification/addition of views and actions (in particular
when inheriting actions in hr_holidays_gantt)
Specification:
Use `form_view_ref` in the action context
instead of the form xml id in all views.
+ Add tree view from "Time Off / My Team"
2. hr_contract: Remove social secretariat field
Social secretariat is a Belgian concept. It does not make
sense to have this in the standard contract app.
Will be reintroduced in l10n_be_hr_payroll (or internal)
if really needed.
Move `job_id` in the right group to easily add fields
on the right with view inheritance.
3. hr_holidays: Display leaves in calendar
Purpose:
When a leave is created and approved, it can also create
a meeting in the calendar. In the leave type configuration
a particular meeting type can be chosen.
The purpose is to simplify this.
Specification:
Remove the choice of meeting type.
The choice should be:
Display Leaves in calendar: Yes/No (checkox)
4. hr: Direclty create user's employee
5. hr_holidays_gantt: Improve gantt views
6. hr_contract_salary: Make applicant's certificate required
Purpose:
Currently, on the salary configurator frontend, the certificate
is a radio button, with a default value selected.
Some applicants don't change the default value, even if it
is not their certificate.
Applicant should always explicitely set their certificate.
Specification:
Make the certificate a required field without a default value.
To reuse the existing validation logic of the salary JS, the input
is now a `select` instead of a `radio`.
7. hr_payroll: Sort payslips by date
Currently, payslips and payslip batches are sorted
by creation date, oldest first.
It's better to sort them according to their dates, more
recent firsts.
8. hr_holidays_gantt: Rename Leave into Time Off
9. hr_payroll: Adapt view inheritance social secretariat field
The field `reported_to_secretariat` of `hr.contract`
has been removed in Community: #4284
This commit adapts view inheritance after this change.
10. hr_payroll: Move schedule_pay from contract to structure
Schedule pay depends on the salary structure, not the contract.
e.g. for the same contract, the regular pay is every month,
but the 13th month is every year.
Hence the field is moved to `hr.payroll.structure` and made
a related field on `hr.contract`.
Note: the field schedule_pay is currently unused.
It could probably be removed completly remove on the contract.
11. hr_payroll: Add stat button on structure type
12. hr_payroll: Merge hr_payroll_gantt into hr_payroll
Since hr_payroll is now an enterprise module, an additional module
is no longer needed to add gantt views.
After this commit, `hr_payroll_gantt` module is deleted and everything
is moved to `hr_payroll`.
13. hr_payroll: Improve payroll menus
Employees
- Employees
-Contracts
Work Entries
- Work Entries
- Conficts
Payslips
- To Pay (show only draft payslips)
- All Payslips (newest first)
- Batches (newest first)
Reporting
- Payroll
- Meal Voucher (l10n_be_hr_payroll)
Configuration
- Settings
- Work Entries
* Work Entry Types
- Salary
* Structure Types
* Structures
* Rules
* Other Input Type (debug mode)
14. hr_payroll: Rename demo data
The renamed demo structure is the main
structure. It should have a general name
instead of a name linked to a particular
employee.
15. l10n_be_hr_payroll: Set default 38h calendar for BE
Set the default calendar of Belgian companies to 38 hours/week
TaskID: 1972536Employee information is now split between private HR-only records and public profiles visible to regular employees. This makes sensitive HR data easier to protect while still allowing staff to view relevant workplace profile information and manage their own profile.
Original PR description
Purpose ======= 1/ Robustness & security: right now it is not easy to understand and do something clean in term of security (hr people vs employees, private info vs public). A HR officer doesn't know…
Purpose ======= 1/ Robustness & security: right now it is not easy to understand and do something clean in term of security (hr people vs employees, private info vs public). A HR officer doesn't know if he can write something on the chatter. Currently, a note will be visible for all the employees who have access to the employee form view for example. 2/ In term of business, it makes sense to let a hr manages payroll stuff (contract, employees private information, ... and other employee see public information (résumé and work information) Specification ============= Introduce 2 new models: - hr.employee.base (AbstractModel): This represents the basic skeleton model on which the shared fields and methods between the public and the private employees models. - hr.employee.public (_auto=False): This is a sql view based on the employee values, readable for an internal user (i.e. an employee). The model hr.employee is not readable anymore for an employee. There are now 3 ways to access the employee data: 1/ From the hr.employee views. HR officer access rights are required 2/ From the public profile. The public data for an employee are accessible but can't be modified. 3/ From the 'My Profile' menu. A classic employee can access its own data from there, and can modify them. TaskID: 1961151
Purchase reports now show dates that better match the purchasing workflow: draft requests use the order date, while confirmed purchase orders use the confirmation date. Report amounts are also calculated in the company currency, making purchase reporting more consistent and easier to compare with sales reporting.
Original PR description
Task : https://www.odoo.com/web?#id=1857130&action=327&model=project.task&view_type=form&menu_id=4720 Pad : https://pad.odoo.com/p/r.ada054bb8e9125979836902bf646ec8a
This update improves how scrap records are handled around manufacturing by avoiding unnecessary manufacturing order information in scrap views. It helps users focus on relevant stock and production details when recording or reviewing scrap.
Original PR description
Task : https://www.odoo.com/web?debug=true#id=1959647&action=327&model=project.task&view_type=form&menu_id=4720 Pad : https://pad.odoo.com/p/r.c11eddca69ea9713e7ae09d14dc2df62 I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update improves several HR workflows, including clearer time off calendar settings, better payroll menus, newer-first payslip sorting, and required certificate selection for salary offers. It also removes Belgium-specific contract details from the standard contract app and consolidates payroll Gantt views to make the apps easier to use and maintain.
Original PR description
1. hr_holidays: Clean manager form refs Purpose: Ease modification/addition of views and actions (in particular when inheriting actions in hr_holidays_gantt) Specification: Use `form_view_ref` in the…
1. hr_holidays: Clean manager form refs
Purpose:
Ease modification/addition of views and actions (in particular
when inheriting actions in hr_holidays_gantt)
Specification:
Use `form_view_ref` in the action context
instead of the form xml id in all views.
+ Add tree view from "Time Off / My Team"
2. hr_contract: Remove social secretariat field
Social secretariat is a Belgian concept. It does not make
sense to have this in the standard contract app.
Will be reintroduced in l10n_be_hr_payroll (or internal)
if really needed.
Move `job_id` in the right group to easily add fields
on the right with view inheritance.
3. hr_holidays: Display leaves in calendar
Purpose:
When a leave is created and approved, it can also create
a meeting in the calendar. In the leave type configuration
a particular meeting type can be chosen.
The purpose is to simplify this.
Specification:
Remove the choice of meeting type.
The choice should be:
Display Leaves in calendar: Yes/No (checkox)
4. hr: Direclty create user's employee
5. hr_holidays_gantt: Improve gantt views
6. hr_contract_salary: Make applicant's certificate required
Purpose:
Currently, on the salary configurator frontend, the certificate
is a radio button, with a default value selected.
Some applicants don't change the default value, even if it
is not their certificate.
Applicant should always explicitely set their certificate.
Specification:
Make the certificate a required field without a default value.
To reuse the existing validation logic of the salary JS, the input
is now a `select` instead of a `radio`.
7. hr_payroll: Sort payslips by date
Currently, payslips and payslip batches are sorted
by creation date, oldest first.
It's better to sort them according to their dates, more
recent firsts.
8. hr_holidays_gantt: Rename Leave into Time Off
9. hr_payroll: Adapt view inheritance social secretariat field
The field `reported_to_secretariat` of `hr.contract`
has been removed in Community: #4284
This commit adapts view inheritance after this change.
10. hr_payroll: Move schedule_pay from contract to structure
Schedule pay depends on the salary structure, not the contract.
e.g. for the same contract, the regular pay is every month,
but the 13th month is every year.
Hence the field is moved to `hr.payroll.structure` and made
a related field on `hr.contract`.
Note: the field schedule_pay is currently unused.
It could probably be removed completly remove on the contract.
11. hr_payroll: Add stat button on structure type
12. hr_payroll: Merge hr_payroll_gantt into hr_payroll
Since hr_payroll is now an enterprise module, an additional module
is no longer needed to add gantt views.
After this commit, `hr_payroll_gantt` module is deleted and everything
is moved to `hr_payroll`.
13. hr_payroll: Improve payroll menus
Employees
- Employees
-Contracts
Work Entries
- Work Entries
- Conficts
Payslips
- To Pay (show only draft payslips)
- All Payslips (newest first)
- Batches (newest first)
Reporting
- Payroll
- Meal Voucher (l10n_be_hr_payroll)
Configuration
- Settings
- Work Entries
* Work Entry Types
- Salary
* Structure Types
* Structures
* Rules
* Other Input Type (debug mode)
14. hr_payroll: Rename demo data
The renamed demo structure is the main
structure. It should have a general name
instead of a name linked to a particular
employee.
15. l10n_be_hr_payroll: Set default 38h calendar for BE
Set the default calendar of Belgian companies to 38 hours/week
TaskID: 1972536A new automated test was added to verify Belgian payroll calculations for an employee with unpaid hours and leave days, without benefits in kind or a company car. This helps reduce the risk of payroll errors in that specific absence scenario.
Original PR description
Add test about payslip with 4 hours unpaid, 2 days leave, no atn and no car f
Resolved issues and error corrections
This fix prevents an error when someone opens a redirected email link to a record while not logged in. It helps users reach the intended page more smoothly instead of encountering a crash or traceback.
Original PR description
Description of the issue/feature this PR addresses: - Task - https://www.odoo.com/web#id=2000286&action=327&model=project.task&view_type=form&menu_id=4720 - Pad - https://pad.odoo.com/p/r.51f71151b69b178c6d5c51e70fc35535 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix lets Gantt view definitions place field and template sections in either order without causing validation errors. It reduces avoidable setup failures for teams configuring or customizing Gantt views.
Original PR description
Before this commit, In Gantt view, if you try to define field tag before templates tag then you will get validation error because field tag declared after templates tag in .rng file. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr