Wednesday, October 4, 2023
9 changes · master
Enhancements to existing features
This update lets interface widgets receive dynamic information about whether a field should be read-only for the current record. It makes the web interface more consistent and easier to extend when widgets need to adapt to business rules.
Original PR description
As with fields, dynamicProps will be accessible to widgets from extractProps. This commit will make readonly accessible as the first dynamicProps. We'll be able to add more when we need them. DynamicInfo.readonly is true if the field is readonly independently of the record. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Several areas of Odoo were updated to use standard browser or JavaScript classes instead of custom Odoo-specific ones. This is an internal cleanup that should make the code easier to maintain without changing day-to-day user behavior.
Original PR description
This commit replaces some odoo classes by native ones. They are simple classes with no big extensions or not at all. task 3439226
This update removes an older internal shortcut used to trigger actions and updates affected areas to use the current approach. It helps simplify the code behind navigation and workflows without introducing a direct change for end users.
Original PR description
This commit removes the event `do-action` listened on `core.bus` and adpats the place where it was triggered. task 3439226
Delivery operations using carrier rate lookup only can now be validated without requiring a customer contact. This aligns the screen rules with the actual shipping process, reducing unnecessary blocking steps for warehouse users.
Original PR description
The requirement of partner_id was put long ago because send_to_shipper() method requires it. But if you look into the python code, you see in _send_confirmation_email() method that the requirement to enter into send_to_shipper() is `integration_level == 'rate_and_ship'` instead of `delivery_type not in ['fixed', 'base_on_rule']`. It means that, with this change, if we have a `delivery_type not in ['fixed', 'base_on_rule']`, we should be able to validate the picking without partner if we have `integration_level == 'rate'`. See python code requirement:  **Description of the issue/feature this PR addresses:** We adapt view requirement to the python requirement. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Removed obsolete background service compatibility code that is no longer needed. This simplifies maintenance for the platform without changing day-to-day user workflows.
Original PR description
This commit removes the legacy service mappers which are useless now. task: 3439226
This update removes outdated service mapping code that is no longer needed. It helps keep the system simpler and easier to maintain without changing day-to-day user workflows.
Original PR description
This commit removes the legacy service mappers which are useless now. task: 3439226
This update replaces some custom Odoo code classes with standard native ones where no special behavior was needed. It is an internal cleanup that should make the Belgian POS blackbox code easier to maintain without changing day-to-day user workflows.
Original PR description
This commit replaces some odoo classes by native ones. They are simple classes with no big extensions or not at all. task 3439226
This update removes an older behind-the-scenes way of launching actions and updates the affected barcode, manufacturing, quality control, and Studio screens to use the newer approach directly. It should make these areas easier to maintain without changing day-to-day user workflows.
Original PR description
This commit removes the event `do-action` listened on `core.bus` and adpats the place where it was triggered. task 3439226
It seems that the check register report was missing some translation terms, it's because this report is present in the l10n_us_reports localisation and so it's not updated each version. In this PR, we will add the pot file. task: 3491716
Original PR description
It seems that the check register report was missing some translation terms, it's because this report is present in the l10n_us_reports localisation and so it's not updated each version. In this PR, we will add the pot file. task: 3491716