Monday, November 6, 2023
10 changes · 17.0
Enhancements to existing features
The website configurator now integrates a website scraping capability, making it easier to build a new site using content or inspiration from an existing one. This streamlines initial website setup and can reduce manual work for users creating or migrating websites.
Original PR description
This commit permits to integrate the website scrapper in the website configurator. See enterprise PR: https://github.com/odoo/enterprise/pull/43306 task-3339551
Payment options are now shown in alphabetical order, making them easier for users to find. When a payment provider is enabled or tested, its most commonly used payment methods are activated automatically, reducing manual setup and helping businesses start accepting payments faster.
Large spreadsheet pivot tables now reuse previously calculated cell data instead of repeatedly recalculating it. This significantly improves dashboard loading and interaction speed for spreadsheets with large pivot tables.
Original PR description
This revision extends the caching introduced in [1] to cache the Pivot cells of a `PivotTable` for every combination of `includeTotal` and `includeColumnHeaders`. the conditions for the `clickableCell` of `ODOO.PIVOT.TABLE` cells fetch the pivot cells a LOT, which becomes problematic for big pivots. For a spreadsheet with a formulat `ODOO.PIVOT.TABLE` that spreads over 2562 (122*21) cells: | | Before | After | |----------------------------------|---------|--------| | `getPivotDomainArgsFromPosition` | 1227 ms | 124 ms | | load spreadsheet as dashboard | 7.97 s | 2.4 s | | | | | [1] https://github.com/odoo/odoo/pull/138594
Activity plans are easier to configure and use across Mail, HR, Sales, Project, and CRM. Users can edit plan templates more directly, schedule activities with clearer due dates, and access new plan setup options in Sales and Project while HR regains its launch plan action.
Original PR description
We do the following improvement: - some wording changes - the activity templates can be edited directly in the list view instead of in a popup except in hr because sub module add too many field to be edited in directly in the list view. - when scheduling a plan, the due date of the created activities are computed as the plan_date_deadline + activity type delay and if the plan_date_deadline is not specified, as today + activity type delay. - there were 2 res_model fields in the mail_activity_plan_view_form that was causing a selection box to appears on many form where the model shouldn't be selectable. We remove one of them here. Add activity plan menus and configuration to sale, project. Re-add the launch plan button in HR. When generalizing the plan, we have removed the custom "launch plan" button in the hr module. We re-add it here. Task-3558929
This update improves how Odoo estimates lead times for subcontracted and manufactured products by accounting for preparation days, vendor delays, purchasing delays, and related production route timing. Businesses get more accurate replenishment and delivery planning, reducing the risk of missed dates or underestimating production timelines.
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
The web interface no longer blocks users when a server request takes more than a few seconds during model reloads. This lets people continue applying filters or taking other actions without waiting for a loading overlay to disappear, improving workflow speed and reducing interruptions.
Original PR description
When a request to the server takes more than 3 seconds, the blockUI then prevents the user from taking another action. For example, when you want to apply several filters quickly, the blockUI appears and, in the end, you may want to apply yet another filter. In this commit, we remove the blockUI because we believe that blocking the user makes little sense. This only makes sense when installing a new application. task-3279095
Newly created assets can now carry the related vehicle information when managed in debug mode. This improves consistency between asset records and their associated journal entries, especially when assets are created from vehicle-related accounting moves.
Original PR description
Before this commit, it was not possible to add a vehicle to a newly created asset. Now in debug mode, you can find the vehicle in the value import group of the form view. Two flows are possible, either creating a move with a vehicle and creating an asset from it. There the vehicle in the asset page is fill with the value of put in the move. Or creating directly an asset from scratch and putting a vehicle (there the associate journal entry must have the right vehicle). task: 3581933
This update enhances the manufacturing planning system to include additional lead time factors (DTPMO) when calculating subcontracting timelines. This improvement helps ensure more accurate production scheduling and better planning for outsourced manufacturing activities.
Original PR description
Enterprise adaption for adding dtpmo to subcontracting lead days. Task-3081481
Document managers can now access and configure activity plans and types directly through the Documents module menu. This improvement makes it easier for document managers to set up and manage activity workflows without needing technical assistance. The change also includes improved wording for better clarity.
Original PR description
We add the activity plan and type menu to allows document managers to configure them. Also improve plan wording Task-3558929
This improvement fixes an issue in the Barcode App where users couldn't split a single product receipt across multiple packages. Previously, after packaging part of a quantity, scanning the same product again would update the already-packaged line instead of creating a new package. Now, the system automatically splits the move line when packaging, allowing users to package different quantities into separate packages as intended.
Original PR description
Imagine the following case: - You have a receipt for 20x a product; - You want to put 10 product into a first package, then 10 more in another package; - So, you open the receipt in the Barcode App, scan 10 times the product's barcode and then put in pack. What happens here is that the move line is put into a new package but that's all, so you end up with one line for the product, 10/20 qty and with the new package as the result package. Thus, if you scan the product one more time, it will update this existing and already packaged line's quantity, making impossible to set the remaining quantity in another package. To fix that, just before to call the `action_put_in_pack`, the "reserved" quantity of the move line will be decreased to its `qty_done` and a new move line will be created for the remaining quantity. Since the new line won't have any `qty_done`, only the first one will be packaged.