Friday, January 22, 2021
27 changes · master
New functionality added to Odoo
Adds a new chatbot capability to Live Chat, allowing businesses to create scripted automated conversations with predefined answers and input steps. This can help teams respond faster to website visitors and route common questions before a human operator joins.
Original PR description
Add a chatbot addon to livechat
Businesses can now export invoices using a generic UBL format, making electronic document exchange easier when no country-specific profile is required. The change also prepares the existing UBL framework for additional profiles and updates Belgian e-invoicing integration to use the shared base more flexibly.
Original PR description
TASK ID: 2361217 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
Enhancements to existing features
Inventory processing has been optimized so large batches of stock transfers can be validated more efficiently. This helps businesses with high warehouse volumes reduce delays when confirming completed operations and improves the tools used to test stock performance.
Resolved issues and error corrections
This fixes how Google and Microsoft calendar sync settings are handled for user records. It helps prevent incorrect sync behavior by relying on Odoo's standard user-field handling mechanism.
Original PR description
Fix wrong calculation
Miscellaneous changes
Set up a DEMO product with - warning message on sale - variant - Order Grid Entry as Sales Variant Selection Create SO, configure this product Warning message doesn't display opw-2442352 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 Forward-Port-Of: odoo/odoo#64867
Original PR description
Set up a DEMO product with - warning message on sale - variant - Order Grid Entry as Sales Variant Selection Create SO, configure this product Warning message doesn't display opw-2442352 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 Forward-Port-Of: odoo/odoo#64867
This update adds richer automatic demo data generation for accounting areas such as journals, invoices, payments, bank statements, and reconciliation rules. It helps teams create more realistic test or demonstration databases faster, while also improving related company, currency, and performance handling.
Original PR description
Task [2230635](https://www.odoo.com/web#id=2230635&action=333&active_id=967&model=project.task&view_type=form&cids=1&menu_id=4720) Add _populate implementation for: * Bank Statements * Journals * Journal Entries / Invoices * Payments * Reconcile Models Load a chart of account for the first 3 companies, and load data only for companies with a CoA installed. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The accounting screens now hide the Electronic Invoicing field when no electronic invoicing service is needed. This reduces clutter for users and helps keep invoice and payment forms focused on relevant information.
Original PR description
…ove view if no EDI require web-service TASK ID: 2439258 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
- Create a promotion of discount 10% with coupon (A) - Create a promotion of fixed discount (50$) with coupon (B) - Create a sale order of 50$, apply A and then B Order will have a negative total. This is due to the check done on the order amount, which needs to be checked without the current program, to allow correct stacking of promotions opw-2410666 Forward-Port-Of: odoo/odoo#64572 Forward-Port-Of: odoo/odoo#63106
Original PR description
- Create a promotion of discount 10% with coupon (A) - Create a promotion of fixed discount (50$) with coupon (B) - Create a sale order of 50$, apply A and then B Order will have a negative total. This is due to the check done on the order amount, which needs to be checked without the current program, to allow correct stacking of promotions opw-2410666 Forward-Port-Of: odoo/odoo#64572 Forward-Port-Of: odoo/odoo#63106
Before this commit: -when moving a snippet using the drag and drop button, two drop zones instead of one was added at the initial location of the dragged snippet. -when moving a snippet using the drag and drop button, no drop zone was added at the initial location of the dragged snippet if the snippet was alone in its parent. For example, the left jumbotron in the banner snippet. -the drop zones handled by the "children rules" were never vertical when it was necessary. This com
Original PR description
Before this commit: -when moving a snippet using the drag and drop button, two drop zones instead of one was added at the initial location of the dragged snippet. -when moving a snippet using the drag and drop button, no drop zone was added at the initial location of the dragged snippet if the snippet was alone in its parent. For example, the left jumbotron in the banner snippet. -the drop zones handled by the "children rules" were never vertical when it was necessary. This commit also refactors the code to avoid some duplicated lines. task-2312878 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 Forward-Port-Of: odoo/odoo#64838 Forward-Port-Of: odoo/odoo#64546
1. Go to Settings > Accounting and set a Check layout 2. Go to Accounting > Vendors > Payments 3. Create 2 payments to Vendors, and Confirm (but do not print). - Payment Type: Send money - Partner Type: Vendor - fill in any Amount - Payment Method: Checks 4. Go to the accounting dashboard, click on "2 checks to print" 5. Select both payments and print the checks from the Actions menu 6. Refresh the page. Both payments still show up with the "Checks to print" search filter
Original PR description
1. Go to Settings > Accounting and set a Check layout 2. Go to Accounting > Vendors > Payments 3. Create 2 payments to Vendors, and Confirm (but do not print). - Payment Type: Send money - Partner Type: Vendor - fill in any Amount - Payment Method: Checks 4. Go to the accounting dashboard, click on "2 checks to print" 5. Select both payments and print the checks from the Actions menu 6. Refresh the page. Both payments still show up with the "Checks to print" search filter enabled. They also shows up in Accounting dashboard as checks to print opw-2427523 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 Forward-Port-Of: odoo/odoo#64840
Like any snippet creating dynamic elements on page load, we need to use a special class on those elements to mitigate the undo/redo system's imperfections. Forward-Port-Of: odoo/odoo#64876
Original PR description
Like any snippet creating dynamic elements on page load, we need to use a special class on those elements to mitigate the undo/redo system's imperfections. Forward-Port-Of: odoo/odoo#64876
task-2347640 Forward-Port-Of: odoo/odoo#63313
Original PR description
task-2347640 Forward-Port-Of: odoo/odoo#63313
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 Forward-Port-Of: odoo/odoo#64863
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 Forward-Port-Of: odoo/odoo#64863
Forward-Port-Of: odoo/odoo#64901
Original PR description
Forward-Port-Of: odoo/odoo#64901
This commit fixes a nondeterministic issue during the rainbowman tour. We make sure that the record is properly created and the kanban reloaded before moving on to the next step, ensuring that the tour completes without race conditions. Task-2426257 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 Forward-Port-Of:
Original PR description
This commit fixes a nondeterministic issue during the rainbowman tour. We make sure that the record is properly created and the kanban reloaded before moving on to the next step, ensuring that the tour completes without race conditions. Task-2426257 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 Forward-Port-Of: odoo/odoo#64845
from #64626 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 Forward-Port-Of: odoo/odoo#64924
Original PR description
from #64626 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 Forward-Port-Of: odoo/odoo#64924
Improve the performance of the replenishment report (`_get_orderpoint_action`). Also indirectly improve performance of `_bom_find` and the forecasted inventory (`report.stock.quantity`) Forward-Port-Of: odoo/odoo#64918 Forward-Port-Of: odoo/odoo#63922
Original PR description
Improve the performance of the replenishment report (`_get_orderpoint_action`). Also indirectly improve performance of `_bom_find` and the forecasted inventory (`report.stock.quantity`) Forward-Port-Of: odoo/odoo#64918 Forward-Port-Of: odoo/odoo#63922
Before this commit, on pivot view when a user adds some groupBy the dropdown menu remains always open. This commit restore the same behaviour like on desktop. Steps to reproduce: * Open an app with a Pivot view * Select the Pivot view * Add one "groupBy" * The dropdown remains open => BUG Task ID: 2439742 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#64613
Original PR description
Before this commit, on pivot view when a user adds some groupBy the dropdown menu remains always open. This commit restore the same behaviour like on desktop. Steps to reproduce: * Open an app with a Pivot view * Select the Pivot view * Add one "groupBy" * The dropdown remains open => BUG Task ID: 2439742 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#64613
This mobile specific code does not work correctly because `if channel in channel_previews` always returns false due to the dict having channel ids as key and not channels. A fix could be to look for id instead of record in the dict, but at the same time this is dead code, there is no need for mobile specific channel info. task-2412157 Forward-Port-Of: odoo/odoo#64722
Original PR description
This mobile specific code does not work correctly because `if channel in channel_previews` always returns false due to the dict having channel ids as key and not channels. A fix could be to look for id instead of record in the dict, but at the same time this is dead code, there is no need for mobile specific channel info. task-2412157 Forward-Port-Of: odoo/odoo#64722
…processing EDI - On account_edi_document, lock the documents successively instead of all at once. - Lock account_move that should be cancelled. Before, cancelling the invoice after cancelling it on the web-service could fail. - Lock ir_attachment that might be unlinked. Before, attachments that weren't attached to any model could become unreachable but still present in the database when an invoice was cancelled or a new attachment was produced. Description of the issue/feature this PR a
Original PR description
…processing EDI - On account_edi_document, lock the documents successively instead of all at once. - Lock account_move that should be cancelled. Before, cancelling the invoice after cancelling it on the web-service could fail. - Lock ir_attachment that might be unlinked. Before, attachments that weren't attached to any model could become unreachable but still present in the database when an invoice was cancelled or a new attachment was produced. 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 Forward-Port-Of: odoo/odoo#64870
When you are selling a kit in point_of_sale, the associated picking is not validated. Because no quantity done is set on its component move lines. This has been caused by modifications made in following commit: https://github.com/odoo/odoo/commit/f9dd1d88d0d24914028464cc12b69ff0878346f8 OPW-2426992 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 guide
Original PR description
When you are selling a kit in point_of_sale, the associated picking is not validated. Because no quantity done is set on its component move lines. This has been caused by modifications made in following commit: https://github.com/odoo/odoo/commit/f9dd1d88d0d24914028464cc12b69ff0878346f8 OPW-2426992 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 Forward-Port-Of: odoo/odoo#64930
During 12.0->13.0 migration, some use cases are solved using notes. Those notes contain values for restricted fields. Instead of losing data, we keep the values and don't copy them to avoid issues in use cases like "create credit note from invoice". Forward-Port-Of: odoo/odoo#64055
Original PR description
During 12.0->13.0 migration, some use cases are solved using notes. Those notes contain values for restricted fields. Instead of losing data, we keep the values and don't copy them to avoid issues in use cases like "create credit note from invoice". Forward-Port-Of: odoo/odoo#64055
\* = hr_holidays, im_livechat, website_livechat A huge amount of components where rendered for no reason, notably when typing a new message (at every key press), which significantly slowed down the interface. There were 2 parts to this problem: - OWL rendering all children automatically, even if their props didn't change, unless `shouldUpdate` is overridden, which is now done. - `useStore` selectors being way too generous in what they observed task-2399731 Forward-Port-Of: odoo/o
Original PR description
\* = hr_holidays, im_livechat, website_livechat A huge amount of components where rendered for no reason, notably when typing a new message (at every key press), which significantly slowed down the interface. There were 2 parts to this problem: - OWL rendering all children automatically, even if their props didn't change, unless `shouldUpdate` is overridden, which is now done. - `useStore` selectors being way too generous in what they observed task-2399731 Forward-Port-Of: odoo/odoo#64935 Forward-Port-Of: odoo/odoo#62703
Before this commit the custom snippets were saved across websites because the RPC mechanism used by the save & reload does not include the context by default. After this commit the custom snippets are saved for the specific website as initially intended. No migration is needed: already created snippets that have been created across all sites will have the correct lifecycle because of the copy-on-update/copy-on-write. Related to task-2374802 Description of the issue/feature this PR
Original PR description
Before this commit the custom snippets were saved across websites because the RPC mechanism used by the save & reload does not include the context by default. After this commit the custom snippets are saved for the specific website as initially intended. No migration is needed: already created snippets that have been created across all sites will have the correct lifecycle because of the copy-on-update/copy-on-write. Related to task-2374802 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 Forward-Port-Of: odoo/odoo#64917
Forward-Port-Of: odoo/enterprise#15891 Forward-Port-Of: odoo/enterprise#15875
Original PR description
Forward-Port-Of: odoo/enterprise#15891 Forward-Port-Of: odoo/enterprise#15875
Forward-Port-Of: odoo/enterprise#15898
Original PR description
Forward-Port-Of: odoo/enterprise#15898
task-2347640 Forward-Port-Of: odoo/enterprise#15320
Original PR description
task-2347640 Forward-Port-Of: odoo/enterprise#15320