This update introduces a new wizard that allows administrators to revert previously generated payslips. This provides greater flexibility in correcting payroll errors and ensures accurate record-keeping for Belgian companies using the Odoo Enterprise HR Payroll module. The change improves data accuracy and compliance.

Task: 6117478

This update prevents Odoo from crashing when the Barcode Lookup API returns a broken image URL. Previously, an invalid URL would cause an error. Now, the system safely ignores these errors, ensuring the 'Get Pictures from Barcode Lookup' action continues to function without interruption.

[FIX] product_barcodelookup: avoid crash on invalid image URLs
**Steps to Reproduce:**
-  Install Sales module.
- Configure a valid Barcode Lookup API key.
- Create a product without an image.
- Set a barcode whose returned image URL is broken or returns HTTP 404
  (e.g. `8426904171073`).
- Select the product and trigger the server action:
  `Action -> Get Pictures from Barcode Lookup`

Issue:

**During image fetching:**

-  Barcode Lookup API successfully returns product data and image URLs.
- `_get_image_from_url()` attempts to download the image.
- The image URL responds with HTTP 404.
- `barcode_lookup_request()` returns a dict for non-200 responses.
-  `_get_image_from_url()` assumes the response is always a `requests.Response`
   object and directly accesses:  `response.status_code`
- This causes: `AttributeError: 'dict' object has no attribute 'status_code'`

**Root Cause:**
- `barcode_lookup_request()` returns inconsistent response types:
     - `requests.Response` for successful requests
     - `dict` for failed requests
- _get_image_from_url() does not handle the dict response before accessing
   response attributes.

**Solution:**
- Make barcode_lookup_request() always return a One Response
  object.
- Move the response validation to the callers instead of returning custom
  dict objects.

**Result:**
- No RPC crash when image URLs are invalid or return 404.
- Broken image URLs are safely ignored.

**OPW-6200749**

Forward-Port-Of: odoo/enterprise#116925

This update resolves an issue that occurred when duplicating Odoo databases used for testing the German POS certification module. Specifically, the system now correctly handles the removal of identifying information (client_id and tss_id) during database duplication, preventing errors and ensuring proper functionality in test environments. This ensures consistent and reliable testing of the module.

In this commit:
--------------------
- On a duplicate database `client_id` and `tss_id` are removed so it works
as test in neutralized dbs without throwing errors.

task- 5457231

Forward-Port-Of: odoo/enterprise#104119

This update simplifies the tour selector within Web Studio. The previous logic was no longer needed due to a change in how the Kanban dropdown toggle is displayed. This adjustment ensures the tour selector functions correctly and efficiently, streamlining the user experience.

Since the visibility of the kanban dropdown toggle is now always visible when the media query 'pointer: fine' isn't met, in the case of this tour, it is no longer useful to check for the non visibility of the element in the selector.

task-6259816

This update ensures consistent behavior across Odoo by adapting how live chat and VoIP features are initialized. The change aligns with recent community updates, streamlining the process and improving the reliability of these core services.

The community counterpart of this PR removed the `onStarted` method as overrides should all use `initialize`. This commit adapts the enterprise modules.

community: https://github.com/odoo/odoo/pull/267160

This update fixes an issue where portal users were redirected to the wrong folder when accessing documents. The fix ensures that links from the Documents section correctly navigate users to the intended folder, improving the user experience. This was caused by a technical oversight in updating folder references.

# How to reproduce
- As admin, give access to folder X & folder Y to a portal user
- As that portal user, go to Documents, click on folder X and copy the page url
- Click on folder Y
- Paste the URL in the browser's search bar

# The problem
You are still in folder Y, even though the link should be to folder X.

# Cause
We forgot to keep `documents_init`' s `folder_id` (refactored into `user_folder_id`) in
https://github.com/odoo/odoo/commit/6bdcc357b195faa0aad8c05eac23aa0a762dd76b

opw-6132231

Forward-Port-Of: odoo/enterprise#116928

This update enhances the accuracy of vendor credit note reporting within the Odoo Enterprise system. Specifically, the system now prioritizes using the 'bill reference' when generating reports for vendor credit notes, ensuring more reliable data. This change maintains the previous fallback behavior for compatibility.

With this commit, we update the report to prioritise the bill reference for vendor credit notes while keeping the previous fallback behaviour

task-6235022

This update fixes a problem where payruns were incorrectly marked as cancelled after removing individual payslips. The change ensures payruns remain valid even after edits, preventing disruptions in payroll processing. This improves the reliability of payrun management.

Fixes the following bugs in payruns:

BUG 1:
- create a payrun, leave it in draft
- create a single payslip, add it to the previously created payrun. The payslip employee will appear in the payrun employee list
- for the previously created payslip, remove it from the payrun
- go back to payruns kanban view, the payrun will results as cancelled even if there still were other employee entries in it (the one defined at start)

BUG 2:
- create a payrun, leave it in draft
- create a single payslip, add it to the previously created payrun. The payslip employee will appear in the payrun employee list
- go on the payrun and clicking on the button "Off-Cycle" for the separately-created payslip This adds other employees not originally on the payrun

task: 6237460