Daily updates from Odoo
Wednesday, May 29, 2019
25 changes · master
New functionality added to Odoo
Point of Sale can now connect to payment terminals through the IoT Box, starting with Ingenico devices used in Benelux. This lets cashiers send card payments directly to a linked terminal and receive payment status updates automatically, reducing manual entry and checkout errors.
Original PR description
With this PR we create a new type of device for IoT Box, payment terminal. We integrate this new type of device in the pos and add use the long polling to catch the status of the terminal In this PR we use the driver for Ingenico. Task: 1891152
Enhancements to existing features
Inventory managers can now adjust product quantities directly from stock quantity lists, reducing the need to create full inventory adjustments for simple corrections. Inventory adjustments were also redesigned with clearer line handling, status cues, account move access, and safeguards against duplicate stock quantity entries.
Original PR description
### Description of the feature this PR addresses: Improve the usability of the Inventory Adjustments and allow to easily correct a product quantity without going through an Inventory Adjustment. See commit messages for more information. *Task #1935921*
Odoo’s messaging and notification system was streamlined to reduce unnecessary processing, especially when posting messages with followers or attachments. This should improve performance and reliability across business apps that use chatter, email notifications, and user alerts.
Original PR description
Purpose of this merge is to clean and improve performances of post and notification mechanism contained in mail application. In this merge we provide * centralization of notification code inside…
Purpose of this merge is to clean and improve performances of post and
notification mechanism contained in mail application.
In this merge we provide
* centralization of notification code inside mail.thread instead of being
dispatched in mail.thread, mail.message and res.partner;
* simplification of call chain, removal of unnecessary methods;
* better propagation of messages value through the various calls in order
to use given value and avoid browse and cache miss adding queries;
* optimization of attachments management in post;
* cleaning of message_post now limited to records and simplified in its
management of parameter;
* cleaning and simplification of recipients grouping for email notification;
* cleaning of message_notify;
* various code cleaning and tweaking in order to reduce query count;
Performance tests indicate number of queries did fall, especially in
use cases involving management of followers and attachments. See sub
commits for more details. This merge is linked to task ID 1943901.Rescheduling behavior is now configured on each replenishment rule instead of through a broad company-wide setting. This makes it easier for users to understand and control when date changes should flow through sales, purchasing, inventory, and manufacturing operations.
Original PR description
Currently the fact that the changes in the expected dates are propagated or not is based on : - the value of the field propagate on the stock.rule - the general inventory setting setting use_propagation_minimum_delta That's not easy to understand for users and difficult to configure. The purpose of this task is to clarify this configuration (everything is configured at the same place + but we keep the flexibility by setting this config on the stock.rule) task-1913401
The portal wording for invoices and bills has been clarified so customers can better understand what they are viewing. This reduces confusion in the customer portal and makes financial documents easier to identify.
The IoT Box can now listen for device connections over the network, making it easier to integrate TCP/IP-connected hardware with Odoo. The update also improves how payment lines are displayed in Point of Sale, helping staff read payment details more clearly.
Original PR description
We use a new method to connect the box to a device in the network. We use the socket to listen a specific port in the box to connect device through the TCP/IP Task: 1891152 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The mail composer is easier and safer to use: users can no longer send empty chatter messages, and the writing area is larger. The update also improves how edited message content is checked, helping avoid unnecessary or incorrect content handling.
Original PR description
Description of the issue/feature this PR addresses: * Task: https://www.odoo.com/web#id=35897&view_type=form&model=project.task&action=327&menu_id=4720 * Pad: https://pad.odoo.com/p/r.84d2ef75380b69b778bb247f375de3ca 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
This update makes company selection more consistent across accounting and related workflows. It helps reduce confusion and errors when users work across multiple companies, especially in accounting, mail redirection, and company-specific suggestions.
Original PR description
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
The project overview has been simplified so users can more easily understand hours, tasks, and related sales information. It removes distracting zero-value lines, improves labels and tooltips, and adds visibility for timesheets linked to cancelled sales orders.
Original PR description
Description of the issue/feature this PR addresses: The Project Overview is quite obscur and difficult to understand for the user. The goal is to simplify what is displayed and to clarify the information provided. Current behavior before PR: Desired behavior after PR is merged: The project overview is easier to understand -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Lead generation rules can now be configured based on which website a visitor uses. This helps businesses running multiple websites tailor lead capture and qualification to each site’s audience.
Original PR description
The purpose of this commit is to allow to define lead generations rules based on the website visited. Task-ID: 1964025
Website themes can now reference default image records used by snippets, making it easier to replace or customize those images consistently. This helps theme designers deliver tailored website visuals with less manual work and fewer duplicated changes.
Original PR description
…customize the default ones easily Description of the issue/feature this PR addresses: * Task: https://www.odoo.com/web#id=40913&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 * Pad: https://pad.odoo.com/p/r.988d02bb3aaadcfdc7877bd8db614794 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
Users can now group information by integer fields, such as grouping vehicles by number of doors. This removes an unnecessary limitation and makes reporting and list analysis more flexible across web views.
Original PR description
No technical reason to forbid it Fixes odoo/odoo#31684 @ged-odoo any reason to forbid the integer? It can makes sense on some models (e.g. on fleet, group vehicles by number of doors) It seems there is also some other `GROUPABLE_TYPES` in different view types (like pivot). Do you want me to add it everywhere?
This update removes an unused internal variable that was triggering a code quality warning. The application behavior remains the same, but the codebase is cleaner and easier to maintain.
Original PR description
Description of the issue/feature this PR addresses: Fix lint error. Current behavior before PR: Works fine, but has lint error. Desired behavior after PR is merged: Works in the same way, but hasn't lint error. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Shop editors now get an Odoo confirmation dialog when changing product size or order, instead of a browser warning that reloads the whole page. Confirming saves the size or ordering change directly and refreshes only the product grid, helping prevent loss of other page edits.
Original PR description
Description of the issue/feature this PR addresses: Task-ID: https://www.odoo.com/web?#id=1960780&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 Current behavior before PR: - When the user changes the size / the sequence of a product, a strange browser a warning appears telling that the page is being left and if the user clicks ok the page reloads and all other editions are lost (top/bottom oe_structures, product names, etc). Desired behavior after PR is merged: - When the user changes the size / the sequence of a product, an Odoo modal appears warning the user that the sequence/size changes cannot be discarded. If the user clicks ok, only the product grid is reloaded and the sequence/size change has been saved in the database directly. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update improves the multi-company switcher so that moving to another company no longer hides the company the user came from. It also slightly improves the switcher layout and clarifies the company label on user forms, making multi-company work smoother and less confusing.
Original PR description
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
Enterprise apps were updated to work with the improved messaging and notification system from the community edition. This supports better message posting performance and keeps customer communications, activity logs, and email notifications working consistently across affected business workflows.
Original PR description
[IMP] various: adapt to new mail update in community, notably API changes Various changes have been made in community mail in order to improve performances and API of main post and notification methods. This commit updates enterprise modules accordingly. Notably * message_post and message_log API update; * groups management for notification emails; * after hook post method update; Related to task 1943901 Linked to PR #4410
Inventory adjustment workflows have been updated to better support the revised line-editing experience, including barcode-related screens. Related demo data and delivery/MRP tests were adjusted so supporting apps continue to work correctly with these changes.
Original PR description
Following the community commit #d69931534935c8f6904212cc6031193132a15fa5 - delivery_*: Makes some changes in tests - mrp_mps: Adapts demo data - stock_barcode: Adapts inventory adjustment view Task #1935921
This update renames internal company references to better match how users and the system already understand company information. It improves consistency across accounting-related features and reduces confusion for future maintenance, with little expected impact on day-to-day users.
Original PR description
The goal is to be coherent with the user property. Actually, company_id and company_ids on the environment are no fields. Calling env.company_id returns a browse record, not an id.
The project overview now includes a clearer section title for the timesheet-related table. This makes the overview easier to understand when reviewing project time, forecasts, and sales information.
Original PR description
In order to make the project overview more understandable, we introduces sections in the bottom table. project_timesheet_forecast_sale intends to add a new section, thus a new section tittle. This is done through view inheritance related task #1968121
Mobile status indicators now appear gray when they cannot be changed. This helps users quickly understand which statuses are informational only and avoids confusion when tapping unavailable options.
Original PR description
…t clickable so user can easily understand it's not changeable * Task: https://www.odoo.com/web?#id=35306&view_type=form&model=project.task&action=327&menu_id=4720 * Pad: https://pad.odoo.com/p/r.a14e26f2115039e6abf3b3c009be432e
Resolved issues and error corrections
This fixes a Point of Sale configuration issue where pricelist checks could fail while settings were being edited. The change helps ensure the system uses the real saved pricelist records, reducing errors or incorrect validation when updating POS settings.
Original PR description
Since ORM changes, the ids a many2many are new (virtual) ones in a onchange, so we have to point to origin which are the real records to check that the many2one is in as it has a real id. 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
This update adjusts manufacturing work order planning checks to allow a tiny one-second timing difference. It helps prevent false test failures without changing how users plan or run manufacturing operations.
Original PR description
This commit relax, by one second, two datetimes comparison regarding workorder planning to avoid any false positives 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
This fix prevents an error when users create a recurring calendar event with zero repetitions or a zero interval. Instead of showing a technical crash, the calendar now warns the user so they can correct the meeting setup before saving.
Original PR description
Description of the issue/feature this PR addresses: - Task - https://www.odoo.com/web#id=1930809&action=327&model=project.task&view_type=form&menu_id=4720 - Pad - https://pad.odoo.com/p/r.5babc87865194c859bf878c22233714c Current behavior before PR: - Getting the traceback while saving the recurrent event and number of repetations as 0 Desired behavior after PR is merged: - User will be warned if he tries to save the event with 0 as the number of repetations -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Updated the tooltip for the minimum stock quantity field so it accurately reflects how reordering rules work. This reduces confusion for users setting inventory thresholds, especially when stock equals the minimum quantity.
Original PR description
Reported by a learning partner, apparently the field description didn't match the behavior. I guess the behavior is ok but only the field help should be reviewed. I tested this on runbot and it indeed triggers the reordering point if equals to the min stock rule 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
Documentation and clarification updates
This pull request records the signed corporate licence agreement for IvyWeb (Pty. Ltd.). It is an administrative legal update that helps confirm contribution rights and does not change Odoo product features or user workflows.
Original PR description
This is the corporate licence agreement for IvyWeb (Pty. Ltd.) 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