This update makes a few internal improvements to how VoIP registration settings are initialized and maintained. It helps keep the calling registration process clearer and more consistent, with minimal direct impact for users.

In this commit:
+ Make the expiration interval a field and document it
+ Set the initial value of `state` in `_created` hook instead of via a compute
+ Fix single quotes

This update simplifies how several Odoo Enterprise apps handle internal data replacement behavior. It should make the underlying code easier to maintain without changing day-to-day user workflows.

* = approvals, documents, sign, voip

Distinction between "replace" and "insert-and-replace" can be guessed based on
the type of the provided data.

task-2957295

https://github.com/odoo/odoo/pull/98404

This fixes the text color on bank reconciliation model buttons so labels appear in white as intended. The change improves readability and keeps the accounting interface visually consistent for users.

The text color should be white.

task: 2928259

Some preloaded records created from XML were treating HTML content as XML, which could add unwanted headers or wrappers. This update marks those fields correctly so demo and configuration content displays as intended across affected apps.

When a record is created through xml data, its HTML fields should
receive a `type="html"` attribute, not a `type="xml"` attribute.

When important XML data with XML type instead of HTML type will have 2
differences:
- The field value will be prefixed by `<?xml version="1.0"/>`
- If the HTML contains multiple root nodes, the value will be wrapped in
  a `<data/>` tag.

See `_fix_multiple_roots()` and the `xml_import` class for more details.

The messaging code was updated to use a simpler internal name for a message list item. This does not change how users interact with the product, but it makes the code easier to understand and maintain.

When an article does not have any title and the user clicks on the text input containing the title of the document, the script will automatically fill the text input with the first h1 of the document. The selector allowing the script to retrieve the first h1 is not correct and can select several titles at once. When it occurs, the script fills the text input with a concatenation of all h1 titles which does not correspond to the desired behavior. With this commit, we will update the selecto

When an article does not have any title and the user clicks on the text input containing the title of the document, the script will automatically fill the text input with the first h1 of the document.

The selector allowing the script to retrieve the first h1 is not correct and can select several titles at once. When it occurs, the script fills the text input with a concatenation of all h1 titles which does not correspond to the desired behavior.

With this commit, we will update the selector to select the first h1 of the document. We will also slightly refactor the function to make sure that the model is updated before updating the view.

task-2957260

Forward-Port-Of: odoo/enterprise#30576

Some Helpdesk Tickets have wrong 'SLA Failed' flag (True), even when all policies are met. To replicate customer issue I followed steps below: 1. We have SLA policy with deadline (assume 5 min after creation of ticket). 2. Our ticket met conditions for SLA (conditions were met before 5 minutes, so "SLA Failed" Flag is false). 3. After SLA deadline (let us say 15 minutes after ticket creation) the Kanban stage of ticket changes. 4. As result, "SLA Failed" flag will be true. As per my

Some Helpdesk Tickets have wrong 'SLA Failed' flag (True), even when all policies are met.

To replicate customer issue I followed steps below:

1. We have SLA policy with deadline (assume 5 min after creation of ticket).
2. Our ticket met conditions for SLA (conditions were met before 5 minutes, so "SLA Failed" Flag is false).
3. After SLA deadline (let us say 15 minutes after ticket creation) the Kanban stage of ticket changes.
4. As result, "SLA Failed" flag will be true.

As per my check, it comes from recalculating function '_compute_sla_reached_late', which checks if deadline is earlier that reached SLA date (ok) or deadline is earlier than now (not ok, as there is no condition to exclude SLA that are already satisfy, i.e. reached date is earlier than deadline). That function depends on deadline, which is recalculated when ticket changes stage.

To fix it, condition for SQL was modified. First one remains the same, second has additional AND condition that reached date is NULL.

Support ticket id: 2869202

Forward-Port-Of: odoo/enterprise#30235

Forward-Port-Of: odoo/enterprise#30543 Forward-Port-Of: odoo/enterprise#29796

Forward-Port-Of: odoo/enterprise#30543
Forward-Port-Of: odoo/enterprise#29796