This update adds the delivery address to the TicketScreen in Point of Sale, making it easier for staff to quickly see and use customer addresses when scheduling deliveries. This enhancement streamlines the delivery process and improves order accuracy by providing all necessary address information directly on the screen.

In this commit:
===============
- Added address details on the TicketScreen when the order preset identification type is `address`.
- This helps to easily see the delivery address while scheduling the delivery.

Task-5974595



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

Forward-Port-Of: odoo/odoo#257302
Forward-Port-Of: odoo/odoo#251389

This update automatically sets the first available printer as the default for Point of Sale transactions. Previously, users had to manually select a printer, and this change simplifies the process. Additionally, restrictions have been added to prevent incorrect printer configurations, ensuring data integrity within the POS system.

Following this commit:
=====
- Set first printer as default printer from the list configured.
- Updated the help tooltip.
- Added placeholder "None" to field product_categories_ids.
- Restrict quick create for `receipt_printer_ids` and 
`default_receipt_printer_id` for pos.config and 
res.config.settings views

task-5494313

Forward-Port-Of: odoo/odoo#246448

This update simplifies the process for users experiencing issues downloading the SSL certificate. The homepage now displays a clear warning message, eliminating the need to manually check logs and reducing potential user frustration. This improves the overall user experience and troubleshooting.

We improved the certificate status warning displayed on the homepage to avoid having to check the logs to know what went wrong while downloading the SSL certificate.

Forward-Port-Of: odoo/odoo#232670
Forward-Port-Of: odoo/odoo#232471

This update adds more thorough tests for the longpolling functionality within Odoo Enterprise. Specifically, the tests now verify how the system handles network errors, ensuring a more reliable response when connectivity issues occur. This improves the overall stability and robustness of the IoT integration.

This commit adds tests for the `onMessage` method of the longpolling JS class, and in particular tests the recently added behaviour where the polling request returns an 'unreachable' result when a network error occurs.

This update automatically removes 'Request' documents when the related record (like a Lead) is deleted. Previously, these documents lingered uselessly after a record was removed, creating confusion. This change improves data cleanliness and efficiency.

Scheduling an "Upload Document" activity for a record (e.g., a Lead) creates a "Request" document that is linked to that record.

Previously, the request document would remain after the record was deleted, leaving it meaningless without its related record. With this change, the request is automatically archived (moved to the Trash) when its related record
is removed.

Note that if a file has already been uploaded for the request, no further action is taken here: the fulfilled document request will be deleted if the record does not inherit from `documents.unlink.mixin` if we delete the record "owning" the attachment of the document; otherwise the document request will be moved to the Trash.

Task-5259439

This update prevents students and PFIs from being assigned BIK (Bank Identification Numbers) that are not permitted under Belgian tax regulations. This ensures compliance with local tax laws and reduces the risk of errors related to incorrect BIK assignments.

Hiding the BIKs that cannot be given to students or PFIs.

task-6172231

This update enhances the user experience by adding options to set date fields as read-only and control their alignment directly within the form view. This provides greater flexibility and accuracy when entering date information, streamlining data entry processes.

Before:
- Read-only and alignment option was not available for date field in form view.

After:
- Read-only and alignment  option is now visible for date field in form view. this will allows users to set date fields as read-only and control their alignment directly from the form view.

task-6179970

This update adjusts the tax report handlers to align with recent changes in the tax tag system used within Odoo. This ensures accurate reporting of taxes, reflecting the latest tax regulations and improving the reliability of financial data. It's a necessary update related to a broader change in the tax tag definitions.

Before this pr:
- The tax tags used in the report_grid_map in custom tax report handlers are codified.

After this pr:
- So now we are updating the report_grid_map according to the change in the tax tags.

Related Com PR: https://github.com/odoo/odoo/pull/255802

Task-6008302

This update adjusts the COA and TB report templates to align with Mexican government reporting specifications. This ensures accurate and compliant financial reporting for Mexican businesses using Odoo Enterprise. The changes were made to improve consistency and meet regulatory requirements.

Reordered COA and TB attributes to be more according on what government expects on those reports

task-5422228

Forward-Port-Of: odoo/enterprise#115374

Odoo now supports the new alphanumeric CNPJ format required by the Brazilian government to accommodate a growing number of businesses. This update replaces an outdated validation method, ensuring Odoo can accurately process Brazilian company registrations as they transition to this new format. This change avoids dependency issues with a third-party library.

Purpose: The Brazilian Federal Government, through the Brazilian Federal Revenue Service (Receita Federal do Brasil), is implementing the alphanumeric CNPJ to address the imminent depletion of its capacity to generate new CNPJ numbers. The current, exclusively numeric model is approaching its limit. The transition to a format that includes letters and numbers expands the number of possible combinations, ensuring the future availability of registrations for new companies. With the government expanding the CNPJ numbers, we need to implement a solution to support the alphanumeric CNPJ that will be issued starting July 2026.

Current Behavior: The method, `is_valid,` from stdnum is currently used to determine whether the CNPJ is valid or not. This is now considered an outdated method to determine the validation.

Changed Behavior: The new validation logic by stdnum, found here https://github.com/arthurdejong/python-stdnum/commit/d3ec3bd7fefe0d0a708b6594a66de28777eb9b8d, is patched into `check_vat_br.` The reasoning for patching this rather than calling stdnum is because using stdnum will cause library dependency issues for older versions of Odoo.

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

Forward-Port-Of: odoo/odoo#260516