Tuesday, August 13, 2024
13 changes · master
New functionality added to Odoo
Sales teams can now create spreadsheet-based calculators from quotation templates and use them to calculate prices, quantities, and other quotation line values before saving them back to the quote. This helps businesses support tailored pricing workflows, such as delivery or assembly cost calculations, while keeping each calculator adaptable to specific use cases.
Original PR description
Purpose ------- In several businesses, it might be cumbersome to properly calculate a quote (define an appropriate quantity, price, etc). The goal of this task is to allow user to easily access a…
Purpose
-------
In several businesses, it might be cumbersome to properly calculate a
quote (define an appropriate quantity, price, etc). The goal of this task is
to allow user to easily access a spreadsheet (blank or preconfigured) to
do those calculations.
Specification
-------------
From a quotation template, you can create a spreadsheet calculator template.
At creation, a list of sale order lines is inserted with a global
filter allowing to filter the lines according to their quotation.
You can add "Field sync" rules on any cell (right click on a cell) to update
one field of one order line in the list (readonly fields are excluded).
Then, when you create a quotation from the quotation template, you can open
the spreadsheet calculator. It creates a copy of the spreadsheet (allowing
you to play around values etc.) and adds a global filter to filter the
sale order lines from the quotation.
From this spreadsheet, by clicking on "Save in SO00XX", it reads the values
in cells with a "Field sync" rules and updates the quotation lines with
those values.
This allows to create very specific flows with any arbitraty computations
to compute any values in sale order lines, based on any data, from the
spreadsheet itself or from the database by inserting other data sources
in the spreadsheet template, for example, employee planning, products,
stock, etc.
This great power and flexibility comes with limitation about how generic
it can be. It's expected to hardcode product names or ids in formulas in
order to match order lines. Hardcoded names are of course not robust to
different languages, ids are robust to that but are less friendly and are
not cross-db compatible. Each spreadsheet calculator template must be
built specifically for every use case and every database.
Task: 3761590Point of Sale can now receive and manage online restaurant orders through UrbanPiper, starting with Zomato and Swiggy. This helps restaurants centralize third-party delivery orders in Odoo, reducing manual entry and improving order handling.
Original PR description
*=pos_restaurant_urban_piper In this commit : ==== - Enabled integration of online orders from various providers with the Point of Sale. - Currently, Zomato and Swiggy are implemented as the first providers. task- 4040542 Co-authored-by: paso-odoo <paso@odoo.com> Co-authored-by: meji-odoo <meji@odoo.com> Related: https://github.com/odoo/odoo/pull/173300 Related: https://github.com/odoo/upgrade/pull/6327
Introduces a new sales commission app to create commission plans and calculate commissions for salespeople and managers. The feature supports commissions based on sales, invoices, margins, and subscription growth, helping businesses automate and track incentive payouts more accurately.
Enhancements to existing features
Field service-related pages now use clearer, more human-readable web addresses. This improves the customer and employee experience by making links easier to understand, share, and recognize across reports, sales, and stock workflows.
Original PR description
*= industry_fsm_report, industry_fsm_sale, industry_fsm_stock This commit modifies existing URLs to the new format so that the URL's become more human readable. Task-3820230
Several HR-related apps now use cleaner, more human-readable web links. This makes shared links easier to understand and helps create a more consistent navigation experience across expenses, payroll, recruitment signing, and referrals.
Original PR description
*= {expense_extract, payroll, recruitment_sign,
referral}
This commit modifies existing URLs to the new format
so that the URL's become more human readable.
Task-3820230The 1099 box field is repositioned on partner records so it appears below the payment method field. This keeps related payment and tax reporting information grouped together, making the form easier to read and complete.
Original PR description
In this commit:https://github.com/odoo/odoo/pull/174537/commits/09d2b29e14425c1e333bbe4ae6e5caa2e6361f9f We moved the field property_payment_method_id into the account module and we want it to be below the payment terms in the res_partner view. This commit will change the xpath so that the field box_1099_id is now below the payment method field. task: 4016652
Planning warnings for single-day time off are now shorter and easier to read. Instead of repeating the same date twice, the message shows the leave date once and includes custom hours only when relevant.
Original PR description
Before this commit even if there was a single day leave the warning would read as "Person is on leave from 12/7/21 (fromTime) to 12/7/21 (toTime)". After this commit if leave is of single day type then the warning would be read as "Person is on leave on 12/7/21 (fromTime to toTime)". If Time is not custom hours the warning would be read as "Person is on leave on 12/7/21" Here fromTime and toTime are subject to availabilty. task-3887999
Public knowledge article lists are now easier to use: visitors can click anywhere on an article row instead of only the title. Rows also highlight on hover, making clickable articles clearer and aligning the public experience with the internal view.
Original PR description
Currently, there are two layout issues with the article public view: 1. The article link hitbox of the article public view does not span over the entire row. To open an article, the user has to click on the article title. To improve the UX experience, we will set the article link hitbox to the entire row as we do in the backend view. 2. When the user hovers an article link, we do not give a clear indication that the element is clickable. To improve that, we will highlight the rows on hovering as we do in the backend view. Those two changes will improve the UX experience and the consistency between the sidebar loaded in the public view and the sidebar loaded in the backend view. task-4011436
Mobile users can now access message actions through a bottom context menu, making common communication tasks easier to find and use on small screens. This improves the experience for teams managing conversations from phones, including WhatsApp-related messages.
Original PR description
Task-4102385 https://github.com/odoo/odoo/pull/175776
Payment follow-up email templates no longer include the customer's general partner address by default. This keeps reminders focused on the designated follow-up contact, reducing confusion and helping messages go to the right recipient.
Original PR description
Since https://github.com/odoo/enterprise/pull/61861, we include the template partners and email addresses, but Payment followup typically uses the followup contact's email address, and doesn't need partner's address in the template Found due to OPW-3988791
Resolved issues and error corrections
This change addresses a point of sale issue where orders could receive duplicate numbers. Preventing duplicate order numbers helps keep sales records clear and reduces reconciliation problems for staff.
Original PR description
- add async...await when necessary
Miscellaneous changes
Where possible, we make the eTIMS-specific fields and buttons invisible unless the company has Kenya as fiscal country. Exceptions to this are: - the buttons on partner and user form views. We don't have a way of showing them only if the currently selected company is Kenyan. However, they are already visible only in debug mode, so this isn't too much of a problem. - the 'Custom Imports' menuitem - we don't have a way of making it conditionally visible. Forward-Port-Of: odoo/enterprise#6690
Original PR description
Where possible, we make the eTIMS-specific fields and buttons invisible unless the company has Kenya as fiscal country. Exceptions to this are: - the buttons on partner and user form views. We don't have a way of showing them only if the currently selected company is Kenyan. However, they are already visible only in debug mode, so this isn't too much of a problem. - the 'Custom Imports' menuitem - we don't have a way of making it conditionally visible. Forward-Port-Of: odoo/enterprise#66905
Issue ----- Trial report assumes the `comparison` key exists when generating report options. However, that won't be the case if `filter_period_comparison` (Period Comparison option) is false. Steps ----- - Go to Accounting -> Configuration -> Accounting Reports. - Choose Trial Balance then go to Options and disable 'Period Comparison'. - Now generate a trial balance report by going to Reporting -> Audio Reports -> Trial Balance. - A `KeyError` is thrown. opw-3991886 Forward-Po
Original PR description
Issue ----- Trial report assumes the `comparison` key exists when generating report options. However, that won't be the case if `filter_period_comparison` (Period Comparison option) is false. Steps ----- - Go to Accounting -> Configuration -> Accounting Reports. - Choose Trial Balance then go to Options and disable 'Period Comparison'. - Now generate a trial balance report by going to Reporting -> Audio Reports -> Trial Balance. - A `KeyError` is thrown. opw-3991886 Forward-Port-Of: odoo/enterprise#68000 Forward-Port-Of: odoo/enterprise#66049