This update adjusts the XPath expressions used in the Website Builder template to align with recent changes made in the Odoo community version. This ensures consistent and accurate rendering of the website, resolving potential display issues. It's a routine maintenance update to maintain website functionality.

Adapt the XPath to the XML changes in community for the website.WebsiteBuilder template.

task-6251151

This update enhances the Odoo system's ability to handle new analytic plans. Specifically, it ensures that newly created plans are correctly reflected in the user interface, mirroring a similar improvement for companies. This change improves the overall usability and accuracy of analytic planning.

The views need to include the newly created field on `account.analytic.line` and other models inheriting `analytic.plan.fields.mixin`.

This is based on the same service for `res.company`: `reloadCompany`

Forward-Port-Of: odoo/odoo#270789

This update changes the unit of measure for the 'Flour' product in the Point of Sale system to kilograms. This adjustment is necessary to properly configure product weighing, particularly for compliance with a specific certification (l10n_eu_iot_scale).

This small PR sets the "Flour" product's units of measure to kilograms.
This helps to configure the weighing of the product, especially for the l10n_eu_iot_scale cert

Forward-Port-Of: odoo/odoo#270508

This update enhances the accuracy of timesheet suggestions generated by the Timesheet Assistant Manager. The changes address minor issues with the assistant's recommendations, ensuring more reliable time tracking for project teams. This improves efficiency and data integrity within the Odoo Enterprise system.

This commit's purpose is to add a few bugprovement to the timesheet assistant manager. Those imp concerns mostly the timesheets suggested by the assistant manager.

task-6179842

This update enhances the Odoo system's ability to handle new analytic plans. By mirroring a similar process used for companies, the system now automatically refreshes the web client when a new analytic plan is created, ensuring data accuracy and a smoother user experience. This change improves the overall efficiency of managing analytic data.

The views need to include the newly created field on `account.analytic.line` and other models inheriting `analytic.plan.fields.mixin`.

This is based on the same service for `res.company`: `reloadCompany`

Forward-Port-Of: odoo/odoo#270789

This update streamlines the process of printing preparation tickets from the kitchen within the Point of Sale system. By consolidating common code, the system avoids duplication and ensures a more efficient workflow. This change enhances the speed and reliability of order fulfillment.

In this commit:
-------------------
- Moved common internally used methods to shared logic to avoid duplicating
the same code multiple times

task: 6131467
Enterprise PR: https://github.com/odoo/enterprise/pull/118286

This update changes the unit of measure for the 'Flour' product in the Point of Sale module to kilograms. This adjustment is necessary to properly configure product weighing, particularly for compliance with the l10n_eu_iot_scale certification, ensuring accurate product tracking and reporting.

This small PR sets the "Flour" product's units of measure to kilograms.
This helps to configure the weighing of the product, especially for the l10n_eu_iot_scale cert

Forward-Port-Of: odoo/odoo#270508

This update ensures that new analytic plans are correctly reflected in the Odoo system after creation. It mirrors a recent change for companies, streamlining the process and preventing data inconsistencies. The change updates views to include new analytic plan fields, enhancing usability.

The views need to include the newly created field on `account.analytic.line` and other models inheriting `analytic.plan.fields.mixin`.

This is based on the same service for `res.company`: `reloadCompany`

Forward-Port-Of: odoo/odoo#270789

This update enhances the accuracy of Belgian payroll tax calculations by providing more flexible options for tax withholding and ensuring calculations are based on the correct withholding tax amount, not the taxable salary. It also adds new features like a total tax target option and clarifies calculation methods for users, improving overall payroll management.

The percentage option was previously computed on the taxable salary instead
of the withholding tax amount. Also, a total guaranteed tax ceiling option
and a net salary safety cap were missing.

 - Change % option calculation to scale against withholding taxes (PP).

 - Rename '€/month' option to '€ extra/month'.

 - Add '€ in total /month' option to pay a target total tax amount.

 - Add descriptive help messages to clarify calculation methods for users.

 - Cap the deduction automatically to never exceed available taxable salary.

Task-ID: 6326856

This pull request includes several improvements to the planning module's field service functionality, focusing on better organization, user experience, and feature control. Key changes include reordering slot states for improved visual clarity, streamlining field service settings, and enhancing the 'My Planning' menu for internal users.

This update simplifies the payroll offboarding process by hiding irrelevant fees and preventing duplicate payslip generation. The system now intelligently handles holiday attest requests, avoiding errors caused by recent hires and ensuring a smoother workflow for HR staff.

First, the "Termination Fees" generation button is now hidden if the employee fully works their notice period. Since these fees are not legally applicable in this scenario, hiding the button removes visual clutter and prevents HR officers from generating invalid payslips by mistake. Action names have also been refined to provide clearer terminology.

Secondly, the generation logic for both termination fees and holiday attests has been updated to be idempotent. Previously, clicking the buttons multiple times would spam the system with duplicate draft payslips. The logic now intercepts the creation process: if a non-cancelled payslip already exists for the target structure and period, the system acts as a smart redirect and simply reopens the existing record(s).

Finally, the system now validates the employee's first contract date before attempting to generate an N-1 holiday attest. If the employee was hired in the current year (Year N), the N-1 attest generation is entirely skipped, preventing the creation of empty, nonsensical documents that would otherwise require manual deletion.

task-6296066

This update enhances the initial setup of the Point of Sale (POS) system by incorporating configuration and session IDs. These IDs allow the system to correctly identify and operate within specific store environments, improving accuracy and functionality. This change primarily impacts the enterprise and IoT POS modules.

*: l10n_it_pos

In this commit:

-  Add `pos_config_id` and `pos_session_id` to the global `odoo` variables initialized in `setupPosPrepDisplayEnv`.
- Use `self_ordering_mode` from the global `odoo` variables to determine whether the config is a kiosk configuration.

Task-6190644

This update enhances data security by preventing sensitive payroll information (like wages and costs) from being visible to unauthorized users. A recent change in how tracking messages are generated made previous security controls ineffective. This fix ensures only payroll team members can access these critical details.

When a new version is created from the salary configurator, a tracking message summarizing field changes is posted on the employee chatter. This message may contain sensitive payroll information such as wage and yearly cost, which should not be visible to users outside the payroll group.

Previously, all tracking messages on hr.employee were visible to any user with access to the employee record. After the mail tracking refactor introduced in task (3645865) (https://www.odoo.com/odoo/project/1251/tasks/3645865), tracking values are now rendered directly into the message body, making the old field-level filtering mechanism no longer applicable.

To restore payroll visibility restrictions:
* Tracking values linked to payroll-restricted fields are separated from regular tracking values during `_track_log`.
* Payroll-sensitive tracking values are posted in a dedicated tracking message using the subtype `mt_hr_payroll_sensitive`.
* Regular tracking values continue to use the standard tracking flow and remain visible to all users with access to the employee chatter.
* Employee chatter message fetching is overridden to hide payroll-sensitive messages from users outside `group_hr_payroll_user`. A test was also added to ensure payroll-sensitive tracking messages remain hidden from non-payroll users.
Task: 4985543

This update ensures that internal users can always see tickets they've been assigned to within the customer portal, regardless of their company access. Previously, this wasn't possible, creating a gap in internal support workflows. This change improves internal team efficiency and visibility.

Show the internal ticket user if assigned to a ticket as a customer, even if no access to the company this ticket belongs to.

Adjust the domain of filtering tickets to show the assigned ticket to him in the portal.

Task-4049642

This update automatically sends emails to Odoo companies when Stripe restricts a connected account due to KYC requirements. It proactively alerts businesses to potential issues with their Stripe accounts, ensuring they address necessary documentation updates promptly. This prevents disruptions to expense processing and maintains compliance with Stripe's policies.

When a company tries to create a connected account, some official documentation need to be submitted to Stripe. Stripe takes care of the KYC steps and might restrict some account which don't meet the requirements. Odoo receives the details about the error and the date of the restriction. This task aims at sending automatic emails to the said companies to let them know that they need to fix the identified issues. 
task: 5441662