Odoo Changelog — 2026-03-26

Thursday, March 26, 2026

3 changes · saas-18.4

Bug Fixes(3)

Resolved issues and error corrections

[FIX] ai: broken conversations with agents on AI app

PR #112003

Enterprisesaas-18.4aiMedium

This update resolves a technical problem causing AI conversations to incorrectly display an 'OOO' banner and engage in self-chat. The fix ensures AI conversations function correctly with agents, maintaining proper routing and preventing unwanted self-interaction. This improves the overall AI app experience for users.

Original PR description

Override AI thread correspondent computation to keep the base behavior but clear the correspondent when it resolves to the current user in ai_composer/ai_chat. This avoids self-chat fallback side effects (like OOO banner) while preserving agent flows that rely on a real non-self correspondent.

source of this crash: https://github.com/odoo/enterprise/pull/108217

Forward-Port-Of: odoo/enterprise#111736

#ai#chatbot#conversation

[FIX] pos_iot: scale compatible with iot

PR #112071

Enterprisesaas-18.4pos_iotMedium

This update resolves an issue where the POS scale wasn't accurately displaying product weights due to a change in how the IoT box sends scale data. The fix ensures that the POS correctly reads and displays weight readings from the physical scale, improving the accuracy of order processing. This primarily affects users utilizing the POS module.

Original PR description

Steps to reproduce
- Use a localisation other than a european one (l10n_eu_iot_scale_cert must not be installed)
- Setup the scale for the POS
- Open the POS
- Add a product to be weighted by scale to the order
- Add product to the physical scale
- The displayed weight is always 0

Cause:
New versions of the IoT box uses the field result to return the scale measure instead of value.

Fix for version 18.0 and its intermediary versions.

[opw-5990467](https://www.odoo.com/odoo/project/49/tasks/5990467)

Forward-Port-Of: odoo/enterprise#111963

#POS#Scale#IoT#Integration

[FIX] l10n_ae_hr_payroll : Use record when computing l10n_ae_hourly_wage

PR #112098

Enterprisesaas-18.4l10n_ae_hr_payrollMedium

This update fixes a calculation error in the UAE payroll module that was causing incorrect hourly wage calculations for employees using the attendance work entry source. The change ensures that worked days are accurately reflected, preventing issues when computing payslips, particularly with leave time off entries. This improves payroll accuracy for UAE-based employees.

Original PR description

### Steps to reproduce:
	- Install the l10n_ae_hr_payroll module.
	- Configure at least two employees, who'll use the UAE Monthly pay structure.
	- On at least one of the employees, set the work entry source to attendance.
	- Register a paid leave time off entry, for the employee whose work entry source is set to attendance.
	- Compute a payslip batch using the UAE Monthly pay structure.
	- Go to the payslip of the employee with the work entry source set to attendance and compute the sheet again.
	- The 'Paid Leave' salary rule results, will change given that the computation of the field l10n_ae_hourly_wage is different when the computation is done for batches and individually.

### Cause:
In 'Paid Leave' rule we use l10n_ae_hourly_wage to compute its result and while computing this field we use self.worked_days_line_ids instead of record inside the loop. This leads to an issue when self has more than one payslip it will take into account all the worked days for each payslip for different employees

### Fix:
We use record instead of self to avoid taking other payslips into consideration while computing the hourly wage.

opw-5979631

Forward-Port-Of: odoo/enterprise#111280

Override AI thread correspondent computation to keep the base behavior but clear the correspondent when it resolves to the current user in ai_composer/ai_chat. This avoids self-chat fallback side effects (like OOO banner) while preserving agent flows that rely on a real non-self correspondent. source of this crash: https://github.com/odoo/enterprise/pull/108217 Forward-Port-Of: odoo/enterprise#111736

Steps to reproduce - Use a localisation other than a european one (l10n_eu_iot_scale_cert must not be installed) - Setup the scale for the POS - Open the POS - Add a product to be weighted by scale to the order - Add product to the physical scale - The displayed weight is always 0 Cause: New versions of the IoT box uses the field result to return the scale measure instead of value. Fix for version 18.0 and its intermediary versions. [opw-5990467](https://www.odoo.com/odoo/project/49/tasks/5990467) Forward-Port-Of: odoo/enterprise#111963

### Steps to reproduce: - Install the l10n_ae_hr_payroll module. - Configure at least two employees, who'll use the UAE Monthly pay structure. - On at least one of the employees, set the work entry source to attendance. - Register a paid leave time off entry, for the employee whose work entry source is set to attendance. - Compute a payslip batch using the UAE Monthly pay structure. - Go to the payslip of the employee with the work entry source set to attendance and compute the sheet again. - The 'Paid Leave' salary rule results, will change given that the computation of the field l10n_ae_hourly_wage is different when the computation is done for batches and individually. ### Cause: In 'Paid Leave' rule we use l10n_ae_hourly_wage to compute its result and while computing this field we use self.worked_days_line_ids instead of record inside the loop. This leads to an issue when self has more than one payslip it will take into account all the worked days for each payslip for different employees ### Fix: We use record instead of self to avoid taking other payslips into consideration while computing the hourly wage. opw-5979631 Forward-Port-Of: odoo/enterprise#111280