This update makes several Odoo Enterprise screens more resilient by automatically checking that related records still exist before actions run. It reduces errors and inconsistent behavior when records are changed or removed, improving day-to-day reliability across approvals, documents, knowledge, mail, signing, CRM, and VoIP workflows.

Task-2986237

Community: https://github.com/odoo/odoo/pull/100408

This update modernizes how several Odoo apps calculate and order mail-related interface data behind the scenes. It should make the codebase easier to maintain while keeping the user experience largely unchanged.

Task-2985304

Community: https://github.com/odoo/odoo/pull/100313

This update introduces a shared public messaging bundle used by features such as Documents, Knowledge, VoIP, and live chat. It helps public-facing messaging experiences load the right components more consistently, improving maintainability and the user experience.

Task-2990182

Community: https://github.com/odoo/odoo/pull/100585

Signature requests using SMS or itsme no longer block signers when the company has run out of required authentication credits. Instead, signing can continue while the requester is warned about missing or low credits so they can top up or resend if stronger authentication is needed.

When an instance doesn't have IAP credits for SMS (or now for itsme) but still
uses an SMS/itsme-enabled role in a signature request, the signatory is locked.
This is overall a bad experience. This commit improves this by making the lack
of credit invisible to the signatory: if they're supposed to identify by SMS
or itsme but the database doesn't have any credit anymore, the signature
proceeds as normal but we warn the user who requested the signature of the
issue, so that they may act upon it: either they decide that the extra
authentication was not really necessary, or they think it is and they can
request the signature again after buying credits.

We also want to warn users about low credits in advance so they can avoid the
situation in the first place.

task-2963665

The consolidation reporting interface has been modernized to use Odoo’s newer web technology. This should make the dashboard and move line views easier to maintain while preserving existing business workflows.

The signature field used in Sign has been updated as part of a behind-the-scenes modernization. Related automated checks were adjusted so the signing experience continues to work reliably for users.

Forward-Port-Of: odoo/enterprise#31445

Forward-Port-Of: odoo/enterprise#31445

The button on follow up reports does not change color when displaying next follow up. Steps: - With two Customers Invoices in need of action in follow up reports - Select the first one and do an action (send email) - Mark as Done -> On the next follow up, the button Send Email didn't change color, it should be back to primary. Remove the class 'btn-primary' when displaying the next follow up. opw-2844518 Forward-Port-Of: odoo/enterprise#31510 Forward-Port-Of: odoo/enterp

The button on follow up reports does not change
color when displaying next follow up.

Steps:

- With two Customers Invoices in need of action
  in follow up reports
- Select the first one and do an action (send email)
- Mark as Done
-> On the next follow up, the button Send Email didn't
   change color, it should be back to primary.

Remove the class 'btn-primary' when displaying the next
follow up.

opw-2844518

Forward-Port-Of: odoo/enterprise#31510
Forward-Port-Of: odoo/enterprise#28623

Main - Do not create cash basis entries on non-cash-basis Company The fixing of this test is made in order to properly test CABA Due to changes in https://github.com/odoo/odoo/pull/94617 Forward-Port-Of: odoo/enterprise#29572 Forward-Port-Of: odoo/enterprise#29257

Main
-
Do not create cash basis entries on non-cash-basis Company

The fixing of this test is made in order to properly test CABA
Due to changes in https://github.com/odoo/odoo/pull/94617

Forward-Port-Of: odoo/enterprise#29572
Forward-Port-Of: odoo/enterprise#29257