This update enhances the ability to retrieve information from related records (o2m relationships) when sending sign requests. Previously, limitations prevented accessing additional data, but this change enables greater flexibility and data access for sign workflows. This improves the functionality of the sign process.

The class `SignerX2Many` is inheritable, but if we need another value from the o2m, we can't use it because the `signerX2Many` is not exportable.

Enable `signerX2Many` customization, allowing more fields to be read from the `sign.send.request.signer` model.

Forward-Port-Of: odoo/enterprise#99977

This update clarifies the labeling of a field used when making salary adjustments within Odoo. The change ensures users understand exactly where this input type is accessible, preventing confusion and streamlining the adjustment process. This improves the overall user experience for HR professionals.

This change ensures the label accurately reflects where the field is accessible and providing better clarity for users when working with salary adjustments.

Task: 5375187

Forward-Port-Of: odoo/enterprise#101065

This update enhances the handling of Chilean electronic invoices by ensuring folio numbers align with available CAF files. A new validation rule requires a valid owner document for certificates, improving data accuracy and compliance with SII regulations. These changes contribute to smoother invoice processing and reduced errors.

This pull request introduces improvements to the handling of Chilean electronic document sequences, enforces stricter validation for certificate data, and modernizes string formatting throughout the codebase. The most significant changes focus on ensuring that document folio numbers are correctly managed in accordance with available CAFs, making the certificate model more robust, and updating code style for clarity and consistency.

This improvement is mostly made because CAFs have expiration dates and fixed folio numbers. If the expiration date is reached but the folios were not fully consumed, the system will try to generate a document with following number in the sequence but an error will be raised because that number belongs to an expired CAF, althought the user had already uploaded a new CAF.
To fix this, whenever the system looks for the highest number to set to a document, it previously check if that number is between the folio numbers of a valid CAF file.

### Chilean electronic document sequence management

* Added `_get_last_sequence` method to `account_move.py` to ensure that the folio number used for Chilean electronic documents (DTE) is valid and corresponds to an available CAF. If no CAF is available for the current folio, the sequence is reset using the document type's prefix and starting number.

### Certificate model validation

* Made `subject_serial_number` a required field in the `Certificate` model, enforcing that every certificate has a valid owner document and improving data integrity. We made this change to prevent the field being empty after loading the certificate in Odoo, since it is required by the SII to validate invoices.

Forward-Port-Of: odoo/enterprise#92208

This update significantly speeds up the process of retrieving product information, particularly when configuring products. By using a batch processing method, the system now completes this task in just 0.8 seconds, compared to 2.7 seconds previously – a 70% improvement. This change enhances the user experience and overall system performance.

Performing read operations on attributes and values in batch yields a significant performance improvement and is standard practice.

Tested with 60 attributes and 8000 values: went from 2.7s to 0.8s (-70%)

No task


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

Forward-Port-Of: odoo/odoo#237037
Forward-Port-Of: odoo/odoo#235170

This update automatically opens the Return creation wizard when generating reports with no existing returns, eliminating the need for users to manually re-enter information. This improves efficiency and reduces the time spent on report generation, particularly for Intrastat and standard reports.

Currently, accessing the 'Returns' view from a report with no existing
returns shows an empty list.
The user then has to click 'New' and manually re-enter values like
dates and the report itself, which are already known.

This commit improves the workflow.
If no returns exist for the current report, the system will now
automatically open the Return creation wizard pre-filled with the
corresponding default values derived from the report context.
This removes the redundant data entry step for the user.

task-5155832

This update enhances the reliability of our access rights tests by replacing manual data manipulation with a more robust method. Previously, tests were fragile and prone to breaking due to changes in Odoo's data models. This change ensures tests are more stable and accurately reflect access control rules.

In our tests for access rights, we manually do CRUD operations to check them. However, this approach is difficult to maintain and highly susceptible to changes in model fields. Therefore, we are switching to using has_access function for more robust verification.