Appointment booking now saves attendee details in the browser after form confirmation, so people without an existing contact profile do not need to re-enter the same information. This makes rescheduling, canceling and rebooking appointments faster and reduces repeated data entry.

Purpose
=======
Prevent the attendees without partner data from having to refill
their info the next time they're booking an appointment.

Specification
=============
Saving their data in the local storage at form confirmation to
autofill the form in case the appointment is canceled/rescheduled
or another appointment is booked.

Task-3594746

Users opening barcode scanning from the Barcode app main menu or operations views now see a manual barcode dialog first instead of the camera opening immediately. This lets them type a barcode when needed, still use the camera from the dialog, and receive a clear notification if camera access is unavailable.

Before this commit, clicking on the barcode image to scan opened the camera directly.

Now it opens the manual barcode dialog where the user can enter the barcode manually or use the camera.

Users can now move eligible shared Knowledge articles directly into the shared section when those articles are shared with at least one external partner. This preserves partner access during the move, reducing friction when reorganizing shared content.

Purpose:
-
Previously, the shared section allowed dropping an article only if it was moved under another shared article or if the article being moved was already a shared root article.

With this commit, dropping an article into the shared section is permitted as long as this article is shared with at least one partner (excluding the user initiating the move and internal permissions, but including inherited permissions).

In the case where a partner had access to the moved article through access inheritance, a new member will be created for this article so that this partner keeps his read/write access on this article.

Task-3603579

Project task progress and overlap warnings now use allocated hours instead of only start and end dates. This gives managers a clearer view of team workload across multiple projects and reduces false overload warnings, while still handling field service tasks with their specific scheduling rules.

Before this commit, the progress bar values were calculated based on the
task's start and end dates. This method proved inefficient for task
planning, as it didn't account for the possibility of a user being
assigned to multiple projects concurrently. For example, if a user had
a 40-hour work week, divided between 10 hours on Project A, 15 hours on
Project B, 5 hours on Project C, and 10 hours on Project D, the
previous system would inaccurately indicate resource overload and
potential task conflict.

With this latest update, progress bar computations are now based on the
actual allocated hours, providing a more accurate reflection of task
distribution. Additionally, if a task's end date extends beyond the
Gantt view's boundaries, the progress bar values are adjusted to
represent only the visible portion of the task, which aligns with the
percentage of the task that is actually visible.

Moreover, overlapping warning are now computed based on allocated hours
as well. The condition for a conflict is that the combined allocated
hours are larger than the workable hours of the user the planned dates.
This modification does not apply the field service tasks :

    Unlike other tasks, fsm tasks overlap in two scenarios:
        1. When the combined allocated hours of an fsm task and
            a normal task exceed the user's workable hours.
        2. When two fsm tasks have overlapping planned dates.

    Example:
        - Task A (normal) conflicts with Task B (fsm) if their combined
        hours > user's workable hours. Both have 1 conflict.
        - Introduce Task C (fsm) with no allocated hours (no conflict
        with Task A) but same time period as Task B.

        Result => Task A has 1 conflict, Task B has 2 conflicts, Task C
        has 1 conflict.

taskid:3349378

Payroll dashboard warnings can now be configured to better match each company’s needs and installed payroll features. This helps payroll teams see more relevant guidance and reduces one-size-fits-all messages on the dashboard.

The obsolete setting for choosing a down payment product has been removed because it has not been used since Odoo 16.2. Down payments now rely on the standard accounting flow, reducing configuration clutter and avoiding confusion for sales and subscription users.

Since version 16.2, the Down Payments setting became obsolete. Dead field, never used.

Odoo: https://github.com/odoo/odoo/pull/145887
Upgrade: https://github.com/odoo/upgrade/pull/5430

Task: 3618096

The appraisal app now presents readiness as a clearer status, with updated status colors and a new Ready filter. Employee avatars were removed from the appraisal view to simplify the interface and help users focus on appraisal progress.

The commit message summary is a concise and clear representation of the
changes made in the commit.

  -  Changed the color of the status.
  -  Remove the employee avatar.
  -  Converted the 'ready' banner into a state.
  -  Added a filter 'Ready'.
task - 3500932