Friday, January 6, 2023
4 changes
Enhancements to existing features
Warehouse barcode users now hear an error sound when they scan an invalid barcode or one that cannot be handled at the current step. Successful scans also get a brief visual flash, making scanning outcomes clearer and helping users correct mistakes faster.
Original PR description
Plays a sound effect when the user scans a wrong barcode (either a non-existing barcode or a barcode who can't be processed in the current state of the app's flow). task-2871895
This update prevents validation errors in specific Odoo views by removing an unsupported rental report directive and temporarily exempting the Knowledge article form from new validation rules. This helps keep affected screens working while stricter checks are introduced to improve system reliability.
Original PR description
[FIX] sale_renting: remove unsupported t-field in arch This commit is the enterprise counter part of odoo/odoo#107083. `t-field` isn't a valid qweb directive. As a matter of fact, the commit…
[FIX] sale_renting: remove unsupported t-field in arch This commit is the enterprise counter part of odoo/odoo#107083. `t-field` isn't a valid qweb directive. As a matter of fact, the commit introducing it noted that it wasn't working [1]. Now that we validate qweb directives used in archs, this one would throw an error. We thus remove it. Task 3085357 [1] https://github.com/odoo/enterprise/commit/11a41bb72a1f045702f37eddc0f583a025112d0c#diff-97c66f033e6f370fadfb24d5cea5f6a09ab3e95ceda55b0c90e38aa1c9d24425R75] [IMP] knowledge: ir.ui.view: bypass owl directives validation The arch of the knowledge article form view is written as an owl template. It uses several owl directives and a lot of js implementation details, which is forbidden. PR odoo/odoo#107083 adds validation steps to detect forbidden owl directives in archs. As a consequence, the knowledge form view would crash at validation. This commit bypasses the validation for the knowledge form view. This override could be removed as soon as that view is fixed (it should become a client action). Task 3085357
This update adds a validation check to ensure a view’s main structure matches its declared type. It helps prevent incorrectly configured views from being saved, reducing the risk of broken or inconsistent user interfaces.
Original PR description
This PR follows #108073
Just ensure the root node of the view architecture matches the view type.
e.g.
Valid:
```xml
<form>
...
</form>
```
Invalid:
```xml
<data>
<div>
...
</div>
<form>
...
</form>
</data>
```Project tasks now alert users when a task is scheduled to start before another task it depends on is completed. This helps teams plan work in the right order and avoid timeline conflicts in project schedules.
Original PR description
[IMP] project: improve UX **Before this commit:** Let's consider task A depending of task B. Task A can be planned before task B. Example: Task A planned from 01/01/2020 to 05/01/2020 and Task B planned from 06/01/2020. **In this commit:** As task A is depending of task B, task B should be done before task A and the planned_date_begin of task A should be greater or equal to planned_date_end of task B. A new bootstrap alert will be displayed when a task is planned before a task on which it depends. task-3053344