Daily updates from Odoo
Wednesday, March 11, 2026
41 changes · master
New functionality added to Odoo
This update introduces a new 'Net Cost' salary rule for Saudi Arabia, addressing complexities in calculating employer contributions. It ensures accurate deductions from employee pay while correctly reflecting employer obligations, particularly for schemes like GOSI. This change improves payroll accuracy and compliance.
Original PR description
This PR introduces a new salary rule 'Net Cost' since setting appears_on_employee_cost_dashboard as True on the salary rule considers the sign on the rule, and for cases like the GOSI Employee Rule we need the sign to be negative to deduct from the employee but also increase the employer contribution amount. - adjusted provision rules to be part of a new category - adjusted remaining days to be allowance instead of company contribution - NET salary doesn't contribute to employer cost - New salary rule 'net cost' contributes to employer cost. Task-5894405 Forward-Port-Of: odoo/enterprise#106834
This update introduces two new Book of Accounts reports – Cash Receipts and Cash Disbursement Journals – specifically designed for Philippine businesses. These reports now accurately track cash flow by analyzing the General Ledger, addressing previous limitations that missed manual entries and in-transit funds, leading to more reliable financial reporting.
Original PR description
## [IMP] l10n_ph_reports: add cash receipt/disbursement report Adds two new Book of Accounts reports: - Cash Receipts Journal - Cash Disbursement Journal Instead of strictly filtering by `account.payment` links, these reports now derive cash flows directly from the General Ledger's liquidity lines (Bank, Cash, Credit Cards, and Outstanding clearing accounts) because it: 1. Catches manual journal entries that affect cash but lack payment records. 2. Captures in-transit funds sitting in Outstanding Receipts/Payments before bank reconciliation. 3. Categorizes transactions accurately by their actual GL impact (Debit = Receipt, Credit = Disbursement), inherently fixing edge cases like negative receipts (refunds). task-[5116323](https://www.odoo.com/odoo/project.task/5116323) Forward-Port-Of: odoo/enterprise#106260
This update adds a new field to stock picking records, allowing users to designate a driver specifically for the 'carta porte complemento' document. This replaces the previous driver field, streamlining the process for managing deliveries and ensuring accurate driver assignment for compliance requirements.
Original PR description
Added new operator field in picking to set the driver to be used at the carta porte complemento instead of the driver field in the vehicle and new button to allow set selected driver as the main one. task-5351444
Enhancements to existing features
This update restricts the ‘Working Schedule Change’ wizard to only Belgian companies, streamlining the process for users. It also removes a redundant field and improves the user interface by adding padding to the time-off warning alert, enhancing the overall user experience.
Original PR description
- Show the “Working Schedule Change” wizard only for employees belonging to Belgian companies. - Remove the “Post Change Contract Creation” field from the working schedule change wizard. - Add extra right padding to the warning alert in the time-off section for improved UI spacing. task-5367812 Forward-Port-Of: odoo/enterprise#109728 Forward-Port-Of: odoo/enterprise#101013
This update enhances the generation of WPS files for Odoo Enterprise companies in the UAE, focusing on compliance and user experience. Key changes include stricter data validation, improved bank account linking, and the ability to export WPS reports in Excel format, streamlining the payroll process.
Original PR description
This commit aims to make the generation of wps files for AE companies more compliant and intuitive for the user, by: - Updating string for l10n_ae_employer_reference field - Domaining the company's salary bank account to accounts that belong to the company - Enabling the export of xlsx wps report - Preventing negative values in EVP section of the wps file - Adding constrains to the employer code as per expected format - Changing the names of allowance inputs - Adding a new category for evp rules - Making sure clearing number is only 9 digits as per expected format task-5884696 Forward-Port-Of: odoo/enterprise#109902 Forward-Port-Of: odoo/enterprise#107218
This update enhances the planning module's user interface by repositioning buttons next to input fields for a cleaner look. Additionally, redundant icons within the kanban card have been removed to streamline the user experience. This change focuses on visual consistency and usability.
Original PR description
This commit improves the UI in planning, by using the o_input_box class around two fields. Instead of having a button right next to the input, the button now floats as a suffix at the right side of the input. Also, two icons were present in the kanban card, since the daterange field already contains an icon in readonly touch mode.
This update reduces the number of template options displayed in the planning view, improving the user interface's clarity and preventing visual clutter. The change limits the badges available to 8, addressing an issue where excessive template choices could overwhelm users. This enhancement focuses on a better user experience.
Original PR description
Add `badge_limit: 8` to the planning template autocomplete widget. **Task~5270283** **Related Community PR: odoo/odoo#252483**
This update enhances the visual appearance of consent emails sent to users when they sign up for Odoo Enterprise. The changes align the email layout with the latest Odoo Finance design standards, creating a more professional and consistent user experience. This improves brand perception and user satisfaction.
Original PR description
- updated consent email template layout as per current odoofin design task-5107776
This update enhances the visibility of VAT return status within Odoo, alerting users immediately when a file is rejected by tax authorities. Previously, errors were only logged in a chat window. Now, the return status will display a visual indicator, allowing for quicker identification and resolution of issues.
Original PR description
Many localisations require some returns (mainly: VAT return) to be sent by API to tax authorities. It frequently happens that the file is rejected by the authorities for xyz reasons. In that case, the response is logged in the return chatter but we should make the failure visual so users directly know that an issue occurred. For that, we'll allow the states widget to be colorful. Now localisation can add custom error messages and alert types and the widget will be colored accordingly and the error message will appear on hover. task-5365547
This update streamlines the process for depositing money at the point of sale. It now automatically selects the first available payment method, eliminating the need for users to manually choose one via a popup. This improves the user experience and speeds up the deposit flow.
Original PR description
### Before this commit: - Depositing money in POS always required selecting a payment method via a popup. - This added an unnecessary step to the deposit flow. ### After this commit: - Automatically select the first available payment method (excluding pay later), ordered by sequence. - Remove the payment method selection popup for deposits. Task:5927077 Related PR: - Community: https://github.com/odoo/odoo/pull/248565
This update optimizes the performance of bank statement processing by removing an unnecessary database field and adding an index. This reduces delays when retrieving and deleting bank statement information, leading to faster and more efficient operations for users.
Original PR description
[IMP] account_online_synchronization: Remove useless online_link_id on statement line The aim of this commit is removing the useless online_link_id field on bank statement line. It is a related…
[IMP] account_online_synchronization: Remove useless online_link_id on statement line The aim of this commit is removing the useless online_link_id field on bank statement line. It is a related stored many2one field without any index. It's leading on big database to big latency when we have try to delete the related object. As the field is now useless (online_account_id is sufficient), this commit delete it totally. no task id [IMP] account_online_synchronization: Add index on online_account_id for statement line The aim of this commit is to add a new index on online_account_id field for the bank statement line model. This is useful because the field is a many2one field used in different searches and in the allow the user to understand from which connection transactions are coming from. It also helps for big database with a lot of statement lines when we fetch transactions (as we need the latest statement line for an online account) or when we delete the connection itself. no task id
Resolved issues and error corrections
This update resolves an issue where renewing a subscription while another renewal process was running would incorrectly mark the subscription as churned. The fix ensures that subscriptions are only processed when their status indicates they should be renewed, preventing this race condition and ensuring accurate subscription management.
Original PR description
Steps to reproduce: - Have a subscription ready to expire/auto-close. - Trigger the `_cron_subscription_expiration` cron. - While the cron is processing earlier batches, manually renew the subscription. - The renewed subscription is incorrectly marked as closed/churned. Cause: The cron searches for all expired/unpaid subscriptions at the very beginning and processes them in batches of 30. If a subscription is renewed concurrently (Race condition), its ID is already in the `subscriptions_close` list, causing the cron to close it regardless of its new state. Solution: Inside the batch processing loop, consider only subscriptions that are strictly still in `SUBSCRIPTION_PROGRESS_STATE`. Task: 5929077 Forward-Port-Of: odoo/enterprise#107157
This change addresses a problem where the system couldn't correctly update invoices when linked to Point of Sale orders in Mexico. The fix adds a necessary permission to read POS order data, allowing the system to accurately process invoice cancellations related to POS transactions. This ensures invoices are correctly linked and processed without errors.
Original PR description
`l10n_mx_edi_pos` is now populating `pos_order_ids` [1]. l10n_mx_edi_pos is designed to send POS data into MX EDI without giving accounting users direct access to pos.order. So, we should consider…
`l10n_mx_edi_pos` is now populating `pos_order_ids` [1]. l10n_mx_edi_pos is designed to send POS data into MX EDI without giving accounting users direct access to pos.order. So, we should consider that in this module we won't have access to:
- `pos_order_ids` m2m on `l10n_mx_edi.document` (caused problems before [2])
- `pos_order_ids` o2m on `account.move`
- `pos.order` model
We add a minimal `sudo()` in
`_create_update_invoice_document_from_invoice` to be able to read from the `pos_order_ids` field on `account.move`:
```
File "/e19-1/l10n_mx_edi/models/account_move.py", line 1551, in _l10n_mx_edi_cfdi_invoice_document_cancel
return self.env['l10n_mx_edi.document']._create_update_invoice_document_from_invoice(self, document_values)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/e19-1/l10n_mx_edi_pos/models/l10n_mx_edi_document.py", line 54, in _create_update_invoice_document_from_invoice
if invoice.pos_order_ids:
^^^^^^^^^^^^^^^^^^^^^
File "/c19-1/odoo/orm/fields_relational.py", line 967, in __get__
return super().__get__(records, owner)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/c19-1/odoo/orm/fields_relational.py", line 45, in __get__
return super().__get__(records, owner)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/c19-1/odoo/orm/fields.py", line 1743, in __get__
recs._fetch_field(self)
File "/c19-1/odoo/orm/models.py", line 3015, in _fetch_field
self.fetch(fnames)
File "/c19-1/odoo/orm/models.py", line 3055, in fetch
fetched = self._fetch_query(query, fields_to_fetch)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/c19-1/odoo/orm/models.py", line 3193, in _fetch_query
field.read(fetched)
File "/c19-1/odoo/orm/fields_relational.py", line 985, in read
raise AccessError(records.env._("Failed to read field %s", self) + '\n' + str(e)) from e
odoo.exceptions.AccessError: Failed to read field account.move.pos_order_ids
You are not allowed to access 'Point of Sale Order' (pos.order) records.
This operation is allowed for the following groups:
- Inventory/User
- Point of Sale/User
```
Afterwards `_create_update_document` in `l10n_mx_edi` will create or write this `pos_order_ids` value on the document without `sudo()`:
```
File "/home/jvo/Code/odoo/trees/e19-1/l10n_mx_edi/models/account_move.py", line 1551, in _l10n_mx_edi_cfdi_invoice_document_cancel
return self.env['l10n_mx_edi.document']._create_update_invoice_document_from_invoice(self, document_values)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/jvo/Code/odoo/trees/e19-1/l10n_mx_edi_pos/models/l10n_mx_edi_document.py", line 56, in _create_update_invoice_document_from_invoice
return super()._create_update_invoice_document_from_invoice(invoice, document_values)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/jvo/Code/odoo/trees/e19-1/l10n_mx_edi/models/l10n_mx_edi_document.py", line 1969, in _create_update_invoice_document_from_invoice
document = remaining_documents._create_update_document(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/jvo/Code/odoo/trees/e19-1/l10n_mx_edi/models/l10n_mx_edi_document.py", line 1936, in _create_update_document
result_document = self.create({
^^^^^^^^^^^^^
File "/home/jvo/Code/odoo/trees/c19-1/odoo/orm/decorators.py", line 365, in create
return method(self, vals_list)
^^^^^^^^^^^^^^^^^^^^^^^
File "/home/jvo/Code/odoo/trees/c19-1/odoo/orm/models.py", line 4021, in create
records = self._create(data_list)
^^^^^^^^^^^^^^^^^^^^^^^
File "/home/jvo/Code/odoo/trees/c19-1/odoo/orm/models.py", line 4253, in _create
field.create([
File "/home/jvo/Code/odoo/trees/c19-1/odoo/orm/fields_relational.py", line 760, in create
self.write_batch(record_values, True)
File "/home/jvo/Code/odoo/trees/c19-1/odoo/orm/fields_relational.py", line 786, in write_batch
self.write_real(records_commands_list, create)
File "/home/jvo/Code/odoo/trees/c19-1/odoo/orm/fields_relational.py", line 1559, in write_real
raise AccessError(model.env._("Failed to write field %s", self) + "\n" + str(e))
odoo.exceptions.AccessError: Failed to write field l10n_mx_edi.document.pos_order_ids
You are not allowed to access 'Point of Sale Order' (pos.order) records.
This operation is allowed for the following groups:
- Inventory/User
- Point of Sale/User
```
We therefore take out `pos_order_ids` in an override and write it ourselves with another minimal `sudo()`.
[1] https://github.com/odoo/enterprise/pull/97060
[2] https://github.com/odoo/enterprise/pull/99590
opw-6000974
Forward-Port-Of: odoo/enterprise#109461This update resolves an issue where autofilling pivot formulas in certain scenarios caused errors and incorrect data formatting. The fix ensures that pivot formulas work reliably, preventing crashes and maintaining the intended positional structure within pivot tables. This improves the accuracy and usability of the enterprise reporting feature.
Original PR description
If we autofill a positional pivot formula in the dimension perpendicular to the positional header, it would not work correctly: - We would crash if the position wasn't in the original pivot table - We would drop the positional part otherwise (`"#country_id", 1` would become `"country_id", 25`). Task: [5909266](https://www.odoo.com/web#id=5909266&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form) Forward-Port-Of: odoo/enterprise#109631
This update resolves an issue preventing users from generating 274.XX reports when they didn't first save the sheet. The fix automatically saves the data internally before report generation, ensuring reports can now be created successfully. This improves the reliability of the Belgian Payroll reporting functionality.
Original PR description
**Steps to reproduce:** - Open Belgian Payroll - From Reporting Menu select 274.XX Sheets - Create New Sheet - Select a Year and a month with Eligible Employees > 0 (for the Generate dropdown to be enabled) - Press Generate button and then try to generate any form (do this directly without pressing save manullay button) **Issue:** The generation of any form (PDF, XML, XLSX) fails due to the receive of an empty self. **Fix:** If the user tried to generate the reports without saving, do an automatic save internally before attempting to generate the reports in the backend. task-5936740 Forward-Port-Of: odoo/enterprise#108721
This update resolves an issue where printing basic receipts would fail if the point-of-sale (POS) name was too long. The fix limits the receipt name length to 46 characters to prevent a technical error that disrupted the printing process. This ensures basic receipts are always printed correctly.
Original PR description
When printing a basic receipt, if the pos name is too long a traceback will occurs when printing the basic receipt. Steps to reproduce: * Create a pos with a name of 46 character or more * Setup the italian fiscal printer * Enable Basic Receipt printing * Open point of sale * Create an order and validate it * Try "Print Basic receipt" Traceback: RangeError: Invalid count value: -15 at String.repeat () If the data being printed is longer than the maximum number of character in a line (MAX_CHARS = 46), paddingLeft becomes negative which cause an error in repeat(). [Similar solution](https://github.com/odoo/enterprise/blob/18.0/l10n_it_pos/static/src/app/fiscal_printer/commands/print_rec_message/print_rec_message.js#L35) [opw-5270697](https://www.odoo.com/odoo/project/49/tasks/5270697) Forward-Port-Of: odoo/enterprise#109766 Forward-Port-Of: odoo/enterprise#109527
This update fixes an issue where sign requests generated from HR wizards didn't automatically use the expiration dates defined on the sign templates. Now, all sign requests will adhere to the template's configured validity period, ensuring accurate tracking and preventing outdated requests.
Original PR description
Before, when sending sign requests from the HR custom wizards, the validity date defined on the sign template was not applied to the generated signature requests. As a result, requests were created without respecting the template’s configured expiration. task-5928110 Forward-Port-Of: odoo/enterprise#107076
This update clarifies the error message displayed when an incorrect account is linked to the Expense Reimbursement salary rule. The change ensures employees receive clearer guidance on setting up their expense reimbursements correctly, preventing potential payment issues.
Original PR description
. Change the error message to say "The account linked to the salary rule Expense Reimbursement must be payable type." task-5965760
This update resolves a problem where spreadsheet thumbnails sometimes failed to save correctly due to a temporary disconnection during the screenshot process. The fix ensures thumbnails are reliably saved, improving the user experience when creating and sharing spreadsheets. This was a minor stability issue.
Original PR description
When we leave a spreadsheet, we take a screenshot of the canvas to save as thumbail. But it's sometime possible for the spreadsheet to be unmounted whe trying to screenshot it, leading to a traceback. Task: [5914708](https://www.odoo.com/web#id=5914708&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form) Forward-Port-Of: odoo/enterprise#109531
This update resolves an issue where Dutch tax returns were marked as 'Submitted' in the system without actually transmitting the required XBRL data to the Dutch tax authorities. The fix ensures that the XBRL export is triggered when a Dutch tax return is submitted, accurately reflecting the submission status and complying with Dutch reporting requirements.
Original PR description
Commit 647699eeb4b8a1cc37ca074fa57844871c5086c1 introduced account returns to the Dutch localization. However, the "Submit" action only updated the internal record state without triggering the actual XBRL export to the Dutch tax authorities. This led to a mismatch where the UI displayed "Submitted" despite no data being transmitted. This commit fixes the flow by: - Overriding `action_submit` on the account return to launch the XBRL wizard when the return type is a Dutch tax return. - Ensuring the SBR tax report wizard calls `_proceed_with_submission` on the associated account return to correctly finalize the process (including locking the period and generating the closing entry). opw-5974711 Forward-Port-Of: odoo/enterprise#110015 Forward-Port-Of: odoo/enterprise#109691
This update resolves an issue preventing automated tests from correctly opening the POS session. The changes update tour selectors to target the 'Open Register' button and modify the UI rendering to ensure the button is consistently accessible. This improves the reliability of our test automation.
Original PR description
In this commit:
- The POS open UI button is now rendered through a widget and no longer exposes the `name=open_ui` attribute. As a result, the existing tour selectors could not locate the button.
- Update the tour triggers to use `button:contains('Open Register')` so the POS session can still be opened correctly during tests.
Task:5425256
Related PR:
- Community: https://github.com/odoo/odoo/pull/241641
- Upgrade: https://github.com/odoo/upgrade/pull/9205This update resolves an issue preventing correct validation of data properties within the Knowledge and Spreadsheet Edition modules. The fix ensures data integrity and proper functionality for these key features, improving overall system stability.
Original PR description
This commit corrects wrong props validation schema that could not work.
This update fixes a technical issue within Odoo's VoIP system. Previously, the system relied on a single data field for status updates, which created maintenance challenges and lacked crucial information like employee access tokens. This change ensures accurate and complete status updates, improving the reliability of the VoIP feature.
Original PR description
Just reading `im_status` instead of the dedicated method makes the maintenance harder and it is potentially problematic as it doesn't return the `im_status_access_token` nor the necessary extra information from employee records to compute out of office. https://github.com/odoo/odoo/pull/252008
This update resolves a minor visual issue in the Helpdesk module related to the 'Rotting days' field. The change improves the field's appearance and usability by applying a standard UI element. This ensures a consistent and polished user experience for Helpdesk users.
Original PR description
This commit fixes the UI of the 'Rotting days' field, by wrapping it in a o_input_box div and using the o_input_box_overlay_end and the o_input_box_overlay_inline classnames. task-6025631
This update streamlines the spreadsheet experience by grouping data sources into organized submenus under 'Data' and 'Charts'. This change addresses a previous crash related to dynamic pivot tables and enhances usability by reducing the length of the Data menu, making it easier for users to find the information they need.
This update removes a temporary flag from the account reports tour, signifying that it is now fully functional and reliable. This ensures users can consistently access and utilize the tour without encountering unexpected issues. The change improves the overall stability of the account reporting feature.
Original PR description
This commit removes the 'undeterministicTour_doNotCopy' flag from the 'account_reports_sections' tour. This indicates that the tour is now stable.
This update removes a temporary flag from the account reporting audit tour, signifying that it is now reliably functional. This ensures consistent and accurate reporting processes for users. The change improves stability and reduces potential issues with the audit tour.
Original PR description
This commit removes the 'undeterministicTour_doNotCopy' flag from the 'account_reports_audit' tour. This indicates that the tour is now stable.
This update corrects a technical issue where incorrect class names were being used in several Odoo modules. The change ensures all elements use the correct 'o_input_box_overlay_inline' class, improving the stability and consistency of the system. This resolves a potential inconsistency that could have impacted user experience.
Original PR description
In commit [1], the class 'o_input_box_overlay_inline' was introduced, but many elements were using an invalid 'o_input_box_inline' class instead of that one. This commit replaces all the wrong implementation of inline suffixes by the right one. [1]: dc8f38b1054664a0e382530bb4fc73983e2085cb
This update resolves an issue where users couldn't enter values in the 'Allocated Time' field within the planning module, particularly when a break time was scheduled. Now, the field functions correctly with a standard input box, ensuring accurate time tracking and scheduling.
Features or functions removed from Odoo
This pull request removes various data-related files and components across multiple Odoo modules. This cleanup streamlines the system and reduces potential data storage overhead. The changes primarily focus on internal components and testing files, impacting several enterprise modules.
Original PR description
odoo/odoo#245916
This update removes a temporary workaround that had been added to ensure appointment scheduling stability. The underlying view fix is now sufficient to resolve the issue, simplifying the system and reducing potential complexity. This change improves the overall reliability of the appointment scheduling feature.
Original PR description
The fix of [commit] from saas-19.2 introduced override of `tz` to provide default value for it. It was done to be stable-friendly. For the master, we can remove the field override because the view fix is sufficient to remove the bug. [commit]: https://github.com/odoo/enterprise/commit/ebb876ce67a9d04116c12394d6385a8b2b562168 Task-5712786
The French Payroll localization module has been removed from Odoo. This decision was made due to the module's outdated and unmaintained state, which posed a risk of confusion and inaccurate implementations. Removing this module simplifies the core system and reduces potential support issues.
Original PR description
The French Payroll localization has been removed as it was unmaintained, outdated, and not suitable for real-world usage. Maintaining it in its current state could lead to confusion or incorrect implementations. TaskID: 6023819
This update removes a technical method used to quickly check billable line items in the database. Following a recent update to the debugging tools, this method is no longer needed and is replaced with a more straightforward interface. This change improves efficiency for users and support teams.
Original PR description
Since PR odoo/odoo#249108, CloC features are availables from the debug menu. That makes the _get_verbose_maintenance method deprecated. The use case those address is the quick check for billable line of codes on some DB by either the user themselves or Odoo Support. Obviously it is more practical to do it via the interface directly part-of-task-5943473
Code cleanup and technical improvements
This update adds the `.this` syntax to Odoo templates to align with upcoming OWL3 requirements. This change ensures compatibility with newer Odoo versions and prevents potential issues when using template variables to access component data, improving long-term stability.
Original PR description
In preparation for OWL3, where template variables will need to use `.this` to target component variables, we add `.this` to template variables that are targetting the component. Script PR: odoo/odoo#247965 task: OWL3 prep - add this. to template variables
This update prepares our website templates for OWL3, a new rendering engine. It adds the `.this` syntax to template variables, which is now required to correctly target component variables within the OWL3 context. This ensures compatibility and proper functionality as we transition to the new engine.
Original PR description
In preparation for OWL3, where template variables will need to use `.this` to target component variables, we add `.this` to template variables that are targetting the component. Script PR: odoo/odoo#247965 task: OWL3 prep - add this. to template variables
This update prepares our website's helpdesk templates for OWL3, a new rendering engine. It adds the `.this` syntax to template variables, which is now required to correctly access and use component variables within the templates. This ensures compatibility with the upcoming OWL3 changes.
Original PR description
In preparation for OWL3, where template variables will need to use `.this` to target component variables, we add `.this` to template variables that are targetting the component. Script PR: odoo/odoo#247965 task: OWL3 prep - add this. to template variables
This update adds the necessary syntax (.this) to Odoo templates to ensure compatibility with OWL3. This change is a preparatory step for a future upgrade, allowing templates to correctly reference component variables, which is crucial for the system's continued functionality.
Original PR description
In preparation for OWL3, where template variables will need to use .this to target component variables, we add .this to template variables that are targetting the component. Script PR: #247965 task: OWL3 prep - add this. to template variables
This update clarifies how message actions are defined within Odoo, enhancing readability and maintainability. The change replaces outdated 'thread' references with 'channel' in the configuration, streamlining the process for developers. This improves the overall organization of communication features.
Original PR description
Introduced by https://github.com/odoo/odoo/issues/243572 for improved readability of message action definition.
This update modifies Odoo's templates to align with upcoming OWL3 requirements. Specifically, it adds `.this` to template variables that target component parts, ensuring compatibility with the new OWL3 framework. This proactive step ensures a smooth transition and avoids potential issues when OWL3 is fully implemented.
Original PR description
In preparation for OWL3, where template variables will need to use `.this` to target component variables, we add `.this` to template variables that are targetting the component. Script PR: https://github.com/odoo/odoo/pull/247965 THIS_TARGETS = ['mrp'] task: OWL3 prep - add `this.` to template variables Community PR : https://github.com/odoo/odoo/pull/252205
This update prepares Odoo for OWL3 by adding the `.this` keyword to template variables that reference components. This change is necessary because OWL3 requires this syntax for targeting component variables within templates. A minor fix was also applied to correct an earlier error in the conversion of boolean values.
Original PR description
…ering context In preparation for OWL3, where template variables will need to use `.this` to target component variables, we add `.this` to template variables that are targetting the component. Script PR: #247965 task: OWL3 prep - add this. to template variables
This update prepares Odoo for a new rendering system (OWL3) that requires a specific syntax (`.this`) to access component variables within templates. The team has added this syntax to several Odoo modules to ensure compatibility and future functionality. This change is a necessary step to support the upcoming OWL3 release.
Original PR description
In preparation for OWL3, where template variables will need to use `.this` to target component variables, we add `.this` to template variables that are targetting the component. Script PR: #247965 task: OWL3 prep - add this. to template variables