Friday, February 9, 2024
5 changes · master
Resolved issues and error corrections
The sales order chat now displays order confirmation email notifications with cleaner formatting. This makes the confirmation history easier for sales teams to read after a customer completes a website purchase.
Original PR description
**Issue Description**: In versions 16.0 to master, there's a formatting issue with the order confirmation email notification displayed in the sales order chat within the `Sale` app. When an order…
**Issue Description**: In versions 16.0 to master, there's a formatting issue with the order confirmation email notification displayed in the sales order chat within the `Sale` app. When an order confirmation email is sent to a customer after a purchase on the website, the corresponding notification message in the sales order chat exhibits broken formatting. The text is overly condensed on one line, leading to an overflow onto the next line, resulting in a cluttered and difficult-to-read display. **Steps to Reproduce**: 1. Navigate to the `Shop` section of the website, add a product to the cart, and proceed to checkout. 2. Complete the payment using demo. 3. Go to the `Sale` app, and locate the order using the order title provided post-payment on the website. 4. Notice that the message about the order confirmation email in the sales order chat has broken formatting. **Proposed Solution**: To address this issue, we will apply `white-space: nowrap;` to the email template. This CSS property will prevent the text from breaking and wrapping onto the next line, ensuring the notification message remains on a single line and improves readability. opw-3697582
This fix ensures Odoo's web testing tools correctly simulate key presses that include Control, Alt, or Shift. It improves reliability for automated checks around keyboard shortcuts and interactions, reducing the risk of missed issues before release.
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
Time off allocations now only allow selecting employees from the companies currently selected by the user. This prevents accidental allocations to employees in other accessible companies and keeps multi-company workflows aligned with the user's active company context.
Original PR description
Before this commit, for databases with multiple companies, you were able to select any employee from any company if you had access to those companies, even though you were not logged to any of them. This commit restrains the choice to the selected companies only.
Belgian payroll users now get a clear warning when trying to update working schedules for multiple contracts at once. This avoids a system error and helps users complete the task correctly by updating one contract at a time.
Original PR description
Updating working schedules in batch mode for contracts currently causes a system error. This commit ensures that the update process now raises a user error if multiple contracts are selected. Task-3571866
Intrastat country and region settings have been moved to the shared Intrastat module so they can support more country localizations beyond Belgium. This keeps configuration consistent and hides region settings when they do not apply to a company's country.
Original PR description
… higher model The fields company_country_id and intrastat_region_id were both defined in l10n_be_intrastat. These fields are now required on other localizations, such as France which will come in a later commit. For this reason, these fields need to be defined on account_intrastat to be used by all possible localization. The view of the intrastat region (visible in the settings) must also be defined in account_intrastat, and make the field invisible if the company country has no intrastat region defined. task-3691571