Thursday, September 12, 2024
5 changes · master
Resolved issues and error corrections
This change removes automation-related setup from the Approvals app because it could unintentionally move customers from the standard price plan to a custom plan. Approvals users keep the expected app behavior without triggering an unwanted pricing change.
Original PR description
Approvals app has a dependence on automation and automation makes user go from standard price plan to custom price which shouldn't happen.
This fix aligns asset-related screens with the newer "list" view naming instead of the older "tree" wording. It helps keep the interface and configuration consistent with recent platform changes, reducing small display or compatibility issues.
Original PR description
[FIX] base/ir.ui.view: fix use 'list' instead of 'tree' see: https://github.com/odoo/odoo/pull/159909
Fixed a visual issue where WhatsApp partner message bubbles appeared unnecessarily faded. This keeps message bubbles easier to read and consistent with the intended conversation styling.
Original PR description
The WhatsApp partner message bubble had an unnecessary `opacity-25` class assigned. The original purpose of the line was to apply a `light-green` background to the bubble. However, as this would conflict with the existing color formatting for message bubbles, this line has now become redundant.  
This fix prevents a validation error when adding a new work order step to a manufacturing order after another step has already started. It keeps work order dependencies in the correct sequence, so production teams can update operations without creating false circular dependencies.
Original PR description
### Steps to reproduce: - Create a MO for a product without BOM (no need of components) - Go to the "Work Orders" tab and create 2 operations: op1 and op2 - Confirm the MO - Start the operation…
### Steps to reproduce: - Create a MO for a product without BOM (no need of components) - Go to the "Work Orders" tab and create 2 operations: op1 and op2 - Confirm the MO - Start the operation waiting for an other WO (op2) - Create a third operation: op3 - Save #### > Validation Error: You cannot create a cyclic dependency. ### Cause of the Issue: During the creation of op3, all the workorders of our MO will be confirmed to ensures that the links of the 3 operations are correctly made: https://github.com/odoo/odoo/blob/d2ce6622f2d6f1917dc319112a688e35a73c2088/addons/mrp/models/mrp_workorder.py#L469-L474 This will trigger a call of the `_link_workorders_and_moves` to re-link them all. However, during this call since op2 has been started the order of the workorders will be op2 > op1 rather than op1 > op2 and sincethe MO has no bom nor `operation_id` the records will not be reordered correctly before being linked: https://github.com/odoo/odoo/blob/d2ce6622f2d6f1917dc319112a688e35a73c2088/addons/mrp/models/mrp_production.py#L1472-L1473 https://github.com/odoo/odoo/blob/d2ce6622f2d6f1917dc319112a688e35a73c2088/addons/mrp/models/mrp_production.py#L1485-L1487 This will create a loop on the m2m dependency since op1 will be blocked by op2 and op2 is already blocked by op1. This is detected by the framework which raises the error. opw-4105603 X-original-commit: dda575f8c9fcdfcb3a1a72429d5c05ede86a7c4e
The barcode app now uses text buttons instead of relying on icons alone, making actions easier for users to understand. Related manufacturing and self-order kiosk dialogs were also adjusted for a more consistent, centered presentation.
Original PR description
*: mrp_workorder, pos_self_order_iot This commit aims to add more text to the UI of the barcode app, in case users don't know the meaning of the illustrations. A text is shown in a button now instead. For the IOT module, the template has been tweaked, to allow visual consistency with the Install Kiosk action dialog. Titles are centered horizontally. task-4160938