Friday, February 9, 2024
8 changes · master
Enhancements to existing features
The Product module now includes demo data showing optional add-ons for an outdoor dining table, such as warranty extension and kits with extra prices. This helps businesses demonstrate product customization choices without creating additional product variants.
Original PR description
Adds demo data in the Product module to showcase the Multi-checkbox attribute. The 'Extra Options' attribute is introduced with the following choices: - 1 year warranty extension (extra price 50) - Cleaning kit (extra price 5) - Protection kit (extra price 10) This attribute is linked to the product: - Outdoor dinning table: - Storable - Price : 589 - Category: Outdoor furniture This setup demonstrates the new attribute's capabilities in enhancing product customization without affecting variant generation. task-3610666 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Discuss now uses a shared helper to fetch certain data once and reuse it when available, while still allowing another attempt if a previous fetch failed. This reduces duplicated handling in the mail app and should make data loading behavior more consistent for users.
Original PR description
In discuss, we often want to fetch data only once but to be allowed to re-fetch in case of failure. Until now, those cases were handled manually. Since this is becoming more and more common to do so, this PR introduces a helper that maintain the state of the fetch and that returns the cached result if available.
Adding or changing a bank account on a bank journal now also updates the related partner record. This keeps financial contact information consistent and reduces duplicate manual entry.
Original PR description
This commit will add an inverse on the bank_account_id so that adding a bank account on the bank journal add it also to the partner. task: 3716666 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The landed cost option is now hidden for product types where it does not apply, such as event tickets, booths, and booking fees. This keeps product setup screens cleaner and reduces the chance of users selecting an irrelevant purchase setting.
Original PR description
In this PR fixes the following issue: - Landed cost boolean is suppose to be visible for a service type product under purchase. But currently it is visible on other type of products specific to other models like booking fees, event tickets, event booths etc. - It should be hidden on other types except service. task-3725202 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
Discuss now loads channel information from one clear place when the app opens, instead of checking and fetching it in two separate startup flows. This reduces redundant background work and helps keep the messaging experience efficient without changing user-facing behavior.
Original PR description
When discuss opens, we want to fetch the channels is it was not already done. Currently, this is done in two places: - When starting the `DiscussClientAction` - When starting the store (with a check on whether discuss is active or not) This PR removes the one in the store service, since the discuss client action is the perfect place to do that.
This change makes it easier to recognize invoice reports in one reusable place. Businesses using customized invoice formats can more easily ensure related electronic documents are included without duplicating larger parts of the reporting process.
Original PR description
Description of the issue/feature this PR addresses: This PR moves the check whether requested report is an invoice one in a separate function so that it can be inherited in case we need to have extra invoice report formats. Current behavior before PR: In case you generate new invoice reports, EDI document will not be included unless you rewrite (or copy/update) the full code of _render_qweb_pdf() and _render_qweb_pdf_prepare_streams() functions. Desired behavior after PR is merged: With this PR, you can only inherits _is_invoice_report() function to add your new report name. Since this is a IMP PR, I am not sure it would be OK to have it in 16.0 as well (which is where I would need the functionality for now) ? --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
When users open Documents from a partner record, the document request form now automatically fills the 'Request to' field with that partner. This saves time and reduces manual entry when requesting documents from customers, vendors, or other contacts.
Original PR description
When reaching Documents from the Documents stat button of a partner, prefill the 'Request to' field with the partner when clicking on Request as there are many chances that we'll ask this partner for a document. task-3688422
A new automated test was added to confirm that Field Service task grouping by assigned user continues to work after shared logic was introduced with Project. This helps reduce the risk of regressions in planning and task management views without changing day-to-day user behavior.
Original PR description
The user_id group expand implementation was changed recently in order for the field service and the project apps to share implementations. There is a test for the project's functionality but no tests for the field service functionality and thus a new test was added for it. task-3696707