Tuesday, January 30, 2024
3 changes · 17.0
Enhancements to existing features
Users switching active companies are now kept away from pages they can no longer access. If the current record is not available under the newly selected company, Odoo redirects them to the app dashboard instead of showing an access error.
Original PR description
Implemented an enhancement in the logNextCompanies function to improve user experience when changing active companies. Previously, changing the active company could lead to an Access Error. The new implementation checks if the current page would result in an Access Error for the new active company: 1. An ORM call to 'check_access_rule' checks the accessibility of the current record based on the new active company. 2. If staying on the current page would not lead to an Access Error, the user remains there. 3. If it would lead to an Access Error, the user is redirected to the current App's Dashboard. This eliminates the unnecessary friction of encountering an Access Error and having to manually navigate back to a usable page. Task-3029616 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update fixes how representation fees are calculated for part-time employees and significantly improves the speed of payslip generation. Payslip processing time has been reduced from over 15 minutes to just 80 seconds for large batches, making the payroll process much faster and more efficient for HR teams.
This update improves how Odoo automatically selects the correct fiscal position for Argentine businesses. Previously, the system completely overrode automatic detection for Argentina. Now businesses can combine multiple criteria—such as AFIP responsibility type and state location—to automatically apply the right fiscal position. This gives companies more precise tax treatment based on their specific registration status and location.
Original PR description
Task Adhoc: 35708 Task latam: 668 Prior to this commit, fiscal positions auto-detecion was completely override for Argentinian countries. With this improvements the afip responsibility field can be combined as a filter to choose the proper fiscal position. Example of a new use case could be: * Name: Gross Income Perceptions Buenos Aires * Detect Automatically = True * Afip Resp. Type = Responsable Inscripto * Country = Argentina * Federal states = Buenos Aires So, this fiscal position will be automatically choosen only for responsables inscriptos of Buenos Aires. Previous use cases still work. I confirm I have signed the CLA and read the PR guidelines at [www.odoo.com/submit-pr](http://www.odoo.com/submit-pr) This pull request replaces https://github.com/odoo/odoo/pull/150163 Forward-Port-Of: https://github.com/odoo/odoo/pull/147116 Forward-Port-Of: odoo/odoo#150485