Friday, August 20, 2021
14 changes · master
New functionality added to Odoo
Point of Sale now supports Worldline payment terminals through the IoT Box. This gives businesses another integrated payment terminal option, helping streamline in-store card payments and terminal management.
Original PR description
Add support for Worldline terminals with the IoT Box. Implementation documentation: https://github.com/odoo/worldline-lib TaskID: 2368696
Businesses can now use the appointment app with the customer portal instead of needing a full website. Customers can book from shared links and view their appointments in the portal, reducing setup needs for service businesses like clinics or offices.
Original PR description
Use case: e.g. We have a Dental Office that does not need a website but still wants to send appointment links to its patients. The patient will get the link and follow the usual process to take the appointment. The user will no longer need to buy the website module to use those features. PURPOSE Allow to use the appointment app even when website is not installed. We now allow the use of this app with the portal app. Parts depending on the website app are still in the former website_calendar app. Parts that are kept in website_calendar: - /calendar route and linked templates; - Website visitor; - website.published mixin & related fields; The new appointment module is the same as before but for the previous point. We also add portal templates for the appointment module. Customers can now check their appointment in customer portal. See sub commits for more details. Task-2427015
Enhancements to existing features
This update cleans up and standardizes the Ecuadorian electronic invoicing process, including supporting setup files and document handling. It helps improve maintainability and reduces the chance of configuration or formatting issues in the EDI workflow.
Original PR description
- Fix libraries definition on manifest - Run Flake8 and black on module l10n_ec_edi
Resolved issues and error corrections
Social form views now prevent clicks on engagement statistic buttons that do not open any action, avoiding a crash introduced after a recent interface update. Campaign forms also hide the engagement statistic when it is zero, keeping the view cleaner for users.
Original PR description
Since the latest OWL refactoring, stat-buttons "button" DOM element in form views cannot be defined without an associated action (it will crash on click). In the social module, we have 2 engagement fields for statistics, on social.posts and on social.campaigns. The engagement statistics are displayed using the style of a stat-button in those models' form views, but have no associated action. To fix the issue, we now mark the buttons as "disabled" so the click action will not trigger anything. We also took this opportunity to hide that statistic in the campaign form view when the value is 0. Task-2618108
Miscellaneous changes
In some cases, depending on how the `entry` and the `entry_details` are structured, the rate could not be detected correctly when the currency was different from th journal's currency. [opw-2618969](https://www.odoo.com/web#id=2618969&model=project.task) Forward-Port-Of: odoo/enterprise#20161
Original PR description
In some cases, depending on how the `entry` and the `entry_details` are structured, the rate could not be detected correctly when the currency was different from th journal's currency. [opw-2618969](https://www.odoo.com/web#id=2618969&model=project.task) Forward-Port-Of: odoo/enterprise#20161
The PLM app has been revamped to make engineering change orders easier to manage and safer to approve. Users get clearer approval tasks, better visibility of document and operation changes, and manufacturing orders can be updated or alerted when a newer bill of materials is available.
Original PR description
Revamp mrp_plm addon: 1. Clean dead code for eco type "both". 2. Create a "ECO Approval" activities for approvers when creating approvals. 3. On MOs, we add a button to change the bom to latest…
Revamp mrp_plm addon: 1. Clean dead code for eco type "both". 2. Create a "ECO Approval" activities for approvers when creating approvals. 3. On MOs, we add a button to change the bom to latest version when MO is still "draft". If the MO is not "draft", a button will be shown to notify the user the availability of a later version. 4. Make the kanban state of the eco customizable. 5. Stages can be shared by different eco types now. 6. Hide the edit button to prevent user editing the file anymore after applying the change. 7. Include operation step changes in eco. 8. When a change is positive, add a "+" in front of the number. 9. Make action_apply multi and add it to list view. 10. When update documents, match the eco type "product" or "bom", i.e. we only apply document changes on the product or on the bom 11. In eco, we add a ribbon to the file to show if it has been edited, deleted, or newly added. 12. Only allow users with access rights to be approvers Task-2466232 COM PR odoo/odoo#69914 Upgrade PR odoo/upgrade#2427 PR #17960
This update adds clearer helper messages across Social Marketing and Marketing Automation menu pages. These messages guide users when pages are empty, making it easier to understand what to do next during onboarding.
Original PR description
PURPOSE Make sure all SM menu items have a proper action helper message. Specification: Current: There are not proper action helper for sm menus for proper onboarding. To Be: To add proper action helper message for better onboarding Task Id: 2584073 PR: #74082
Marketing automation actions can now run closer to their intended time instead of waiting for the next hourly background run. Campaign participant synchronization is also triggered right after launch, helping campaigns feel more accurate and responsive.
Original PR description
The marketing automation module is based on many actions that take place at a certain moment in time (e.g: "Send an email exactly one hour after the client opens another email"). Since the underlying…
The marketing automation module is based on many actions that take place at a certain moment in time (e.g: "Send an email exactly one hour after the client opens another email"). Since the underlying implementation is using CRON calls, these timings are usually not well respected (the CRON executing activities runs every hour, giving a maximum delay of one hour from the desired execution time). To get sharper timings, this commit adds CRON triggers when scheduling various marketing.traces. We also schedule the marketing.participants synchronization right after campaign launch to minimize delays. This should allow the feature to feel overall more accurate and maybe even improve actual results in terms of marketing statistics. Unit tests have been added in the test_marketing_automation module, within the existing "test_flow", to ensure this behavior. We re-use the "test_simple_flow" method since it has all the necessary activities to test our various use cases. Task-2520229
The Belgian balance sheet now includes the foreign currency translation differences account in the adjustment accounts section. This improves the accuracy of Belgian financial reporting and removes older account-code based checks in favor of broader account category rules.
Original PR description
The goal is to adjust the "Comptes de régularisation" section of the Belgian balance sheet. The 496000 account "Foreign currency translation differences - Assets" was not included. At the same time, every control domain that includes an 'account_id.code' was removed. Only the ones using an 'account_id.user_type_id.internal_group' are meant to be used from now on.
The reconciliation model form has been updated to make its labels and available options easier to understand. It also hides an activity-related option when it is not relevant, reducing confusion during setup.
Original PR description
This task aims to both explain supported reconciliation cases and improve the reconciliation model form view. The form improvement is mainly about label wording and make the options more self speaking. Task : 2427089 == PR's == https://github.com/odoo/odoo/pull/73043
Adds a test to ensure tax reports calculate taxable bases correctly when one tax affects the base for another and appears across multiple invoice lines. This helps prevent overstated tax bases and supports more reliable tax reporting.
Original PR description
The fix is on the related community branch. This is just adding a test for it.
1) Let's consider then following taxes
- tax 1, 42%, affecting the base
- tax 2, 10%
2) Create an invoice with the following lines, and post it:
- price=100, taxes=tax1
- price=100, taxes=tax2
- price=100, taxes=tax1+tax2
=> The tax details should compute the following amounts:
- base amount of tax 1: 200
- tax amount for tax 1: 84
- base amount of tax 2: 242
- tax amount for tax 2: 24.2
Before this fix, the base amount for tax 1 wasn't computed properly, and gave 300 instead of 200. This was because the same tax line (the one from tax1 with no tax_ids) was matching two different base lines: the one with tax1 and tax2, and the one with only tax1The pull request does not include changed files, commit messages, or a description, so the business impact cannot be determined. More information is needed to explain what changed and which Odoo areas are affected.
The extension was only added correctly when the `doc_name` was not provided. As a workaround, we could put the extension in the form, but it defeats the purpose of the wizard allowing to export multiple formats at the same time. Forward-Port-Of: odoo/enterprise#20164
Original PR description
The extension was only added correctly when the `doc_name` was not provided. As a workaround, we could put the extension in the form, but it defeats the purpose of the wizard allowing to export multiple formats at the same time. Forward-Port-Of: odoo/enterprise#20164
This reverts commit be8697c3d531decadbc4175fe5d0f8e3f7bb4647. The commit above does not actually solve the issue it was created for, instead it removes a feature we use to allow to force a car when signing new contracts. Reverting this commit while we find a better way to solve the issue, which is actually linked to not being able to sign with a forced car when no user has been created yet. Task ID: 2624963 See https://github.com/odoo/enterprise/pull/20116 Forward-Port-Of: odoo/ent
Original PR description
This reverts commit be8697c3d531decadbc4175fe5d0f8e3f7bb4647. The commit above does not actually solve the issue it was created for, instead it removes a feature we use to allow to force a car when signing new contracts. Reverting this commit while we find a better way to solve the issue, which is actually linked to not being able to sign with a forced car when no user has been created yet. Task ID: 2624963 See https://github.com/odoo/enterprise/pull/20116 Forward-Port-Of: odoo/enterprise#20254