Saturday, December 20, 2025
2 changes · saas-18.4
Resolved issues and error corrections
This update resolves an issue where administrators could access employee details from the Point of Sale (PoS) frontend. The fix simply disables the ability to open the employee form, aligning with the intended use of employee data within the backend system. This improves the user experience and prevents unnecessary access.
Original PR description
Steps to reproduce ------------------ 1. Enable "Log in with Employees" 2. Login with any employee and make an order 3. Switch to the admin, "Mitchell Admin" usually 4. Go to the paid orders (we are still in PoS UI not in the backend), and select the order paid in step 2. 5. Click on "Details", the order form will appear, click on the "Cashier" name A traceback will appear, saying 'Cannot find key "hr_employee_form" in the "views" registry'. The fix ------- We simply disable the employee_id field; it will not try to open the employee form anymore. That is much simpler than adding all the required hr assets to the PoS frontend. Employee details are meant to be seen and navigated from the backend. opw-5252486 Forward-Port-Of: odoo/odoo#240012
This update enhances how other Odoo modules can customize activity actions. By separating the action execution step, developers can now easily add specific behaviors, like loading custom views, without needing to duplicate existing logic. This improves flexibility and integration with other parts of the system.
Original PR description
The `openActivityGroup` method in `ActivityMenu` currently handles both the preparation of filters (domains, contexts) and the actual execution of the action. This coupling prevents other modules from intercepting the action execution to inject specific behaviors—such as loading a specific server-side action or specialized views—without completely overriding the method and duplicating the filter logic. This commit extracts the final execution step into a new method `executeActivityAction`. This allows extending modules (e.g., `documents`) to customize the action load (e.g., to ensure specific JavaScript hooks are initialized) while relying on the base implementation for domain and context generation. Task-5187045 Forward-Port-Of: odoo/odoo#240560 Forward-Port-Of: odoo/odoo#238377