Odoo Changelog — 2024-06-10

Monday, June 10, 2024

2 changes · saas-17.3

Improvements(2)

Enhancements to existing features

[IMP] pos: Improve UI and access controls across features

Coresaas-17.3point_of_salepos_hrpos_hr_restaurantpos_restaurantMedium

The point of sale experience has been refined with clearer employee access controls, better restaurant payment handling, and small interface improvements. These changes help staff use the system more confidently while reducing mistakes such as unauthorized product creation or incorrect payment method selection.

Original PR description

- Implemented employee login and update form placeholders for basic and advanced rights in the edit dashboard.
- Enforced primary payment method after order placement in pos_restaurant.
- Restricted basic user rights from creating products.
- Swapped positions of Lock and Print buttons, added a lock icon for clarity.
- Adjusted floor plan corner selector size.
- Hid zero dollar price for combos in the cart. 
 
Task ID: 3916835


---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

#point of sale#restaurant#employee access#payments#user interface

[IMP] loading: signal changes on registry new

PR #168180

Coresaas-17.3baseMedium

After a module is installed, Odoo now notifies running processes that the system registry has changed. This helps workers pick up database structure updates such as new rules or defaults without relying on a manual restart, reducing inconsistent behavior after installations.

Original PR description

Installing a modules and running the post test in the same run will lead to a state where the registry_invalidated flag is set, because the registry loading did not clear the flag after install.

Actually, it makes sense to signal the change after installing a module. The schema may have changed, with new constraints, new default, but existing worker won't take that into account.

This issue already exist for server admin that need to restart manually all workers after a manual install.

The proposed solution will signal the changes after load_modules, just after comitting the new registry schema.

A possible issue with that may be to trigger a reload before the process is restarted, if the code changed. The assets and static resources may be reload immediately even if the python code is not reloaded yet. But this is already an issue now and it is unlikely to do that.

#module-installation#registry#workers#reliability

- Implemented employee login and update form placeholders for basic and advanced rights in the edit dashboard. - Enforced primary payment method after order placement in pos_restaurant. - Restricted basic user rights from creating products. - Swapped positions of Lock and Print buttons, added a lock icon for clarity. - Adjusted floor plan corner selector size. - Hid zero dollar price for combos in the cart. Task ID: 3916835 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Installing a modules and running the post test in the same run will lead to a state where the registry_invalidated flag is set, because the registry loading did not clear the flag after install. Actually, it makes sense to signal the change after installing a module. The schema may have changed, with new constraints, new default, but existing worker won't take that into account. This issue already exist for server admin that need to restart manually all workers after a manual install. The proposed solution will signal the changes after load_modules, just after comitting the new registry schema. A possible issue with that may be to trigger a reload before the process is restarted, if the code changed. The assets and static resources may be reload immediately even if the python code is not reloaded yet. But this is already an issue now and it is unlikely to do that.