Robot Odoo
9b13494777
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: 1972536 closes odoo/odoo#33233 Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
Odoo
Odoo is a suite of web based open source business apps.
The main Odoo Apps include an Open Source CRM, Website Builder, eCommerce, Warehouse Management, Project Management, Billing & Accounting, Point of Sale, Human Resources, Marketing, Manufacturing, Purchase Management, ...
Odoo Apps can be used as stand-alone applications, but they also integrate seamlessly so you get a full-featured Open Source ERP when you install several Apps.
Getting started with Odoo
For a standard installation please follow the Setup instructions from the documentation.
Then follow the developer tutorials