Original PR description

### Add `settling` and `deposit` orderlines : 
- Now in PoS when settling an order we want to see the list of the orders for which the customers have due with the remaining due amount for each order. Then we can select the order(s) we want to settle, and it adds orderlines with a ref to the settling order(s). We can also add basic orderlines to the order.
- For money deposit money we don't change the flow, so we're still redirected to the payment screen to complete the deposit, and we shouldn't be able to add any other orderlines to the order. That's why deposit orderline are only added to the order at the validation.
- From the backend we now have the details of `settling` and `deposit` orderlines.
- `settling` and `deposit` orderlines are excluded from tax computation, as these are not sales lines. But we wan't to see these lines on the receipt and invoices

community PR: https://github.com/odoo/odoo/pull/193372

task-id: 4342951

Original PR description

After this commit:
===
- The test order functionality is implemented, allowing users to test easily the entire UrbanPiper flow.
- Test cases have been added to ensure the order flow operates smoothly.

Task-4040543

Original PR description

- Hide the leave payroll state in the time off form view when the leave is cancelled.
- Ignore the cancelled leave to deffer when generating the payslips

task-4351775

Original PR description

This commit enhances the preparation display by splitting order by courses.
This allow the  kitchen to know when to prepare each course to ensure that the client do not wait too much.
	•	Orders remain marked as “Pending” until the course is fired.
	•	After firing, the displayed time reflects the elapsed time since the “fire” event, instead of the creation time.
Task: 4444501

Original PR description

In the tree view of the payslip model, we can do mass edit to create a journal entry. Before, we were able to perform this action on a paid payslip which does not make sense. Now we have an error message if we try to do it.

Task: 3874129

Original PR description

Before this commit:
When a user logged in with their notification_type set to inbox, they did not
receive notifications in their Odoo inbox for sign request documents,
even if they received mail notifications.

After this commit:
Users will receive notifications in their Odoo inbox for sign request documents
if their notification_type is set to inbox.

task-3995294

Original PR description

When you reduce the screen width or view the page on devices with
medium/small screens, the control panel button group rearranges itself
in an unsightly way (e.g. excessive button height).

It also looks like the Documents mobile view is too different from
the standard Odoo mobile view.

Medium breakpoint and below:
=======================

All actions of the selected documents are grouped together in a single
dropdown (in the control panel).

Small devices, portrait:
=================

We make the look and feel closer to the standard Odoo list view for
mobile, but we do it also for the kanban view as, in Documents, kanban
cards are selectable:
- The action dropdown for the selected documents takes the place of the
DocumentCogItemMenu.
- The list selection box floats to the top left of the navbar.
- The details panel toggler in the control panel navigation disappears.

task-4471881

Original PR description

Before this commit, we was using fuzzy search which was creating a score for each partner and then sorting the partners based on that score. This was causing error in search result.

Now we use exact match search which will search for the exact match of the search string in the partner name, phone, mobile, email, street, city, state, country, zip, vat, and barcode.

taskId: 4517586

Original PR description

Purpose:
--------
Currently, when posting a scheduled message failed due to an error,
the cron interrupts and will attempt to resend the message on each of its
subsequent runs and fail again, preventing any scheduled message to be
posted.

This commit changes the cron behavior to catch any exceptions raised during
message posting, notify the author of the message about the failure, and
delete the failed scheduled message. This prevents infinite retry attempts.

The notification to the author of the scheduled message contains the content
of the scheduled message. The rationale is that the posting might fail
because the user does not have access to the record it will be posted on
anymore, and won't be able to see the scheduled message again.

The scheduled messages will now be unlinked when unlinking the record on
which they are scheduled.

Task-4531402

Original PR description

Before this commit, for a portal user, the creation of an API key will always be valid for one day.

This commit adds the option of selecting a period for which the API key will be valid.

The periods proposed take into account of the user's group. Consequently, in the case of a portal user, the administrator must enter a maximum number of days for the portal group
(the `api_key_duration` field in the `res.groups` model).

opw-4414586

Original PR description

Steps to reproduce:
- Configure a product with a price of 229.
- Assign a tax to the product with the 'Included in Price' option enabled under advanced settings.
- Create a new Discount Program with the program type set to 'Discount Code'.
- Set a discount of  per order, using the same tax as the product.
- Create a sales order with the configured product.
- Apply the coupon code to the order.

Issue:
- The total amount of the sales order does not reduce to 0 as expected.
- The computed coupon discount amount is incorrect.

Cause:
- The case for handling tax-included pricing was not taken into consideration when calculating the discount.

Fix:
- Use the sum of line.price_total when tax-included pricing is applied to accurately compute the price_unit of the reward.

opw-4486030

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

Original PR description

Before this commit, only pointerup was listened and was on the global document. Now, the event is listened on the ownerDocument of the element.

Like that, if the element is inside an iframe, it will be correctly listened. The "drop" is also added to the listened events, because sign doesn't use the draggable hook of owl, instead it uses the vanilla drag and drop system of javascript.

The dropzone shown during an onboarding tour is also fixed and takes into account the offset of the iframe in the top document.





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

Original PR description

When the Arabic language was selected, the PoS Restaurant module would error due to date formatting using Arabic numerals. This commit forces Latin digits in the date format to prevent the error.

opw-4544010

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

Original PR description

Steps:
- create a BOM for product A: component product B, ration 1.0, lead time 1 day
- put 4 as the on-hand qty of product A
- in the MPS, create records for products A & B with manufacture route for product A
- put 6 as the forecasted demand of product A  on the 2nd period or further
(this is so that the indirect demand of B is shown on the previous period)

Issue:
The indirect demand of product B will be 6 instead of 2 (6-4). This is because it uses `date_stop` with the lead time, see https://github.com/odoo/enterprise/pull/70232

Fix:
Subtract the starting qty from the indirect demand qty for the corresponding subproduct.
This is to make sure that the real `subproduct_indirect_demand` is compared to the
'ratioed' `replenish_qty` of the subproduct when selecting the date to use.

task 4381021

Original PR description

After this commit https://github.com/odoo/enterprise/commit/574d608b21199d5590d2335f4360a0a6470d1257, The workflow actions have been removed and replaced
by server actions and this PR is responsible for handling the migration of
workflow actions into server actions.(see https://github.com/odoo/upgrade/pull/6729)

```
AttributeError: 'int' object has no attribute 'create_document_from_attachment'
```
We created server actions sending to `journal_id` as `int` when migrating
dbs to 18.0. While the method originally supported only recordsets,
it's actually convenient to support `int`s here to avoid browse in the action
(more readable and more accessible to end-users).

opw-4453249

Original PR description

Since https://github.com/odoo/enterprise/commit/b198b60d337d2ea6a5d17872fb621322df57a20f get_invoiced should also return the invoice linked with the subscription based on the field account.move.line.subscription_id.

Unfortunatly, if the query based on sale_line_ids found no invoice for a given origin_order_id, the invoice found based on subscription_id were not added.

This can easily happen when the invoice are read by a user (for example odoo bot) that doesn't belong to the company of the invoice.

Solution: Invoice by origin_order_id should come from the result of the query + move_by_origin

Original PR description

If a warehouse has multi-steps deliveries, the actual demand of a product only takes the real outgoing move into account: the move that goes directly to the customer location.

Since moves are not created in advance anymore, we need to take the earlier moves in the chain into account instead while making sure that we only use a single move at a time.

The move used will be the last created in the chain, the one without `move_dest_ids`.

task 4510137

Original PR description

Steps to reproduce:
CRM > Sales > Teams > Pipeline > Graph View >Insert Into Spreadsheet

=> Boom: Name 'active_id' is not defined.

The action context contains a dynamic value, which needs the *current* to be evaluated.

Task: 4548431
opw-4491590
opw-4500397