Calendar invitation emails now avoid showing the automated OdooBot name as the meeting contact. This makes invitation messages look more natural and less confusing for recipients.

When the partner name of the meeting is 'OdooBot', change the sentence to prevent displaying 'OdooBot' in the mail.

Task-3544915

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

This update improves how manufacturing scrap forms keep related values up to date. It reduces the chance of inconsistent information when users edit scrap records, making the process more reliable without changing the overall workflow.

Task: 2709744

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

The customer rating search view has been reorganized to make common filters and grouping options easier to find. Labels and ordering were adjusted so teams using ratings, especially in project-related views, can review feedback more clearly.

Improvements are as follows:
- reordered the groups as follows: assigned to, helpdesk team, rating, customer,
  date inside search view > group by of customer rating.
- inside search view switch the position of helpdesk team and customer.
- added an attribute invisble to make sure that it only display on project

task-3475466

Creating a to-do from the activity menu now uses the dedicated to-do activity type instead of a redundant reminder type. This reduces confusion for users and protects the default to-do activity type from being deleted or archived accidentally.

Before this commit, if we add todo from activity menu then it create a activity
with reminder type which is redundant with todo.
Remove reminder type activity from activity type and make to do activity type as
default when creating a todo from activity menu.

task-3196864

Mexico and Chile localization screens now show certain banking and partner fields only for companies in the relevant fiscal country. This reduces clutter and helps users in other countries avoid seeing fields that do not apply to their business.

This PR will hide some fields to other companies by adding fiscal country
codes to some model used in the mexican and chilean localization.

task: 3551098




---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Fields related to Mexican and Chilean electronic invoicing are now limited to companies with the matching fiscal country. This keeps screens cleaner for companies in other countries and reduces confusion from irrelevant localization options.

This PR will hide some fields to other companies by adding fiscal country
codes to some model used in the mexican and chilian localization.

task: 3551098

The Helpdesk customer rating search view has been reorganized to make common filters and grouping options easier to find. Users will see clearer ordering for grouping by assignee, team, rating, customer, and submission date, with the date label renamed to “Submitted on.”

Improvements are as follows:
- reordered the groups as follows: assigned to, helpdesk team, rating, customer,
  date inside search view > group by of customer rating.
- renamed Date into Submitted on.
- inside search view switch the position of helpdesk team and customer.

task-3475466

The Knowledge command palette now remembers whether a user is allowed to create new articles instead of checking repeatedly while they type. This reduces unnecessary server calls and should make search suggestions feel faster without changing normal permissions behavior.

When the user enters specific terms in the command palette, and there is no article matching those terms, the system will display a helper that allows the user to quickly create a new article with the provided name. The helper will only be shown if the user has the permission to create a new article in the database. To verify this permission, the system will perform an RPC call to the server each time the helper needs to be displayed.

In practice, it's highly unlikely for the user to lose the 'create' privilege between two searches. Therefore, one can cache the result of the RPC call that checks if the user is allowed to create a new article. Caching this result should reduce the number of RPC calls triggered when the user types something in the search bar.

To implement the caching mechanism, we will simply use the `memoize` utility function to cache the promise checking the user's 'create' privilege. The system will perform the RPC call on the first invocation, cache the promise, and reuse it for subsequent calls, thereby improving speed.

If the user loses the 'create' privilege between two searches, the system will display an access error if the user clicks on the helper. While this occurrence should be infrequent, it's not a major issue, as similar errors can also occur with the existing code.

task-3603346