Wednesday, October 2, 2019
6 changes · master
Enhancements to existing features
Message posting with email templates can now use an existing automatic commit option that was previously only available in a lower-level mail process. This makes it easier and safer for custom developments to send templated messages in long-running or batch operations.
Original PR description
The underlying `mail.compose.message` model has a useful `auto_commit` argument when sending emails, which is unavailable when posting messages with template. This patch simply exposes the preexisting feature, to ease developments that need it. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr @Tecnativa
This update removes use of an obsolete calendar view setting that had already been retired. It helps keep the web interface tests and configuration aligned with current behavior, reducing maintenance risk without changing day-to-day user workflows.
Original PR description
Description of the issue/feature this PR addresses: `readonly_form_view_id` was removed in 369c20a99bd25172f72f4efde870172a4729aadc. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update improves Odoo's internal testing tools by allowing automated web requests to include additional request options such as custom headers. This helps CI and test workflows better simulate real-world scenarios without changing customer-facing behavior.
Original PR description
Description of the issue/feature this PR addresses: It improves CI framework Current behavior before PR: ``url_open`` cannot be called with custom headers Desired behavior after PR is merged: extra params can be passed to request -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update improves the calendar model description to avoid confusion with similarly named event models. It helps users and administrators better distinguish calendar events from other event-related records in Odoo.
Original PR description
Description of the issue/feature this PR addresses:
Current behavior before PR:
`_description = "Event"` is already there for `event.event`
Desired behavior after PR is merged: No more confusion due to same model name
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prResolved issues and error corrections
Purchase requisitions now locate the relevant product line directly instead of checking every line one by one. This improves performance for requisitions with many lines and makes the purchasing workflow more responsive.
Original PR description
Description of the issue/feature this PR addresses: Having a purchase requisition with many lines defined Current behavior before PR: Each line is looped, until a matching product is reached. Desired behavior after PR is merged: Just filter out the related product, which is faster then looping over all of them. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The event track views now use clearer wording so users understand that the partner field refers to the speaker. The form view also removes duplicated speaker-related information, reducing confusion when managing event sessions.
Original PR description
Before this patch, the word "Partner" wasn't specific enough to make the user know that it was referring to the speaker. This was OK in the form, bug i.e. in the calendar view it's very confusing:  Also, in the form view, the partner field was duplicated, contributing even more to the confusion. And "Speakers" seemed like there were more than 1, as it was previously on v9, but nowadays there's only one:  -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr @Tecnativa