This update simplifies how the enterprise mail form layout handles the chatter area by moving shared logic into the common codebase. The change reduces duplicated customization and should make future maintenance safer without changing day-to-day user workflows.

The invoice document scanning flow now shows more specific error messages when OCR processing fails, such as unsupported image sizes, missing page counts, or PDF conversion problems. This helps users and support teams understand what went wrong and take the right next step faster.

- Added new errors messages to be displayed in the client coming from the OCR

This update strengthens automated checks across Helpdesk workflows, including ticket assignment, portal closure, live chat commands, ratings, service-level policies, field service tasks, and related sales, repair, stock, and accounting actions. It helps reduce the risk of regressions in customer support processes without changing end-user functionality directly.

This PR removes some unused test code and adds tests to cover the following helpdesk cases:

- Employees on time off should not get automatically assigned to tickets.
- The `/helpdesk command` should create a new ticket.
- The `/helpdesk_search` command should return tickets matching the query.
- When an SLA policy is set on a service, the SOL containing this service should be set on the SLA policy once the SO is confirmed.
- An email should be sent to the customer when a ticket reaches a stage with a rating template.
- The ratings should be displayed on the website.
- Tickets should be able to be shared on the help forum.
- Tickets should close automatically after a configurable period of time.
- Customers should be able to close their own tickets in the portal when the setting is enabled.
- Refunds, Repairs and Returns should be logged in the chatter.
- An fsm task should be able to be created from a ticket, and closing said task should be logged in the chatter of the ticket.

Task-2796546

The mail enterprise form code was reorganized so related sections are grouped and ordered more logically. This is an internal cleanup that makes future maintenance easier without changing user-facing behavior.

Overridden methods from Form view are separated from custom mail methods, and
are sorted according to their call in the lifecycle.

This will make it easier to understand the file, in preparation to clean it
further.

Part of task-2871070

When supplier invoices are processed with the “Single line per tax” option, line descriptions now use a generic supplier-and-date format instead of detailed extracted text. This keeps invoice summaries focused on the amounts and taxes, which is what users of this option typically need.

When the option "Single line per tax" is activated, it will now use
the generic "Supplier - date" description.
This is done as most users of that option don't actually care about the
description of the lines, only the amounts and taxes matter.

Task #2858632

This update simplifies how sales-related apps calculate prices and discounts, making the logic easier to maintain and more consistent across subscriptions, rentals, and time-based sales. It also improves related tests and naming, reducing the risk of future pricing issues without introducing major visible changes for users.

COM PR: https://github.com/odoo/odoo/pull/88230

Before, each time we wrote on an appointment type we set to False the message_intro if we didn't update it. We now remove this part as it leads to side effect on performance. The additional queries are linked to the "res.lang" model. Indeed with the previous behaviour, the field was automatically set to False. This led to ignore translation feature for the field each time we wrote on records. We fix also an unslug in a route which was not used correctly task-2858271 Forward-Port-O

Before, each time we wrote on an appointment type we set to False
the message_intro if we didn't update it.
We now remove this part as it leads to side effect on performance.

The additional queries are linked to the "res.lang" model.
Indeed with the previous behaviour, the field was automatically set
to False. This led to ignore translation feature for the field each
time we wrote on records.

We fix also an unslug in a route which was not used correctly

task-2858271

Forward-Port-Of: odoo/enterprise#28653
Forward-Port-Of: odoo/enterprise#28054

Commit 25db5caf33c6ddfc2895915a99fe296c91ca24ef updated the SIP.js library, changing the name of some parameters. This commit renames a parameter that had been forgotten. Forward-Port-Of: odoo/enterprise#28665

Commit 25db5caf33c6ddfc2895915a99fe296c91ca24ef updated the SIP.js library, changing the name of some parameters.

This commit renames a parameter that had been forgotten.

Forward-Port-Of: odoo/enterprise#28665

Prior to this commit, cancelling a time off would have no effect on the payslip if it was already created. Since an user may now cancel a time off as long as the associated work entries are not validated, this became necessary. TaskId-2791386 Relates to odoo/odoo#86268 Forward-Port-Of: odoo/enterprise#26497

Prior to this commit, cancelling a time off would have no effect on the
payslip if it was already created.
Since an user may now cancel a time off as long as the associated work
entries are not validated, this became necessary.

TaskId-2791386

Relates to odoo/odoo#86268

Forward-Port-Of: odoo/enterprise#26497

Steps: - Marketing automation - Campaigns -> Open a campaign - Edit mode - Edit an activity - Create a new mail template via the activities form view A new marketing template form view is opened with "Send From" readonly The 'email_from' field should only be readonly if it's a non automation related mailing. opw-2844711 Forward-Port-Of: odoo/enterprise#28638 Forward-Port-Of: odoo/enterprise#28357

Steps:
- Marketing automation
- Campaigns -> Open a campaign
- Edit mode
- Edit an activity
- Create a new mail template via the activities form view
A new marketing template form view is opened with "Send From" readonly

The 'email_from' field should only be readonly if it's a non automation
related mailing.

opw-2844711

Forward-Port-Of: odoo/enterprise#28638
Forward-Port-Of: odoo/enterprise#28357

Before this commit if `/info` is added to the url of an online appointment (e.g. `/calendar/appointment_type/info`), without specifying the arguments, it throws a server error. This is particularly problematic as in v14 the pattern is added to the site map. This causes problems with search engines and crawlers and prevents successful crawling of the website. We can prevent unsuccessful crawls by excluding this URLs from the site map. (See discussion in: https://github.com/odoo/enterpri

Before this commit if `/info` is added to the url of an online
appointment (e.g. `/calendar/appointment_type/info`), without
specifying the arguments, it throws a server error. This is
particularly problematic as in v14 the pattern is added to the
site map. This causes problems with search engines and crawlers
and prevents successful crawling of the website.

We can prevent unsuccessful crawls by excluding this URLs
from the site map. (See discussion in:
https://github.com/odoo/enterprise/pull/27894)

opw-2856276

Forward-Port-Of: odoo/enterprise#28286
Forward-Port-Of: odoo/enterprise#27921

The new searchpanel implementation hadn't been correctly adapted owl2. This commit fixes the issues. Co-authored-by: William Braeckman <wbr@odoo.com> Forward-Port-Of: odoo/enterprise#28610

The new searchpanel implementation hadn't been correctly adapted
owl2. This commit fixes the issues.

Co-authored-by: William Braeckman <wbr@odoo.com>

Forward-Port-Of: odoo/enterprise#28610