Daily updates from Odoo
Monday, January 21, 2019
4 changes · master
Enhancements to existing features
This update renames employee leave management to the more internationally understood “Time Off” and introduces a new dashboard with a calendar and request summary. Employees get a clearer, more intuitive view of their time off balances and requests, while related messages and usability are improved.
Original PR description
Description of the issue/feature this PR addresses: We need to use an international word to define holidays and leaves. Employees needs a good dashboard and leaves summary Desired behavior after PR is merged: We have Time Off (no more leaves). Each user has a intuitive dashboard for his Time Off. The dashboard has a calendar and a summary of all time off and time off request. Some intro messages are more clear and give correct information. id=1916871 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Payroll records, contracts, and salary structures are now better separated by company and country, helping prevent users from viewing or using payroll data that belongs elsewhere. Salary rule accounting settings can now differ by company, reducing the risk of incorrect payroll accounting when multiple companies share the same payroll setup.
Original PR description
Purpose ======= Currently the payroll doesn't manage the multi company Specification ============= 1/ Add ir.rules on hr.contract and hr.payslip to prevent users to access a record in another company. 2/ Add ir.rules on hr.payroll.structure to prevent users to access a record for another country. 3/ Remove company_id fields on models that doesn't require it, as hr.salary.rule.category. 4/ Make the accounting fields on the salary rules company dependent. 5/ Specify the country on the salary structures on the l10n_**_hr_payroll modules. 6/ Add demo data and modify the salary package tour. 7/ Make the car_atn and company_car_total_depreciated_costs fields compute_sudo=True, as one car can be assigned on several contract, for different companies Closes #26866 Closes #25231 Closes #24683 Closes #23814
Payroll records and salary structures are now better separated by company and country, helping users see only the records relevant to their organization. Demo data and the salary package walkthrough were updated so multi-company payroll scenarios are easier to test and understand.
Resolved issues and error corrections
Payroll salary rule accounting can now be managed separately across companies. This prevents one company's accounts from appearing in or overwriting another company's payroll setup, reducing the risk of incorrect payslip accounting.
Original PR description
…nies Before this commit - Install a **l10n_xx_hr_payroll** which includes information of the rules (it always install in the main company: **Company A** in this use case). - Configure the accounting…
…nies Before this commit - Install a **l10n_xx_hr_payroll** which includes information of the rules (it always install in the main company: **Company A** in this use case). - Configure the accounting for the rules - Create **Company B** - Use the same salary rules for both companies, as **l10n_xx_hr_payroll** modules are not multicompany. Behavior: - **Company A** accounts are shown in **Company B** salary rules. - If the accounts are changed in **Company B** rules, it also overrides **Company A** accounts, (which causes major confusions, and great mistakes if a payslip is run). - A salary rule with **Company A** set on `company_id` can still be **seen** through Company B. which causes that it can be mistakenly _ran by a user in Company B_, with the _accounting of Company A_. After this commit: Salary rules accounting can be used with multi-company **OPW** 1847799 Fixes #23814 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr