Saturday, May 24, 2025
2 changes · saas-18.3
Resolved issues and error corrections
This fix ensures that point of sale users see an error message again when an IoT device action fails, instead of the issue being hidden. Background polling still avoids repeated connection warnings, so users get clearer alerts without notification spam.
Original PR description
In https://github.com/odoo/odoo/pull/210149, changes were made to the IoT longpolling methods to eliminate multiple error notifications when the IoT box couldn't be reached. However, these changes went a bit too far as it also broke error messages in the PoS, since they relied on the `action` method throwing an error when something went wrong. Instead, it currently fails silently. This commit reverts the change only for the `action` method (the polling method will still not throw errors). Enterprise PR: https://github.com/odoo/enterprise/pull/86166 task-4787494 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The stock forecast widget now stays hidden on incoming receipts, where forecast warnings are not relevant. Availability labels are also adjusted so internal transfers require full demand coverage, while deliveries can be marked available when there is any positive forecast stock.
Original PR description
Commit https://github.com/odoo/odoo/commit/4fbd88ad3ac2d92b47b024b96f1c40ed4b3f97e3 changed the forecast widget decoration on `stock.move` but made it visible on receipt. As it doens't make sense to see a potential forecast issue on a incoming move, this commit hides the widget in those cases. Moreover, we introduce a computation difference between internal and delivery transfers. Internal transfers will be marked as `Available` if the entire demand quantity is available. Deliveries need only a positive forecast quantity to be marked as `Available`. Task: 4747117 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr