Odoo Changelog — 2023-04-27

Thursday, April 27, 2023

3 changes · master

Improvements(3)

Enhancements to existing features

[WIP][IMP] mrp_workorder: remove viewform from tablet

Enterprisemastermrp_workorderquality_mrp_workordermrp_workorder_expirymrp_workorder_iotpurchase_mrp_workorder_qualityquality_mrp_workorder_iotquality_mrp_workorder_worksheetmrp_workorder_hrMedium

The manufacturing work order tablet interface was reworked to remove an inefficient internal form setup and simplify how production and quality steps communicate. This should make the tablet experience easier to maintain and more reliable for shop floor workflows, with related cleanup across quality, IoT, expiry, worksheet, HR, and purchasing integrations.

Original PR description

The tablet view has been developed during owl transition. So the architecture chosen is a main component containing 2 form views (quality.check and mrp.workorder) + sub components. However the communication between both form and main component is a complex bus process not efficient. The purpose of this task is to have something similar to a view.

task 3074299

#manufacturing#tablet#work orders#quality#maintenance

[IMP] *: support unity for overrides of read and search_read

PR #39260

Enterprisemasterhr_appraisalhr_referralsale_timesheet_enterprise

This update prepares several business modules for a safer migration to a newer way of loading records. It reduces the risk of disruption while teams move from the old approach to the new one, especially in appraisal, referral, and timesheet-related workflows.

Original PR description

duplicate code of read and search_read to support unity read. this will help us migrate code from the "old" read to the new without breaking everything

#migration#compatibility#read-logic

[IMP] web_studio, *: use supportedOptions from the field metadata

PR #39847

Enterprisemasterweb_studioknowledge

Odoo Studio now reads editable field widget options directly from each widget's own metadata instead of relying on a separate Studio-maintained list. This makes future widget updates easier to maintain and reduces the risk of Studio showing outdated or inconsistent configuration options.

Original PR description

*: knowledge

This commit removes the need to declare and detail each available option for a specific widget. Now, this list of supported options are detailed directly on the field widget's object, with the supportedOptions attribute.

Only the properties that are tied to a type of field remain in the file of the TypeWidgetProperties component. It is now easier to maintain and update the available options that are editable in studio, since a developer can only implement it in the widget implementation file, without the need to update a list in studio.

task-3259617

#studio#field-options#maintenance

The tablet view has been developed during owl transition. So the architecture chosen is a main component containing 2 form views (quality.check and mrp.workorder) + sub components. However the communication between both form and main component is a complex bus process not efficient. The purpose of this task is to have something similar to a view. task 3074299

*: knowledge This commit removes the need to declare and detail each available option for a specific widget. Now, this list of supported options are detailed directly on the field widget's object, with the supportedOptions attribute. Only the properties that are tied to a type of field remain in the file of the TypeWidgetProperties component. It is now easier to maintain and update the available options that are editable in studio, since a developer can only implement it in the widget implementation file, without the need to update a list in studio. task-3259617