Tuesday, December 24, 2024
13 changes · saas-18.1
Enhancements to existing features
This update removes outdated HR test helper files that relied on legacy internal test tooling. It helps keep the HR module easier to maintain and aligned with the platform’s current testing standards, with no expected impact on day-to-day users.
Original PR description
Purpose of this commit: Remove files that depends on legacy 'bus/../test/helpers'. Part of:3818666 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update removes old Web Studio test files that relied on outdated internal test utilities. It helps keep the codebase easier to maintain and supports ongoing modernization work, with no expected impact on day-to-day users.
Original PR description
Purpose of this commit: Remove files that depends on legacy 'bus/../test/helpers'. Part of:3818666
This update removes outdated internal test helper files from the Timesheet Grid module. It helps keep the codebase easier to maintain and aligned with newer testing standards, with no expected change for everyday users.
Original PR description
Purpose of this commit: Remove files that depends on legacy 'bus/../test/helpers'. Part of:3818666
Resolved issues and error corrections
This update adjusts a web module performance test so it works reliably when demo data is not installed. It helps keep automated quality checks stable for deployments that use a lean, no-demo setup, without changing business features.
Original PR description
Without demo load menu perf test fails, 40 > 38 queries. It is due that some override of `_load_menus_blacklist` relies on some data or fallback are used. This commit was already merged in odoo/odoo#190328 But was reversed in odoo/odoo#191446 ==== This is a backport of https://github.com/odoo/odoo/pull/191584
Miscellaneous changes
This update prepares Odoo for the SaaS 18.1 release by freezing the version and aligning release-related settings. It helps ensure the platform is consistently identified and ready for the next hosted release cycle.
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#191594
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#191594
Steps to reproduce the issue: - Go to the settings and enable multi-routes. - Navigate to the warehouse and attempt to duplicate it. Problem: The operation types “Repair,” “Stock After Manufacturing Operation,” “Picking Before Manufacturing,” and “Manufacturing” are copied instead of creating new records. opw-4386529 Forward-Port-Of: odoo/odoo#191403 Forward-Port-Of: odoo/odoo#189965
Original PR description
Steps to reproduce the issue: - Go to the settings and enable multi-routes. - Navigate to the warehouse and attempt to duplicate it. Problem: The operation types “Repair,” “Stock After Manufacturing Operation,” “Picking Before Manufacturing,” and “Manufacturing” are copied instead of creating new records. opw-4386529 Forward-Port-Of: odoo/odoo#191403 Forward-Port-Of: odoo/odoo#189965
The Viva Wallet integration relies on Odoo being called by Viva Wallet via a webhook. There have been many issues of this webhook never being called, and therefore payments getting stuck in Odoo. In this commit, we add a polling fallback. Every 5 seconds we query the Viva Wallet session, and if we get a response (success/failure) then we update the payment state in the PoS. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odo
Original PR description
The Viva Wallet integration relies on Odoo being called by Viva Wallet via a webhook. There have been many issues of this webhook never being called, and therefore payments getting stuck in Odoo. In this commit, we add a polling fallback. Every 5 seconds we query the Viva Wallet session, and if we get a response (success/failure) then we update the payment state in the PoS. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#191241 Forward-Port-Of: odoo/odoo#190213
Design Themes: https://github.com/odoo/design-themes/pull/1038 Enterprise: https://github.com/odoo/enterprise/pull/76159
Original PR description
Design Themes: https://github.com/odoo/design-themes/pull/1038 Enterprise: https://github.com/odoo/enterprise/pull/76159
*: pos_restaurant, pos_loyalty Previously, synchronization management was faulty when two devices created a command at the same time. One would override the other. To overcome this problem, when sending the command to the server, we check whether the table used by the command already contains a command. If so, they are merged. When different devices use the same PoS, when an order is created on one of them, it is directly synchronized with the others. This makes it possible to calc
Original PR description
*: pos_restaurant, pos_loyalty Previously, synchronization management was faulty when two devices created a command at the same time. One would override the other. To overcome this problem, when sending the command to the server, we check whether the table used by the command already contains a command. If so, they are merged. When different devices use the same PoS, when an order is created on one of them, it is directly synchronized with the others. This makes it possible to calculate the various table states with greater precision. As in Master, orders are now identified by UUID rather than ID. The `replaceDataByKey` function is no longer used; what it used to do is now in loadData. All these fixes are very important in view of the problems encountered by some customers. Forward-Port-Of: odoo/odoo#190559 Forward-Port-Of: odoo/odoo#190088
This pull request prepares the Enterprise codebase for the SaaS 18.1 release. It is a release housekeeping update that helps align versioning and packaging for the next service rollout, with no specific business feature changes identified from the provided details.
Community: https://github.com/odoo/odoo/pull/191697 Design Themes: https://github.com/odoo/design-themes/pull/1038
Original PR description
Community: https://github.com/odoo/odoo/pull/191697 Design Themes: https://github.com/odoo/design-themes/pull/1038
Since the latest changes on https://github.com/odoo/enterprise/commit/6d49119281901e51910bb71e34300e414216123b, we use the gantt view as in appointments so when trying use the "More Options" from here, we will try to load the calendar form for which we will need to add the assets to not throw an error. Steps to reproduce: 1. Get a restaurant session in pos. 2. On the top right burguer menu, select Manage Bookings. 3. Then create a new one o select an existing one to open the dialog.
Original PR description
Since the latest changes on https://github.com/odoo/enterprise/commit/6d49119281901e51910bb71e34300e414216123b, we use the gantt view as in appointments so when trying use the "More Options" from here, we will try to load the calendar form for which we will need to add the assets to not throw an error. Steps to reproduce: 1. Get a restaurant session in pos. 2. On the top right burguer menu, select Manage Bookings. 3. Then create a new one o select an existing one to open the dialog. 4. Click on "More Options". opw-4334444 Forward-Port-Of: odoo/enterprise#74030