Monday, January 8, 2024
4 changes
2 changes
Enhancements to existing features
Employees and applicants now have a clearer way to choose company cars in the salary configurator, separating available cars from cars that need to be ordered. Payroll officers gain more control over whether the "To Order" option is shown, and signed offers now better track ordered vehicles for future updates.
Original PR description
The objective of this PR is to simplify the way employees and applicants pick their cars in the salary configurator : 1. We now make a clear distinction between existing cars as fleet.vehicle records…
The objective of this PR is to simplify the way employees and applicants pick their cars in the salary configurator : 1. We now make a clear distinction between existing cars as fleet.vehicle records and fleet.vehicle.models, the selection in the company car will now only contain existing cars. 2. Wishlist was renamed to "To Order" 3. The user can now do a secondary simulation of his salary with his wishlist car 4. The payroll officer has now the possibility to display or not display the "To Order" field in the salary configurator. Added fields : ordered_car_id : Once an offer has been fully signed by both the employee and the hr officer, if the employee selected a car model to order, that model will be created as a fleet.vehicle and be assigned to this field. When the new car is available, a new offer will be generated with this car as the default one. Modified behavior: new_car and new_car_model_id : This field is now a purely technical field, it will serve as information during the signing process to show the hr officer, which car model has been chosen to be ordered. Once an offer is fully signed, it will be emptied again and transfered to ordered_car_id. task-3356387
Features or functions removed from Odoo
Helpdesk ticket types have been removed to simplify how support tickets are categorized. Teams can continue using helpdesk teams, tags, and property fields, reducing clutter in ticket views while keeping flexible reporting options.
Original PR description
purpose: Currently, we have 4 ways of categorizing tickets: helpdesk teams, ticket types, tags, and property fields. It seems overkill and adds clutter to the views of tickets needlessly. Among all of these fields, ticket types seem to be the least useful/versatile as it is a simple selection field that could easily be added with property fields. We are thus removing ticket types. task - 3242226
2 changes
Resolved issues and error corrections
This fix resolves a critical issue where creating an automation rule in subscriptions that triggers a "Create next activity" action would cause the system to enter an infinite loop and crash. The solution adds a safety check to prevent the alert configuration process from repeatedly calling itself with the same parameters, allowing users to successfully set up activity-based automation rules for subscription stage changes.
Original PR description
Steps to reproduce: - Install subscriptions - Create an automation rule with: - Stage goes from "In Progress" to "Churned" - "Create next activity" for the action to do - With activity type set as "To-Do" for example - Save Issues: Infinite recursion occurs as configure_alerts call configure_alerts with the same arguments. Solution: We need to see if we went into _configure_alerts, this is done using a flag in the context. opw-3620679
The Dutch tax and ICP reports that are submitted to government authorities have been updated to comply with new taxonomy rules and validation requirements. Additionally, a rounding option has been added to ensure reported amounts match what is actually submitted, improving accuracy and consistency in tax reporting.
Original PR description
The reports ICP and Tax Report that have to be sent to the Dutch authorities did not pass the validation tests anymore on the authorities' server. They have been updated to the new taxonomy rules. For further maintenance on the taxonomy, see https://www.taxonomie-viewer.nl/ We also add a rounding down option to the Dutch Tax Report to be consistent with the values to export/send. Forward-Port-Of: odoo/enterprise#53432 Forward-Port-Of: odoo/enterprise#50939