Daily updates from Odoo
Friday, December 6, 2019
7 changes · master
New functionality added to Odoo
Website editors can now add charts directly to pages using a new Chart snippet. This makes it easier to present business data visually with common chart formats such as bar, line, pie, doughnut, and radar charts.
Original PR description
Introducing a new snippet called Chart. This snippet uses the lib https://www.chartjs.org/ 6 types of graph are possible: Bar vertical Bar horizontal Line Pie Doughnut Radar -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Website editors can now add a customizable countdown block to pages for launches, promotions, and events. The block supports different display styles and end-of-countdown actions such as showing a message or redirecting visitors.
Original PR description
This commit introduces a new snippet: Countdown. The countdown snippet is composed of 4 circle countdown, one for every time unit: seconds, minutes, hours and days. On countdown ends, 3 possible…
This commit introduces a new snippet: Countdown. The countdown snippet is composed of 4 circle countdown, one for every time unit: seconds, minutes, hours and days. On countdown ends, 3 possible actions: 1. Nothing 2. Show message: show a message once the countdown ends. The message will be displayed bellow the countdown (stopped on 0). The message can be edited through the website builder. 3. Redirect: redirect the user to the chosen URL. If the user is on the page at the exact moment the countdown reach 0, the user will be redirected automatically. If the user lands on the page after the countdown has reached 0, there will be no redirection and the link will be shown bellow the countdown (stopped on 0). The countdown layout can be customized in multiple ways: 1. By choosing to hide some time units. For instance, seconds can be hidden or only days shown. 2. By changing its design (plain background, thin circle etc). 3. By changing its size between small/medium/large. task-2093081
Enhancements to existing features
Surveys can now use a specific question to collect or update the participant's email address, with existing invitation emails prefilled to reduce retyping. The change also corrects a user-facing typo in survey validation messaging and improves related survey behavior.
Changing a product's standard cost now automatically updates the related inventory valuation records in most costing setups. This removes the need for a separate manual wizard, making product cost updates more direct and reducing the risk of missed valuation adjustments.
Original PR description
Overwrite the method ``write`` of the model ``product.product``. When we write on ``standard_price``, if - the context key ``disable_auto_svl`` is not set - the ``cost_method`` is not "fifo" We automatically compute ``stock.valuation.layer`` (before we needed to manually call ``_change_standard_price``) Task #2031422
The website editor’s left panel is now easier to use, with cleaner input layout and support for confirming entries with Enter. These changes make editing website snippets smoother and more predictable for content editors.
Resolved issues and error corrections
Maintenance requests now show a more focused list of equipment when both an employee and department are selected. This avoids offering unrelated equipment that is not assigned to any employee, making the request process clearer and less error-prone.
Original PR description
If a department & an employee are set on a maintenance request, we select an equipment linked to the department *or* the employee **or no employee at all** (regardless of the department). Removed the last clause. It does remove the ability to select an employee and then select an equipment linked to the employee or no employee at all, but I think it makes somewhat more sense than being able to select any equipment not linked to an employee when setting both employee and department. ping @oma-odoo Also technically we might want a helper to apply a field's domain on a record somehow: onchange_department_or_employee_id has to pretty much duplicate the domain do do its thing, and it's likely bugged given the domain it defines (see above).
Code cleanup and technical improvements
Stock validation wizards now better support handling several transfers at once by showing which transfers may be affected and letting users choose the relevant ones. This makes bulk warehouse operations clearer and reduces the risk of applying immediate transfer or backorder decisions to the wrong records.