Odoo Changelog — 2024-03-12

Tuesday, March 12, 2024

2 changes · 17.0

Improvements(2)

Enhancements to existing features

[FW][IMP] iot: Create ctypes payments parent

Enterprise17.0iotpos_iotpos_iot_sixMEDIUM

This update consolidates repeated code from multiple payment terminal drivers into a shared parent class, making the system easier to maintain and update. All payment terminals now benefit from improved features like smarter sleep management and better handling of simultaneous requests, ensuring more reliable payment processing across all supported devices.

Original PR description

Currently, we have some code repeating in SixDriver, WorldlineDriver_L and WOrldlineDriver_W.

The goal of this PR is to move this code to a parent class for easier maintenance and better code strcture

Additionally, it applies the code to every ctypes dependant terminal driver, adding some features like "smart sleep" or rejecting double request processing when the terminal is busy for every single of them

task-3707945

Forward-Port-Of: odoo/enterprise#57064

#payment-terminals#code-maintenance#reliability#refactoring

[FIX] web_studio: reportEditor meaningful display when loading error

PR #58491

Enterprise17.0web_studioMEDIUM

The report editor now displays meaningful error information when reports fail to load in debug mode, allowing administrators to see what went wrong and access the problematic views for troubleshooting. This improvement helps with report recovery and migration processes by providing visibility into issues that were previously hidden from users.

Original PR description

Since commit [1], the report editor never crashes at loading time. This is intended to ease the migration process, or report recovery in general, where the operator could reset the views, explore the diff of some views, or edit their plain XML.

However, commit [1] did not offer a way to actually see the error in the reportEditor itself. This was on purpose as the lambda user would not know what to do anyway with that information.

This commit aims at offering that piece of information in case we are in debug mode. The display of the error allows to open the incriminating views in a dialog, and see some basic information on them, as well as, obviously, the error message and type.

opw-3735973

[1]: 62c167f87176674cbabad976d93eeb717f73df7a

#report_editor#error_handling#debug_mode#user_experience

Currently, we have some code repeating in SixDriver, WorldlineDriver_L and WOrldlineDriver_W. The goal of this PR is to move this code to a parent class for easier maintenance and better code strcture Additionally, it applies the code to every ctypes dependant terminal driver, adding some features like "smart sleep" or rejecting double request processing when the terminal is busy for every single of them task-3707945 Forward-Port-Of: odoo/enterprise#57064

Since commit [1], the report editor never crashes at loading time. This is intended to ease the migration process, or report recovery in general, where the operator could reset the views, explore the diff of some views, or edit their plain XML. However, commit [1] did not offer a way to actually see the error in the reportEditor itself. This was on purpose as the lambda user would not know what to do anyway with that information. This commit aims at offering that piece of information in case we are in debug mode. The display of the error allows to open the incriminating views in a dialog, and see some basic information on them, as well as, obviously, the error message and type. opw-3735973 [1]: 62c167f87176674cbabad976d93eeb717f73df7a