Wednesday, February 28, 2024
16 changes · saas-17.1
Enhancements to existing features
This update enhances the testing process for our Point of Sale system, specifically focusing on barcode scanning. The tests have been reorganized to better utilize existing barcode functionality, ensuring more reliable and accurate scanning results. This improves the overall stability and performance of the POS experience.
Original PR description
refactor 'scan_barcode' method to use barcodes function task id: 3674936 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#153993
Resolved issues and error corrections
This update improves the clarity of tax labels within Odoo's Point of Sale, Sale, and Website Sale modules. The term 'VAT' has been replaced with 'Tax' to align with international standards and improve user understanding. This change ensures consistent and accurate reporting of tax information.
Original PR description
task-3653060 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
In the current system, the order widget experienced undesired updates to all order lines when a new product with the same attribute was added. Our recent changes address this issue, ensuring that existing attribute values remain unaffected by the addition of new ones. Moreover, we've refined the display of attribute information. If an attribute is designated as "never," it will now be incorporated into the order line note. Conversely, attributes with different settings will continue to be dis
Original PR description
In the current system, the order widget experienced undesired updates to all order lines when a new product with the same attribute was added. Our recent changes address this issue, ensuring that existing attribute values remain unaffected by the addition of new ones. Moreover, we've refined the display of attribute information. If an attribute is designated as "never," it will now be incorporated into the order line note. Conversely, attributes with different settings will continue to be displayed in their usual format. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#152213
This update fixes an issue where the quantity returned in the returns wizard was incorrectly reflecting the full delivery quantity (10) instead of the delivered quantity (6). This change ensures that returns accurately reflect the actual amount of product returned, improving inventory accuracy and reducing discrepancies. The fix was triggered by a reported bug (opw-3726157).
Original PR description
**Steps to reproduce the bug:**
- Create a delivery picking:
- product: P1
- Qty: 10
- Mark as todo
- Set “Quantity” to = 6
- Validate the picking without creating a backorder
- return the picking
**Problem**:
The qty to return is 10 instead of 6
opw-3726157
Forward-Port-Of: odoo/odoo#155508This update fixes a limitation in the hr_gamification module where badges couldn't be assigned to users without a linked employee. The change removes a dependency between user and employee IDs, now allowing badges to be granted to any user regardless of their employee association. This expands the usability of the gamification feature.
Original PR description
When hr_gamification is installed, it's not possible to grant badges to users that don't have associated employees. Expected behavior: we should be able to grant badges to any users. This is because user_id was related field with employee_id. We remove that dependency. task - 3593382 Forward-Port-Of: odoo/odoo#155007
This update ensures the translation file (POT) for the core 'base' module is current. Outdated translation files can lead to inconsistencies in localized versions of the software. This fix guarantees accurate translations for this foundational module.
Original PR description
Export pot of base module Entreprise: https://github.com/odoo/enterprise/pull/57503 Forward-Port-Of: odoo/odoo#155375
It is necessary to append the description "The due date should not be earlier than the invoice date. Please verify the invoice dates and payment terms." when the user receives error 10164. Task Adhoc side: 36216 Forward-Port-Of: odoo/enterprise#57157 Forward-Port-Of: odoo/enterprise#55901
Original PR description
It is necessary to append the description "The due date should not be earlier than the invoice date. Please verify the invoice dates and payment terms." when the user receives error 10164. Task Adhoc side: 36216 Forward-Port-Of: odoo/enterprise#57157 Forward-Port-Of: odoo/enterprise#55901
When an incoming call is cancelled by the remote party, the current session is not properly cleared, causing Odoo to reject all subsequent calls, assuming the user is busy, since the previous session is still present. This commit fixes the problem by properly clearing the current session when a CANCEL message is received. Forward-Port-Of: odoo/enterprise#57525
Original PR description
When an incoming call is cancelled by the remote party, the current session is not properly cleared, causing Odoo to reject all subsequent calls, assuming the user is busy, since the previous session is still present. This commit fixes the problem by properly clearing the current session when a CANCEL message is received. Forward-Port-Of: odoo/enterprise#57525
Issue: When adding a new Calendar Item without a title, the item does not allocate the required space, causing it to appear slightly under the calendar item. Additionally, if any item is moved to the top of the calendar, it overlaps the title placeholder, preventing title modification. Steps to Reproduce: 1. Install Knowledge. 2. Create a new article and select 'Build an Item Calendar'. 3. Proceed without entering a title. 4. Type anything below the created Calendar and move it to
Original PR description
Issue: When adding a new Calendar Item without a title, the item does not allocate the required space, causing it to appear slightly under the calendar item. Additionally, if any item is moved to the top of the calendar, it overlaps the title placeholder, preventing title modification. Steps to Reproduce: 1. Install Knowledge. 2. Create a new article and select 'Build an Item Calendar'. 3. Proceed without entering a title. 4. Type anything below the created Calendar and move it to the top of it. Solution: Modify the 'onBuildItemCalendarBtnClick' function to utilize a "computed" title rather than directly using the name. This ensures that a placeholder title is always present, allowing for later deletion or modification. opw-3725805 Forward-Port-Of: odoo/enterprise#56423
Backport of: https://github.com/odoo/enterprise/pull/53382/commits/60bd7a3a24aa9abd9fcf97b65c7cfd25812c3b73 opw-3764778 Forward-Port-Of: odoo/enterprise#57513
Original PR description
Backport of: https://github.com/odoo/enterprise/pull/53382/commits/60bd7a3a24aa9abd9fcf97b65c7cfd25812c3b73 opw-3764778 Forward-Port-Of: odoo/enterprise#57513
Since commit d79ac56, invoices coming from the email alias were automatically sent to the OCR even when the automatic sending mode was disabled. The logic that decides whether or not the document should be automatically sent to the OCR was duplicated at multiple places, making this kind of error easy to make. This commit addresses the issue by introducing a new `_check_auto_extract_conditions` function that regroups all the necessary conditions that needs to be met for auto extraction. Ti
Original PR description
Since commit d79ac56, invoices coming from the email alias were automatically sent to the OCR even when the automatic sending mode was disabled. The logic that decides whether or not the document should be automatically sent to the OCR was duplicated at multiple places, making this kind of error easy to make. This commit addresses the issue by introducing a new `_check_auto_extract_conditions` function that regroups all the necessary conditions that needs to be met for auto extraction. Ticket #3708420 Forward-Port-Of: odoo/enterprise#57504
Improve how the CODA journal is retrieved Community https://github.com/odoo/odoo/pull/155375 Forward-Port-Of: odoo/enterprise#57503
Original PR description
Improve how the CODA journal is retrieved Community https://github.com/odoo/odoo/pull/155375 Forward-Port-Of: odoo/enterprise#57503
The tag `document_tag_signature_request` is used by the `sign` endpoint, but it could be missing after an upgrade from <17 due to the `forcecreate=0` in the data file. Forward-Port-Of: odoo/enterprise#57324
Original PR description
The tag `document_tag_signature_request` is used by the `sign` endpoint, but it could be missing after an upgrade from <17 due to the `forcecreate=0` in the data file. Forward-Port-Of: odoo/enterprise#57324
Before this commit, the test test_add_non_searchable_field crashed in no-demo mode because an image was not set on a partner, and that had only an effect on a sanity check in the business code rather than an effect on the relavance of the test After this commit, the test doesn't crash in demo mode. runbot-error-57397 runbot-error-57430 runbot-error-57432 runbot-error-57822 runbot-error-58218 Forward-Port-Of: odoo/enterprise#57559
Original PR description
Before this commit, the test test_add_non_searchable_field crashed in no-demo mode because an image was not set on a partner, and that had only an effect on a sanity check in the business code rather than an effect on the relavance of the test After this commit, the test doesn't crash in demo mode. runbot-error-57397 runbot-error-57430 runbot-error-57432 runbot-error-57822 runbot-error-58218 Forward-Port-Of: odoo/enterprise#57559
Before this commit, the "Force Source Location scan" setting of the delivery picking type was always reset on "Mandatory Scan" every time the `stock_barcode` module was updated. This behavior is not wanted, if the user changes the setting, we don't want to update it again. Forward-Port-Of: odoo/enterprise#57499
Original PR description
Before this commit, the "Force Source Location scan" setting of the delivery picking type was always reset on "Mandatory Scan" every time the `stock_barcode` module was updated. This behavior is not wanted, if the user changes the setting, we don't want to update it again. Forward-Port-Of: odoo/enterprise#57499
Before this commit, the new class of tests for studio approvals crashed in without demo mode After this commit, it works as data used in the test have been adapted runbot-error-57997 runbot-error-57996 Forward-Port-Of: odoo/enterprise#57558
Original PR description
Before this commit, the new class of tests for studio approvals crashed in without demo mode After this commit, it works as data used in the test have been adapted runbot-error-57997 runbot-error-57996 Forward-Port-Of: odoo/enterprise#57558