Friday, January 27, 2023
16 changes · master
Enhancements to existing features
This update improves performance in timesheet, project, and sales-related calculations by avoiding unnecessary sorting when grouping records. Business users should see faster loading or recalculation in affected sales timesheet and project workflows, with no intended change to visible behavior.
Original PR description
In this commit improve the following performance
- replace read_group to _read_group because we don't need the order in
compute methods.
- read_group uses orderby which was sorting the records of groupby
- by replacing read_group to _read_group will help us in performance by
getting recorded faster than earlier
task-3149468The Uruguayan localization content has been rewritten in English and paired with Spanish translation files. This aligns the module with Odoo localization standards, making it easier to maintain while preserving Spanish language support for users in Uruguay.
Original PR description
All the localisation should be written in english and then translated to the native language of the country. In this case, the Uruguayan localisation was written is Spanish, this PR translate the module in english and add the corresponding PO file in spanish. Task-id: 3126154 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The live messaging service can now be extended to handle more types of real-time events. This makes it easier to add future custom behavior without changing the core websocket entry point.
Original PR description
PURPOSE: Currently `_serve_ir_websocket` can handle only two events. You can't add custom events to this method. Make this method extensible to handle more events for `Websocket` bus service. SPECIFICATION: Moved `_serve_ir_websocket` method to `IrWebsocket` model. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
When a lead is enriched and its details are later updated, Odoo will send feedback to improve the shared company directory. This helps keep company records more accurate over time, improving future lead enrichment results for users.
Original PR description
Description of the issue/feature this PR addresses: After the 'Enrich' button is used on a lead, any change to the lead information will send a vote to iap-directory. The votes will be used to improve the accuracy of the company record . Needs this PR in order to work: https://github.com/odoo/iap-apps/pull/374 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Odoo's AsiaPay integration now lets businesses choose the correct AsiaPay brand for their merchant account, such as PesoPay for the Philippines, SiamPay for Thailand, or BimoPay for Indonesia. This helps merchants in those countries connect to the required local payment endpoint instead of being limited to PayDollar.
Original PR description
Issue: Merchant account created inside Philippine will use PesoPay, created inside Thailand will use SiamPay, and created inside Indonesia will use BimoPay. Currently. only PayDollar is available.…
Issue: Merchant account created inside Philippine will use PesoPay, created inside Thailand will use SiamPay, and created inside Indonesia will use BimoPay. Currently. only PayDollar is available. Cause: Missing PesoPay, SiamPay and BimoPay. Solution: Add a brand setting on payment provider to allow user to select which branch will be used. More: - What is PayDollar, PesoPay, etc. to AsiaPay? PayDollar, PesoPay, SiamPay, BimoPay is the same system under AsiaPay but is for different countries to apply. PesoPay is for the PH market SiamPay is for the TH market BimoPay is for the ID market while PayDollar is for all other market likes HK, CN, MO, TW, SG, MY, IN, VN, NZ and AU - Why are there multiple endpoints for a given API? Below reasons are from AsiaPay side Local regulators requirements for BimoPay Branding purposes to localize for the users for PesoPay and SiamPay. - Why didn't we integrate all these endpoints in the first version of our AsiaPay implementation? We got in touch with AsiaPay after our first integration. Therefore after partnership established with AsiaPay, they provide more integration guides on the whole development - If many customers ask for these endpoints? Right now, there is no customers asking for these endpoints. However if they register AsiaPay under certain countries, they have to use the other endpoints otherwise they will not able to use AsiaPay on Odoo at all. task-3073748 See also: - https://github.com/odoo/odoo/pull/108342 (deleted by mistake) - https://github.com/odoo/odoo/pull/108971 (targeting 16.0 but need to target master) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Costa Rica localization content has been standardized so its source text is in English, with Spanish provided through translations. This improves consistency with Odoo localization practices and makes future translation maintenance easier.
Original PR description
Before this PR, all this localisation was written in spanish, but all the localisation have to be written in english and then translated back in the native language. This PR correct that. Task-id: 3149070 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Finnish localization module now uses English source text with Finnish translations maintained separately. This improves translation consistency and makes future updates easier for multilingual deployments.
Original PR description
Before this PR, all this localisation was written in Finnish, but all the localisation have to be written in english and then translated back in the native language. This PR correct that. Task-id: 3151267 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Dutch localization content has been converted to English as the source language, with Dutch translations added separately. This improves consistency with Odoo localization standards and makes future maintenance and translation updates easier.
Original PR description
All the localisation should be written in english and then translated to the native language of the country. In this case, the Dutch localisation was written is Dutch, this PR translate all the module in english and add the corresponding PO file in Dutch. Task-id: 3115909 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The accounting interface now makes debit note actions less prominent, reflecting that these documents are rarely used in many markets. This helps keep critical accounting screens focused on the most common workflows while still preserving debit note functionality for localizations that need it.
Original PR description
Debit Notes are a type of financial documents that is not very often used. Even though it's an official document type, in many countries their usage is not Odoo does not come with a preinstalled Debit Note management, but it can be added by installing the module account_debit_note. The module as mostly been developped following localisation requirements, and while it's a corner case, it appears all the time in one of our most critical screen. Let's make it a bit more discrete. task-3125955 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
Odoo’s email composer is being updated to make message content, recipients, and templates behave more predictably. Notifications now handle attachments more consistently, and related preview, wording, and test coverage improvements reduce errors in email-based workflows.
Original PR description
RATIONALE Remove _onchange_template_id / defaults usage for composer fields. It lacks control and make value computation hard to understand and predict. SPECIFICATIONS Remove _onchange_template_id /…
This update improves performance in several service, planning, timesheet, quality, and sales-related areas by using a faster way to calculate grouped information when sorting is unnecessary. Business users may notice quicker loading or calculation times in related views and reports, with no intended change to functionality.
Original PR description
In this commit improve the following performance
- replace read_group to _read_group because we don't need the order in
compute methods.
- read_group uses orderby which was sorting the records of groupby
- by replacing read_group to _read_group will help us in performance by
getting recorded faster than earlier
task-3149468The follow-up report now explains more clearly what the assigned responsible person means. This helps users understand that the role applies specifically to manual follow-up activities, reducing confusion when managing customer follow-ups.
Original PR description
The tooltip for `followup_responsible_id` should specify what responsible of follow-up report means, an highlight it concerns the manual follow up activities. task-3145326
Data cleaning and data merge now use clearer notification settings where available instead of relying on hidden context values. This is a minor internal improvement that supports cleaner maintenance and more consistent communication behavior.
Original PR description
Just use a parameter instead of a context key when possible. See community PR for more details. Followup of odoo/odoo#99482 Task-2710804 (Mail: Clean MailThread API)
The Dutch reporting module now uses English as the source language and provides Dutch translations separately. This improves consistency across localizations and helps maintain accurate Dutch financial report labels for users.
Original PR description
All the localisation should be written in english and then translated to the native language of the country. In this case, the Dutch localisation was written is Dutch, this PR translate all the module in english and add the corresponding PO file in Dutch. Task-id: 3115909
The Finnish reporting module now keeps its report labels in English as the source language and provides Finnish through translations. This makes the localization easier to maintain consistently while preserving the Finnish user experience.
Original PR description
Before this PR, all this localisation was written in Finnish, but all the localisation have to be written in english and then translated back in the native language. This PR correct that. Task-id: 3151267
Several HR reporting screens now open directly in graph view, making trends easier to see without extra clicks. Employees Analysis adds an employee count measure, Appraisal Analysis defaults to a yearly Gantt view, and Recruitment Analysis is grouped by creation date for clearer activity tracking.
Original PR description
1) We show first graph view instead of pivot view in below report.
-Employees Referral Analysis
-Time In Stage Analysis
-Payroll Analysis
-Employees Analysis
2) Add employee count measure in Employees Analysis report
3) set the default year mode in Gantt of Appraisal Analysis
4) Improve Recruitment Analysis report
Currently in the graph view of the hr recruitment report, the horizontal axis is based on source.we base it
on create instead of source.
task: 3014453RATIONALE Remove _onchange_template_id / defaults usage for composer fields. It lacks control and make value computation hard to understand and predict. SPECIFICATIONS Remove _onchange_template_id / defaults usage for composer fields. It lacks control and make value computation hard to understand and predict. Split _onchange_template_id + default_get + get_record_data usage into editable computed stored fields. Each field should have its own method with its triggers (template, composition mode, ...). OTHER CHANGES Improve 'message_notify' to behave like 'message_post' with attachments. Add some parameters to the notification process to lessen a bit context usage. Improve wording of recently added features. Improve test coverage of recently modified features. Cleanup hr_recruitment_survey field naming and file organization, done when fixing a bug not really related to this branch. Fixup mail template preview wizard, some rare bugs when previewing notably attachments. LINKS This PR is build on previously merged content that originated form this PR. See notably odoo/odoo#99482 / Task-2710804 (Mail: Clean MailThread API). Task-3093257 (Mail: The Composer Update) Task-2088884 (Mail: Use editable computed stored fields in compose Prepares Task-3149286 (Account: Cleanup account.invoice.send wizard)