Monday, December 5, 2022
13 changes · master
Enhancements to existing features
An unused Payroll menu entry was removed to keep the application cleaner and easier to maintain. This has no expected impact on day-to-day payroll workflows because the menu was no longer in use.
Original PR description
'hr_payroll.menu_hr_payroll_root' is not used anymore and can be removed in order to cleanup a bit unused records.
The payroll accounting test setup for Belgium now uses an updated way to load the chart of accounts for the right company. This helps keep multi-company payroll and accounting test scenarios aligned and more reliable without changing day-to-day user workflows.
Original PR description
…ompany And adapt inherited functions for the extra param.
The Serbian reporting module was standardized so its source text is in English, with Serbian translations provided through a dedicated translation file. This improves maintainability and makes future updates and translations easier while preserving the local user experience.
Original PR description
Ideally, we develop in English any localization (then translate to the domestic language, in this case Serbian) All the module has been translated in english and then a .po file has been create to translate back in Serbian Task-id: 3086250
The Chilean and Mexican electronic invoicing modules were updated to use the current Odoo XML label instead of the older OpenERP label. This is a small internal alignment that helps keep localization files consistent with current platform naming.
Original PR description
change the openerp xml tag to odoo in l10n_cl_edi and l10_mx_edi module
The appointment share and onboarding link popups now underline the short link code. This makes it easier for users to see that the code can be edited before sharing the appointment link.
Original PR description
This PR adds an underline on `short_code` in the share modal of the appointment and appointment onboarding's 'get your link' modal which shows the user that the code is editable. taskID-3081979
Resolved issues and error corrections
This fix makes the accounting spreadsheet dashboard explicitly require the reporting component it already relies on. It helps prevent dashboard failures if that reporting component is manually removed.
Original PR description
…ports The dashboard actually depends on `account_reports` because it uses menus defined in that module. `account_reports` is auto-installed with `acount_accountant`, so it "works". But it will break if `account_reports` is uninstalled manually.
Miscellaneous changes
Forward-Port-Of: odoo/enterprise#32952
Original PR description
Forward-Port-Of: odoo/enterprise#32952
This fix prevents the accounting reports setup from creating tax-related accounting entries when no chart of accounts is configured. It avoids unnecessary errors during configuration and helps companies complete setup more reliably.
Fixed an issue that could prevent users from opening marketing automation campaign views. The update restores the missing context needed by the screen, reducing disruption for teams managing automated campaigns.
Original PR description
Marketing automation uses the 'state' variable which was accessible through the rendering context prior to commit: odoo/odoo@4c5b867ff6b0b674cb83d1a1262ae354ebaa6d57 This resulted in a traceback when trying to open a campaign view. task-3084676
To reproduce: 1) Make a new partner 2) Create an invoice for this partner 3) Create a payment for the same partner, at the same date, for the same amount. Don't reconcile it with the invoice. 4) Open Aged Payable/Aged Receivable (depending on the type you chose for the invoice) ===> Our partner and the operations we just created are not displayed. When the operations made for a partner balanced to 0, the partner was not displayed in the report. This was wrong. OPW 3067204 Forward-Po
Original PR description
To reproduce: 1) Make a new partner 2) Create an invoice for this partner 3) Create a payment for the same partner, at the same date, for the same amount. Don't reconcile it with the invoice. 4) Open Aged Payable/Aged Receivable (depending on the type you chose for the invoice) ===> Our partner and the operations we just created are not displayed. When the operations made for a partner balanced to 0, the partner was not displayed in the report. This was wrong. OPW 3067204 Forward-Port-Of: odoo/enterprise#34601
When submitting a large batch of documents, it could happen that the parse cron timed out. In that case, the documents that were already sent will be rollbacked even though a credit was consumed. Commiting after each document sent will prevent the same document from being sent twice. Ticket #3076874 Forward-Port-Of: odoo/enterprise#34489
Original PR description
When submitting a large batch of documents, it could happen that the parse cron timed out. In that case, the documents that were already sent will be rollbacked even though a credit was consumed. Commiting after each document sent will prevent the same document from being sent twice. Ticket #3076874 Forward-Port-Of: odoo/enterprise#34489
With Belgian salary configurator installed: if the selected car was already assigned, `create_new_contract` would return a dict with the error which was not unpacked as expected. `new_contract` would contain the key `error` and `contract_diff` the `True` value. Forward-Port-Of: odoo/enterprise#34596
Original PR description
With Belgian salary configurator installed: if the selected car was already assigned, `create_new_contract` would return a dict with the error which was not unpacked as expected. `new_contract` would contain the key `error` and `contract_diff` the `True` value. Forward-Port-Of: odoo/enterprise#34596
Steps to reproduce: - Install manufacturing, quality, iot apps. - Manufacturing > Settings > Enable Work Orders - Quality > Control Points, remove filters - If you have the demo data, Select 'Print labels' > duplicate > change type to pass/fail > save - If you don't have the demo data, create two steps for a product which has a BoM, one of type 'Print label' and one 'Pass/fail', Operations: manufacturing, Work Order operation: Assembly. - IoT app > Devices > Receipt printer > Add quality
Original PR description
Steps to reproduce: - Install manufacturing, quality, iot apps. - Manufacturing > Settings > Enable Work Orders - Quality > Control Points, remove filters - If you have the demo data, Select 'Print…
Steps to reproduce: - Install manufacturing, quality, iot apps. - Manufacturing > Settings > Enable Work Orders - Quality > Control Points, remove filters - If you have the demo data, Select 'Print labels' > duplicate > change type to pass/fail > save - If you don't have the demo data, create two steps for a product which has a BoM, one of type 'Print label' and one 'Pass/fail', Operations: manufacturing, Work Order operation: Assembly. - IoT app > Devices > Receipt printer > Add quality Control Point 'Print labels' > Save - Manufacturing app > Create manufacturing order > product: 'Table' (or the one you picked earlier) > Confirm > Work Orders > Tablet view > Go to 'Print labels' step > Click on 'Print labels' > Printing on the IoT will succeed/fail (not relevant) Issue: Currently, the pass/fail step is active, but the 'Print labels' step is displayed. If you click on any button, the display updates and the correct step is shown to the user. If you click on 'Skip' instead, the pass/fail step is skipped completely, finalizing the work order. Solution: After receiving an answer from the IoT device, call the `onClose` callback to update the screen to display the correct step. opw-3029006 Forward-Port-Of: odoo/enterprise#34572 Forward-Port-Of: odoo/enterprise#34240