Wednesday, May 15, 2024
5 changes · saas-17.1
Resolved issues and error corrections
This fix changes manufacturing order handling so base operations are not blocked simply because of planned start dates. Instead, production steps are controlled according to the bill of materials order, helping teams process manufacturing work in the intended sequence.
Original PR description
manual port of https://github.com/odoo/odoo/commit/c5175077ff9403bd2c1873a0144f31a6e8c8d3e3 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
Mass production now lets users generate the needed serial numbers before quality check warnings appear. This prevents the process from being blocked or interrupted in the wrong order, especially in two-step manufacturing setups.
Original PR description
When mass producing products that needs serial numbers, the quality check warning is thrown before being able to generate multiple serial numbers. The main fix is done in the enterprise pr, this commit only adds hooks for the enterprise changes enterprise : https://github.com/odoo/enterprise/pull/59382 task-id: 3821092 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
Fixed an issue where users with an active livechat session could encounter a crash when creating a new draft record, such as a sales order. The change keeps livechat and record creation working smoothly together, reducing disruption for operators handling customer conversations.
Original PR description
Before this commit, when a livechat operator had livechats open, making a draft record result to crash. Steps to reproduce: - Log in as Admin; - Set a livechat user name in Preferences then Save; -…
Before this commit, when a livechat operator had livechats open, making a draft record result to crash. Steps to reproduce: - Log in as Admin; - Set a livechat user name in Preferences then Save; - In incognito, open livechat from website then post a message; - In admin tab, when livechat is open, make a new record e.g. make a new sale order => Crash with: ``` TypeError: can't access property "channel_type", this.message.thread is undefined ``` This happens because when making a draft record, the chatter contains the message "Creating a new record...". This record was missing `originThread`, which is assumed to be necessarily known for any message. Thankfully this is not a problem most of the time, but with livechat open and livechat operator having a custom livechat name, this executes evaluation of `this.message.originThread.type`, which crashes due to unset `originThread`. This commit fixes the issue by properly setting the originThread of the "Creating a new record..." message. opw-3913228
Point of Sale now links records more efficiently when loading large amounts of data. This should reduce waiting times in situations with many records, improving the overall user experience for businesses using POS.
Original PR description
Prior to this commit, the addItem function had a time complexity of O(n), which resulted in lengthy data load times when dealing with numerous records. This commit optimizes the function by utilizing a set, thereby reducing the time complexity to O(1) and significantly improving performance. opw-3923668 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Manufacturing orders that produce several serialized items now open the serial number generation step before showing quality check warnings. This prevents users from being blocked by a quality alert before they can create the required serial numbers and backorders.
Original PR description
When producing all the products of a MO, the quality check error is raised before the serial number autocomplete wizard is shown. This should be the opposite. task-id: 3821092