Wednesday, December 22, 2021
5 changes · master
Enhancements to existing features
Calendar event organizers are now informed when some attendees have missing or invalid email addresses. This helps them understand that those attendees will not receive email notifications and can correct the contact details if needed.
Original PR description
If some attendees of an event have an empty or invalid email address, the organizer of this event should be informed that these attendees won't receive any email notifications. opw-2667016 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Batch payments now include a communication area where users can track changes, add notes, schedule tasks, and receive activity notifications. This makes payment follow-up easier and improves visibility for teams managing batch payment workflows.
Original PR description
Currently: batch payments don't have a chatter and the changes cannot be tracked. Desired: users want to be to able track changes, make notes, and schedule tasks. Task ID: 2711574 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update adds a new way for users to open and view the current website directly inside the Website app dashboard. It helps teams preview or access the live website more quickly without leaving the Odoo back office.
Original PR description
[WIP] task-2687506
Manufacturing backorders are now processed more efficiently when work orders are involved. This should reduce delays for users managing larger or more complex production runs, while keeping the functional behavior largely unchanged.
Original PR description
Rename generate_backorder_productions_multi to split_production Make generate_backorder_productions take advantage of split_production task 2633369
Code cleanup and technical improvements
Manufacturing orders with multiple serial numbers are now split in batches instead of one by one, greatly reducing processing time for large production runs. The change also adds a warning when mass producing with components from multiple lots, helping users confirm the action is intentional.
Original PR description
There is 2 major issues with the production of multiple serials number - Performance issue - Duplicated code with classic backorder mechanism The performance issues exist since backorders were create…
There is 2 major issues with the production of multiple serials number - Performance issue - Duplicated code with classic backorder mechanism The performance issues exist since backorders were create one by one and `stock.move` and `stock.move.line` are always recomputed. They are not created in batch neither. _generate_backorders is removed and replace by _split_productions. The functionality are the same. Technicaly it does the maximum in batch, first it creates all the `mrp.production` then all the `stock.move` and finaly, it splits the existing `stock.move.line` among the new `stock.move` It means that the reservation is not recompute anymore during a backorder process and will remain the same than the splitted production order. Performance metrics (10 components): | # | 2 | 10 | 100 | 1000 | |----------|------------|----------|----------|-------------| | Before | 0.47s | 2.84s | 32.25s | 580.53s | | After | 0.13s | 0.36s | 2.60s | 35.17s | task 2633369