Tuesday, September 3, 2024
17 changes
9 changes
New functionality added to Odoo
A new payroll wizard helps calculate Tax Deducted at Source (TDS) from the provided employee and contract details. This makes monthly payroll processing easier and more transparent by showing the tax calculation before applying it to contracts.
Original PR description
In this PR, a new wizard is created to calculate the TDS based on the given parameters and apply it to the monthly contracts Task - 3910821
Enhancements to existing features
Web Studio now notifies selected users when a record action is approved or refused, rather than when the approval request is first created. This makes notifications more timely and relevant, so stakeholders are alerted when a decision has actually been made.
Original PR description
We refactor the way the field users_to_notify is used. Now, the users to notify (if any) are notified when an action/method on a record is approved/refused. Previously they were notified when a request was created. They are not longer notified at that moment. Task ID: 4122972
8 changes
Enhancements to existing features
Users can now customize which time period options (month, quarter, or both) appear in date filters within spreadsheets. This improvement gives teams more flexibility in how they filter and view data, allowing them to focus on the specific time granularities that matter most for their analysis.
Original PR description
This commit adds the possibility to disable the month or quarter granularity (or both) for fixedPeriod date filters. Task: [3887844](https://www.odoo.com/web#id=3887844&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form)
The timesheet analysis report now has clearer list and form views with more relevant fields for reviewing time entries. This makes it easier for teams using timesheets and helpdesk timesheets to inspect and analyze reported work without seeing an overly technical default layout.
Original PR description
## [IMP] {helpdesk_}timesheet{_grid}: make list view for timesheets analysis report
This commit overrides the list view of timesheets analysis report to add fields that could be interested to analysis.
## [IMP] {helpdesk_}timesheet{_grid}: add form view for timesheet analys…
…is report
Before this commit, the form view was the default one that is the one
displaying all the fields defined inside the report.
This commit defined a form view to have the same render than one defined
for timesheets.
task-4053021Users returning to a spreadsheet from a drill-down records view now keep their filters, selected cells, scroll position, and loaded data. This avoids frustrating resets and delays, especially when working with pivot tables and shared spreadsheets.
Manufacturing users can now choose which existing operation should come before a newly added shop floor operation. This makes it easier to keep production steps in the right order when plans change during execution.
Original PR description
This commit permits to select a previous operation when the user adds a new operation from the shop floor. task-3848797
Published Knowledge articles now provide social platforms with article-specific preview information instead of generic website defaults. This improves how shared links appear on services like Facebook and WhatsApp, making them clearer and more appealing to open.
Original PR description
When a user publishes an article and shares the access link with a friend on Facebook, WhatsApp, or other social media platforms, most platforms fetch the website's Open Graph metadata to display a preview of the link. For the website's knowledge module, we have not defined any Open Graph metadata. The system currently uses default values loaded from the `ir.ui.view` model and the preview does not give any information about the article. To enhance the link preview on the external platforms and enhance the SEO of the articles, we will manually set the Open Graph metadata using the information about the article. This should make people more inclined to click on the link. task-4001922
Rental and subscription pricing tables now appear inside the product details accordion when that layout is enabled. This keeps product pages cleaner and more consistent while preserving the pricing information shoppers need.
Original PR description
Follow the changes made in [community](https://github.com/odoo/odoo/pull/173823), this PR shows the rental and subscription pricing table inside the product details accordion if the accordion is enabled by the user. task-3987039
Companies can now distinguish the country used for tax mapping from the delivery country used for automatic fiscal position detection. This helps businesses exporting from warehouses outside their fiscal country apply the right taxes without rebuilding their fiscal position setup.
Original PR description
Description of the issue this commit addresses: Some companies export goods from warehouses outside of their fiscal country. It is currently not possible to use the "Detect Automatically" feature of the fiscal positions for them as the country they need to set to get the right tax mapping is not the country that needs to be detected for the auto apply. --- Desired behavior after this commit is merged: This commit allows users upon the installation of the new module to split the country of the tax mapping and the country of the auto apply. They are named "Fiscal Country" and "Delivery Country" and it grants companies the ability to have a working flow without starting from scratch if they need such a behavior. --- Community PR: https://github.com/odoo/odoo/pull/177746 task-4066525
Batch payslip generation now only includes employees with an active contract matching the selected salary structure type. This helps payroll teams avoid creating incorrect payslips and reduces manual cleanup.
Original PR description
This PR enhances the batch payslip generation process. Previously, payslips were generated for all employees, regardless of their salary structure type. Now, payslips will only be generated for employees with a running contract based on the same salary structure type. task-4002203
The signature request feature has been improved to prevent users from accidentally creating templates on-the-fly through the request wizard. Users must now select from existing templates, which reduces errors and ensures better template management. This change makes the signature workflow more controlled and reliable.
Original PR description
Before this commit, Using the "request signature" option allowed users to create templates on the fly, which could lead to errors. In this commit, the Creation of templates on the fly from the wizard is no longer allowed. task-4069128
Resolved issues and error corrections
Fixed an issue where the document preview window would unexpectedly close when users tried to add tags to a document. This improves the user experience by allowing users to add tags without losing their place or having to reopen the document preview.
Original PR description
Current behaviour: --- When you open a document, and you want to add a tag, the preview closes. Steps to reproduce: --- 1. Go to Documents 2. Open a document 3. Add a tag 4. The preview closes Cause of the issue: --- In updateRecordTagId from documents_search_model.js Update trigger > load > documents-close-preview trigger opw-3879288
This fix ensures that only service products can be used when creating sales order lines directly from helpdesk tickets. Previously, non-service products could be incorrectly added, which could cause issues with timesheet tracking. Now the system properly validates that only service products are allowed and shows a clear error message if someone tries to use a non-service product.
Original PR description
### Before this PR: ->If we create a product that isn't a service > open the helpdesk ticket form view -> type the name of the product you created from the SOL field and click create -> a new SOL is generated for this product and is successfully set on the ticket ### After this PR: A new SOL is generated only for service products, it should only be allowed for services products, it will throw validation error that isn't service task-3972359
This fix resolves a problem where marketing campaign activities were not displaying correctly when campaigns contained more than 40 activities. The system was splitting activities across multiple pages, but the hierarchical organization of parent and child activities only worked when all activities were loaded together. By removing the page limit, all activities now display properly regardless of quantity.
Original PR description
Current behaviour: --- When you create a campaign, if you add more activity (56) than the default pager limit (40) The next pager page will be empty (instead of showing the remaining 16 activities)…
Current behaviour: --- When you create a campaign, if you add more activity (56) than the default pager limit (40) The next pager page will be empty (instead of showing the remaining 16 activities) Steps to reproduce: --- 1. Go to Marketing Automation 2. Create a campaign 3. Create more than 40 activities 4. Alternate parents/child when creating 5. The pager will appear, with at least 2 pages 6. Go to the second page 7. Nothing displayed NB: When inputting the number of activities in the pager, everything is rendered fine. Cause of the issue: --- To be displayed, the activities are hierarchised, by finding child and parents (`_getSortedRecordsByHierarchy`) However this system works great when all the records are given. Using a pager, some records are not used in the hierarchy, causing the outputted list to be incomplete. (ie if an activity A is in the first 40 and the child in the last 16, it will not be rendered correctly) Fix: --- Disabling the pager by setting a higher limit opw-4006610 Forward-Port-Of: odoo/enterprise#67979
This update fixes how Odoo calculates line discounts when importing Chilean invoices through email. Previously, Odoo would calculate discounts incorrectly, causing amounts to not match official records. The fix prioritizes the actual discount amount from the invoice file and now properly handles surcharges on line items, ensuring accurate financial records for Chilean businesses.
Original PR description
Before this PR: There are two problems: first, if you have a line discount like this: <img width="350" alt="Captura de pantalla 2024-03-27 a la(s) 09 48 55"…
Before this PR: There are two problems: first, if you have a line discount like this: <img width="350" alt="Captura de pantalla 2024-03-27 a la(s) 09 48 55" src="https://github.com/odoo/enterprise/assets/382893/7564b133-c6e9-4bab-97f3-d8a0a2634fe5"> The calculation made by Odoo is: 319319 * 21.35 / 100 = 68175 which does not match the amount placed in "DescuentoMonto". In this case, it is 68173 (difference of 2 CLP) which is why it is better to prioritize the discount amount instead of the percentage in the XML, which is already rounding, leading to a problem. The second: if you have a surcharge in the line, like this: <img width="354" alt="Captura de pantalla 2024-03-27 a la(s) 09 52 40" src="https://github.com/odoo/enterprise/assets/382893/5a7ffa96-a2d9-498f-acf3-7003c95aa789"> Odoo ignores it. After the PR: The first issue is fixed by giving priority to the "DescuentoMonto" tag. The second issue is added as an improvement. Since Odoo does not have a column to show the surcharge separated in the line, we are taking advantage of the feature that supports negative discounts in the line to put that surcharge as negative. Forward-Port-Of: odoo/enterprise#65842 Forward-Port-Of: odoo/enterprise#59532
Fixed an issue where the Spanish VAT Registro de IVA export button was appearing as the main action for all companies worldwide, regardless of their country. The button now only displays for Spanish companies, preventing confusion for users in other countries.
Original PR description
Before this commit, as soon as this module is installed, the button to generate the Libros Registro de IVA was the main button for all the companies. Instead of having a new handler, just add the code in the default handler, and manage the buttons based on the country of the current company.
Customers were receiving subscription renewal invoices twice—once with the standard template and again with the subscription-specific template. This fix ensures invoices are sent only once using the appropriate subscription template, improving the customer experience and reducing confusion.
Original PR description
When validating a payment for a subscription and the sale's setting `sale.automatic_invoice` is enabled, the invoice is send twice to the customer on subscription renewal; first with the normal…
When validating a payment for a subscription and the sale's setting `sale.automatic_invoice` is enabled, the invoice is send twice to the customer on subscription renewal; first with the normal template then a second time with the subscription specific template. To reproduce: - As Administrator: - Enable the "Automatic Invoice" option in the setting - Install/enable the `demo` payment provider and method - Log-in as `portal` user - Go the /shop and add the `Office Cleaning Service (SUB)` to you cart - Pay your order using the `Demo` payment method => The invoice is send once - Go to your subscription (/my/subscriptions) - Click on your new subscription - Scroll to the `Anticipate payment` section and pay for it (again choose the `Demo` payment method) - You get back the the subscription page, click on the last invoice (2nd invoice you created) => Scroll to the history section and see that the invoice is sent twice This commit ensure we're only sending invoice with the subscription specific template on renewal. OPW-3900040