Daily updates from Odoo
Navigate
Branch
Thursday, July 18, 2019
13 changes
New functionality added to Odoo
SMS features are improved across contacts, calendar, and CRM, with better sending behavior, clearer failure messages, and automatic SMS support from server actions. This helps teams communicate with customers more reliably while keeping useful records on related business documents.
Original PR description
PURPOSE Provide fixes to SMS behavior, notably in composer. Better integration in various applications: contacts, calendar, crm. Allow to automatically send SMS from server actions. SPECIFICATIONS See sub commits for more details. Linked to task 1925950 and 1935280
Enhancements to existing features
This update adds clearer structure and labels to accounting form views, making them easier for implementers to customize reliably. It does not change day-to-day accounting workflows, but helps reduce effort and risk when tailoring screens for specific business needs.
Original PR description
Description of the issue/feature this PR addresses: Sheet and element names Current behavior before PR: There is no `<sheet>` on the form view and most elements have no name to xpath on. Desired behavior after PR is merged: There is a `<sheet>` on the form view and the most important elements have a name to xpath on. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Stripe payments now use newer checkout and card setup flows to support Strong Customer Authentication required by PSD2. This helps keep online card payments compliant and improves reliability for customers paying through Stripe, with redirection payments recommended as the best-supported flow.
Original PR description
With the PSD2 directive coming into effect on September 14th, it was time to switch our Stripe integration to use newer APIs that support Strong Customer Authentication (SCA for short). This meant…
With the PSD2 directive coming into effect on September 14th, it was time to switch our Stripe integration to use newer APIs that support Strong Customer Authentication (SCA for short). This meant switching from the old stripe.js implementation for 'redirection' flow to the Stripe Checkout API and from the Charge API to the newer SetupIntent API for s2s flows. This feature branch introduce these changes as well as some slight changes in the payment module (mainly functional improvement that were noticed when developing this, nothing major and no change in the flow/model of the basic payment models). Note that the way our checkout flow is built for s2s transactions prevents us from using the PaymentIntent API (which would be a better fit that the SetupIntent in some cases) - to use that API, we would need the payment transaction to be created before the token, which is not the case in our current flows. This will probably be changed in a future task with a more flexible checkout flow. In the mean time, the downside of using SetupIntent instead of PaymentIntent means that from the bank's point of view, the authorization of the card and the payment are 2 different requests - this could lead to a higher rejection rate in SCA flows and possibly to payments that stay 'pending'. There is no way to know for sure before PSD2 goes into full effect though, and this implementation should normally suffice.I would advise using the 'redirection' flow most of the time though, since it is clearly the best fit between Odoo and the Stripe APIs at the moment. Task 1986267
The IoT system now stops checking a device once no one is actively listening to it. This reduces unnecessary communication with the IoT Box and helps avoid wasted network and device resources.
Original PR description
When all listeners had been removed for a device, we kept sending requests to the IoT Box. So we stop the longpolling when there's no listener on the device.
The employee “My Profile” view has been reorganized to make personal and HR information easier to access and less error-prone. This also fixes issues that could prevent employees from viewing their own appraisal-related profile information and corrects a dashboard comparison problem.
The Gantt view now shows the exact progress percentage inside the item popover when a progress field is used. This makes it easier for users to understand completion status without relying only on the striped visual indicator.
Original PR description
* Task: https://www.odoo.com/web#id=1939533&model=project.task&view_type=form&menu_id=4720 * Pad: https://pad.odoo.com/p/r.27e4044ba80dd75b322de35d2e736e16
Resolved issues and error corrections
This fixes a display issue in the Lunch app where the pager could overflow when showing amounts. Users should see cleaner, more reliable navigation in lunch cash movement views, especially when amounts take up more space.
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
Odoo Studio now creates related fields with the same storage behavior as the field they reference. This prevents unexpected data storage and makes field setup more predictable for users configuring apps in Studio.
Original PR description
Task: https://www.odoo.com/web#id=1985710&action=327&model=project.task&view_type=form&menu_id=4720 pad: https://pad.odoo.com/p/r.ca4debca71cbd375ce888e00caa286f8 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 grid view now shows its empty-state help message using the same rendering approach as the rest of the grid. This prevents display issues caused by mixing incompatible rendering methods and improves reliability for users viewing empty grids.
Original PR description
The grid view is the only view to use snabbdom in order to render the view, the code used in order to support the noContentHelp was written using jquery which is incompatible with snabbdom virtual dom. This commit simply converts the noContentHelp rendering to snabbdom.
Features or functions removed from Odoo
This change removes an old web module loading mechanism that had been broken since earlier compatibility code was removed. Because it was unused and already non-functional, the impact is expected to be minimal while reducing outdated code.
Original PR description
`window.openerp` being undefined, the method `on_modules_loaded` throws an error when reaching its purpose (loading additional modules)... The commit 905e019 removed the compatibility layer for Odoo v8 (compatibility.js) which contained the `window.openerp` declaration. Being broken for that long without consequences, this feature proved to not be useful anymore. We then remove it.
The Mail app no longer shows the custom filter for messages because it was not working properly. This prevents users from relying on a broken search option and makes the filter menu clearer.
Original PR description
Description of the issue/feature this PR addresses: <b> Task:</b> https://www.odoo.com/web?#id=1939953&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 <b> Pad:</b> https://pad.odoo.com/p/r.9eaf33c4bcb04ddbee0af197d5403e1d 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 no longer supports the older model constraint mechanism and now only warns when it is still present. This helps teams move to the newer validation approach while reducing maintenance of outdated framework behavior.
Original PR description
Simply leave a warning in case a model uses a non-empty attribute `_constraints`.
Code cleanup and technical improvements
This update reorganizes how Odoo's page control panel is built and managed, making the interface framework more consistent across apps. It should help support future improvements to navigation, actions, and view controls while keeping current business workflows largely unchanged.
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