Users can now create CRM leads directly from eligible Facebook, Twitter, and LinkedIn posts or comments. This helps sales teams turn social engagement into follow-up opportunities faster, while clearer campaign source and medium names improve reporting.

To allow user to generate a lead in the CRM, a 'Generate Lead' option has been
added in the dropdown menu associated to each comment and post.

This option is available when the user has the appropriate rights and when he
is not the author of the post/comment.

The generate lead feature has been implemented for:
- Facebook
- Twitter
- LinkedIn
But can be implemented for future media easily by following the same architecture.

Co-authored-by: Aurélien Warnon <awa@odoo.com>

Task ID: 2206496

The Belgian payroll process now avoids including archived employees when generating paid time off allocations. This prevents outdated employee records from affecting payroll-related leave generation and helps keep HR results accurate.

TaskID: 2393749

The website quick create menu now avoids repeating the same permission checks for different user groups. This reduces unnecessary requests and should make the content creation experience faster and smoother for eligible users.

Before, one request by groups, now we use a variable is_system / is_designer
to make only once the request.

This update reorganizes email-related templates across several Odoo Enterprise apps so they are easier for teams to find, maintain, and improve later. It also removes blank email templates that added clutter without changing normal business workflows.

PURPOSE

Clean organization of templates in odoo apps: mail.template records in data,
qweb templates (views) used directly in code, notably using post with view.
Purpose is to ease future improvements in posting based on templates.

Remove unused blank templates in crm and mail.

SPECIFICATIONS: TEMPLATES MOVE

  * move those templates in their own file to ease their discovering and
    maintenance;
  * put them into data (as those are not views even if it contains qweb)
  * guidelines are now :

    -> Qweb templates should be in data/mail_templates.xml;
    -> mail.template records should be in data/mail_template_data.xml;

  * put their declaration in no update when not done if template has no
    technical code or complex dependency on underlying code;
  * move found mail data (mail.message.subtype or mail.activity.type) records
    in a mail_data file that should contain only "core" records linked to mail;

SPECIFICATIONS: REMOVE BLANK TEMPLATES

Crm and mail hold a blank template that adds no real value. Its purpose was to
give a base for salesmen to perform a mass mailing on leads. Using a template
and its action menu entry it was possible to launch a mail composer in
mass mail mode on leads.

However template itself is not necessary. Same goal can be achieved with
a standard action. As template was blank and creating noise we can remove
it and simplify available templates.

LINKS

Task ID-2375767
COM PR odoo/odoo#61814
ENT PR odoo/enterprise#14775
UPG PR odoo/upgrade#1936

Forward-Port-Of: odoo/enterprise#14885 Forward-Port-Of: odoo/enterprise#13815

Forward-Port-Of: odoo/enterprise#14885
Forward-Port-Of: odoo/enterprise#13815

Field parameters validation was introduced some months ago and recently fixed in https://github.com/odoo/odoo/pull/60402 but some modules have not been covered by the fix, probably due to runbot restrictions. This PR fixes some wrong parameters in l10n_es localization. * attribute length doesn't exist, should probably be size instead * attribute relation has no sense on o2m fields COM PR: https://github.com/odoo/odoo/pull/62335 ENT PR: https://github.com/odoo/enterprise/pull/14982 Fo

Field parameters validation was introduced some months ago and recently fixed in https://github.com/odoo/odoo/pull/60402 but some modules have not been covered by the fix, probably due to runbot restrictions.

This PR fixes some wrong parameters in l10n_es localization.

* attribute length doesn't exist, should probably be size instead
* attribute relation has no sense on o2m fields

COM PR: https://github.com/odoo/odoo/pull/62335
ENT PR: https://github.com/odoo/enterprise/pull/14982

Forward-Port-Of: odoo/enterprise#14982

Invoices with invoice dates in the past were always reported in Taxcloud as if they happened when the user clicked "Post". This results in incorrect tax reports in Taxcloud. Taxcloud reps have confirmed to us that we should instead do our requests with the invoice date. opw-2335987 Forward-Port-Of: odoo/enterprise#14907

Invoices with invoice dates in the past were always reported in
Taxcloud as if they happened when the user clicked "Post". This
results in incorrect tax reports in Taxcloud.

Taxcloud reps have confirmed to us that we should instead do our
requests with the invoice date.

opw-2335987

Forward-Port-Of: odoo/enterprise#14907

Forward-Port-Of: odoo/enterprise#14916

Forward-Port-Of: odoo/enterprise#14916

Issue - Create 2 companies - Enter and save some products linked to either company 1 or company 2 - Let's say you want to receive some products (so create a Receipt) - Open the barcode app, click on Operations, and then on the receipt you want to process - Try to add a product Product related to a specific company are not in the list. Cause company_id inside the product domain has quotes around it : ('company_id', '=', 'company_id') Solution Remove quotes : ('co

Issue

	- Create 2 companies
	- Enter and save some products linked to either company 1 or company 2
	- Let's say you want to receive some products (so create a Receipt)
	- Open the barcode app, click on Operations, and then on the receipt you want to process
	- Try to add a product

	Product related to a specific company are not in the list.

Cause

	company_id inside the product domain has quotes around it :
	('company_id', '=', 'company_id')

Solution

	Remove quotes :
	('company_id', '=', company_id)

opw-2389423

Forward-Port-Of: odoo/enterprise#14969
Forward-Port-Of: odoo/enterprise#14945

In the mobile apps, the JS date picker is replaced by a native one. But after properly setting a new value in a date/datetime field AND focusing another field, the newly set value's format change to the JS library's (TempuDominus) default. Actually even if the JS date picker isn't displayed (or even instantiated), some event listeners (i.e. click, blur, keydown...) are still set on the `window` global object. Those listeners only handles event emitted from elements with the 'datetimepic

In the mobile apps, the JS date picker is replaced by a native one. But
after properly setting a new value in a date/datetime field AND focusing
another field, the newly set value's format change to the JS library's
(TempuDominus) default.

Actually even if the JS date picker isn't displayed (or even
instantiated), some event listeners (i.e. click, blur, keydown...) are
still set on the `window` global object. Those listeners only handles
event emitted from elements with the 'datetimepicker-input' class on
them.

Outside the mobile apps, we rely on these events to ensure proper
formatting is applied. But in the apps, we disable completely the
library... or so we thought!

This commit removes the 'datetimepicker-input' class from the
DateWidget's elements to ensure the library's event listeners don't
handle them.

Note: sadly as those listeners are registered at library's load time, we
have no proper way to remove them entirely in the mobile apps.

Forward-Port-Of: odoo/enterprise#14904
Forward-Port-Of: odoo/enterprise#14882

Before this commit, the chatter of the form view was wrapped inside an extra unnecessary div, this caused an issue with an heuristic for the display of the chatter. task-2363437 Forward-Port-Of: odoo/enterprise#14793

Before this commit, the chatter of the form view was wrapped inside
an extra unnecessary div, this caused an issue with an heuristic for
the display of the chatter.

task-2363437

Forward-Port-Of: odoo/enterprise#14793

When the user attempts to add the current app to his device's home screen, an error is displayed. Steps to reproduce: - Open an app - Go to the burger/user menu and open it - Click on "Add to home screen" and a traceback occurs Following the refactoring of the HomeMenu on enterprise, the menu's data aren't exposed directly any more from the WebClient. This commit fixes it by properly accessing them from the WebClient's Menu. Task ID: 2388619 Forward-Port-Of: odoo/enterprise#

When the user attempts to add the current app to his device's home screen,
an error is displayed.

Steps to reproduce:

- Open an app
- Go to the burger/user menu and open it
- Click on "Add to home screen" and a traceback occurs

Following the refactoring of the HomeMenu on enterprise, the menu's data
aren't exposed directly any more from the WebClient.

This commit fixes it by properly accessing them from the WebClient's
Menu.

Task ID: 2388619

Forward-Port-Of: odoo/enterprise#14841

Avoid usage of Diffie-Hellman ciphers, because newer version of openssl (at least version 1.1.1) do not allow the ones *.afip.gov.ar servers are using (with error "dh key too small"). More information related to this error: * https://wiki.debian.org/ContinuousIntegration/TriagingTips/openssl-1.1.1 * `https://github.com/WhyNotHugo/django-afip/pull/50` * https://stackoverflow.com/questions/38015537/python-requests-exceptions-sslerror-dh-key-too-small opw-2347939 opw-2351013 opw-236597

Avoid usage of Diffie-Hellman ciphers, because newer version of openssl
(at least version 1.1.1) do not allow the ones *.afip.gov.ar servers are
using (with error "dh key too small").

More information related to this error:
* https://wiki.debian.org/ContinuousIntegration/TriagingTips/openssl-1.1.1
* `https://github.com/WhyNotHugo/django-afip/pull/50`
* https://stackoverflow.com/questions/38015537/python-requests-exceptions-sslerror-dh-key-too-small

opw-2347939
opw-2351013
opw-2365971
opw-2366142

Co-authored-by: Nicolas Lempereur <nle@odoo.com>

Forward-Port-Of: odoo/enterprise#14249

WHY: chart of accounts may not be setup right after module installation Forward-Port-Of: odoo/enterprise#14943 Forward-Port-Of: odoo/enterprise#14925

WHY: chart of accounts may not be setup right after module installation

Forward-Port-Of: odoo/enterprise#14943
Forward-Port-Of: odoo/enterprise#14925

Applies to the PLM kanban's "Set cover image" action popup and to the account followup alerts. Before this commit the close icon was included in translated resources. For example, in Spanish the "×" had been turned into "&veces;" thus not rendering an icon anymore After this commit the close icon is not a translated text anymore and remains an icon across all languages task-2312878 Forward-Port-Of: odoo/enterprise#14209

Applies to the PLM kanban's "Set cover image" action popup and to the
account followup alerts.

Before this commit the close icon was included in translated resources.
For example, in Spanish the "×" had been turned into "&veces;"
thus not rendering an icon anymore

After this commit the close icon is not a translated text anymore and
remains an icon across all languages

task-2312878

Forward-Port-Of: odoo/enterprise#14209

When an application icon is missing from the filestore, the `apps` prop is not valid because `web_icon_data` is empty, but the `web_icon` is not a list of three elements as it still references an icon (`module,path`). The `backgroundColor` is then `undefined`, and in debug mode the prop validation fails and the page remains blank with a stacktrace. This could happen when the filestore is missing, for example if the database has been restored from a dump without a filestore. This commit make

When an application icon is missing from the filestore, the `apps` prop is not valid because `web_icon_data` is empty, but the `web_icon` is not a list of three elements as it still references an icon (`module,path`).
The `backgroundColor` is then `undefined`, and in debug mode the prop validation fails and the page remains blank with a stacktrace.
This could happen when the filestore is missing, for example if the database has been restored from a dump without a filestore.

This commit makes the script check that the third part is not `undefined` before using the `webIcon`, or fallbacks to the default icon if it is not the case.

Forward-Port-Of: odoo/enterprise#14792

o-spreadsheet 1.0.1 includes a few minor fixes. No breaking changes. See https://github.com/odoo/o-spreadsheet/releases/tag/1.0.1 Forward-Port-Of: odoo/enterprise#14850

o-spreadsheet 1.0.1 includes a few minor fixes. No breaking changes.
See https://github.com/odoo/o-spreadsheet/releases/tag/1.0.1

Forward-Port-Of: odoo/enterprise#14850

validate_batch can be used with multi records OPW #2335893 Forward-Port-Of: odoo/enterprise#13266 Forward-Port-Of: odoo/enterprise#13068

validate_batch can be used with multi records

OPW #2335893

Forward-Port-Of: odoo/enterprise#13266
Forward-Port-Of: odoo/enterprise#13068