Saturday, October 26, 2024
12 changes · master
Enhancements to existing features
Payroll summary reports are now handled by the main payroll engine instead of being separately implemented per country. This makes period-based payroll totals more consistent and easier to customize for local requirements, including salary rule selection.
Original PR description
Purpose ======= Almost all countries have something like a master report where you select a period of time and it will sum up all lines on that period of time and generate a file. This could be improved (selection of salary rules) + make it standard. Like other standard functions, every L10N will customize if needed. TaskID: 4127251
When a spreadsheet document is used as the basis for a new dashboard, Odoo now automatically moves the original spreadsheet to the trash. Users also receive a notification, reducing confusion and helping keep document lists cleaner.
Original PR description
This commit handles archiving original spreadsheet document when using the spreadsheet as a base for a new dashboard in Odoo. A notification is also displayed to the user to indicate that the original spreadsheet document has been moved to trash. task-3798026
Resolved issues and error corrections
Clicking into template-based text areas no longer automatically highlights the default text. This makes editing marketing, helpdesk, and website content feel more predictable and helps prevent accidental replacement of template text.
Original PR description
*: marketing_automation, website_helpdesk This commit removes the default behavior of automatically selecting text when clicking on an element that contains pre-defined text originating from templates. Previously, when interacting with such elements, the default template text would be highlighted upon click, which could lead to unintended user experiences, especially in scenarios where the user does not expect or desire the selection of content by default. By eliminating this automatic selection, we ensure a more intuitive and streamlined interaction, giving users greater control over their text editing process when working with elements populated from templates. task-4147162
Miscellaneous changes
Some cities that process service invoices [1] have stricter hsCode validations than others and error on the hsCode we send. Avalara requires periods to be removed from the hsCode field for goods transactions. This was already the case. For services they inform us that the periods should be kept but leading zeroes should be stripped [2]. [1] e.g. Belo Horizonte [2] There's no documentation on this. This was specified by Avalara support in an internal support ticket. opw-4009684 Forward
Original PR description
Some cities that process service invoices [1] have stricter hsCode validations than others and error on the hsCode we send. Avalara requires periods to be removed from the hsCode field for goods transactions. This was already the case. For services they inform us that the periods should be kept but leading zeroes should be stripped [2]. [1] e.g. Belo Horizonte [2] There's no documentation on this. This was specified by Avalara support in an internal support ticket. opw-4009684 Forward-Port-Of: odoo/enterprise#72835 Forward-Port-Of: odoo/enterprise#72641
When users duplicate a spreadsheet list or pivot, the new item name now clearly includes “(copy)”. This helps users distinguish originals from duplicates and reduces confusion when managing spreadsheet data.
Original PR description
## Description This commit appends "(copy)" to the name when a list or pivot is duplicated. Task: 4269121
- Add support for batch payment via Zengin and bank statement import - Currently only support txt files task-3304270 Forward-Port-Of: odoo/enterprise#72855 Forward-Port-Of: odoo/enterprise#71290
Original PR description
- Add support for batch payment via Zengin and bank statement import - Currently only support txt files task-3304270 Forward-Port-Of: odoo/enterprise#72855 Forward-Port-Of: odoo/enterprise#71290
Before this commit, when the user alters the unit_amount field of an analytic account line which is not a timesheet and the amount has more than 6 digits then the user will get a user error saying he cannot encode a number with more than 6 digits for the unit amount field. This commit makes sure the check made on the unit amount is only made when the analytic line altered is a timesheet. Forward-Port-Of: odoo/enterprise#72755
Original PR description
Before this commit, when the user alters the unit_amount field of an analytic account line which is not a timesheet and the amount has more than 6 digits then the user will get a user error saying he cannot encode a number with more than 6 digits for the unit amount field. This commit makes sure the check made on the unit amount is only made when the analytic line altered is a timesheet. Forward-Port-Of: odoo/enterprise#72755
The error occurs when we validate the quality worksheet template. Steps to reproduce: --- - Install the ``quality_mrp_workorder_worksheet`` module - Quality > Configuration > Quality Worksheet Templates - Click on ``Design Template`` - Click on ``Close`` - Click on ``Validate`` Traceback: --- ``ValueError: Expected singleton : quality.check()`` This error occurs at [1], where we are receiving ``self`` as empty. Previous behavior: --- When we try to design a template in the
Original PR description
The error occurs when we validate the quality worksheet template. Steps to reproduce: --- - Install the ``quality_mrp_workorder_worksheet`` module - Quality > Configuration > Quality Worksheet…
The error occurs when we validate the quality worksheet template. Steps to reproduce: --- - Install the ``quality_mrp_workorder_worksheet`` module - Quality > Configuration > Quality Worksheet Templates - Click on ``Design Template`` - Click on ``Close`` - Click on ``Validate`` Traceback: --- ``ValueError: Expected singleton : quality.check()`` This error occurs at [1], where we are receiving ``self`` as empty. Previous behavior: --- When we try to design a template in the ``Quality Worksheet Templates`` the studio opens as expected. However, if we close it without making any changes, we are redirected to the form view. In this view, we encounter strange behavior and are unable to perform any actions. After behavior: --- Now, when we click on ``Design Template`` from the list view and then close it, we are redirected to the form view of the ``Quality Worksheet Templates``. [1]- https://github.com/odoo/enterprise/blob/7eb1131b413afc2549382d2524ec83445803b682/quality_mrp_workorder_worksheet/models/quality.py#L12 sentry-5695518176 Forward-Port-Of: odoo/enterprise#68341
steps: -> populate the portal user's appointments with enough appointments to have multiple pages in the portal -> go on the portal, filter by "past" -> go to page 2 --> the filter by "past" is removed from the url opw-4236596 Forward-Port-Of: odoo/enterprise#71965
Original PR description
steps: -> populate the portal user's appointments with enough appointments to have multiple pages in the portal -> go on the portal, filter by "past" -> go to page 2 --> the filter by "past" is removed from the url opw-4236596 Forward-Port-Of: odoo/enterprise#71965
The query count in single module build is higher than the one with all modules installed. - test_mail_enterprise   - test_mail_enterprise + documents_project    - test_mail_enterprise + documents_project   In summary, a one2many fields document_ids on document_projects triggers an [orm optimisation](https://github.com/odoo/odoo/pull/111651/files) leading to 10 less queries. In 16.0 the query count adapted in an all-enterprise build fails in single module In 17.0 a regression of performance was missed because a margin is added on a bunch of query count that didn't break in the all-enterprise build This pr proposes to add a field with the corresponding optimization in the test module in stable, to have reliable query counter. This field will be moved to the document module in master. RunbotError-65777 Forward-Port-Of: odoo/enterprise#72700 Forward-Port-Of: odoo/enterprise#72598
The field fetching status is used to check if we need to call the synchronization. In case there is an error during the synchronization, the user would be block with his connection. The solution is to reset the fetching status when fetching the transaction or use the new reset button on the list view of the online accounts. task:4262788 Forward-Port-Of: odoo/enterprise#72745 Forward-Port-Of: odoo/enterprise#72492
Original PR description
The field fetching status is used to check if we need to call the synchronization. In case there is an error during the synchronization, the user would be block with his connection. The solution is to reset the fetching status when fetching the transaction or use the new reset button on the list view of the online accounts. task:4262788 Forward-Port-Of: odoo/enterprise#72745 Forward-Port-Of: odoo/enterprise#72492
**Version:** - 17.0 **Current Behaviour:** - Whenever tags were added to the document, the saved notification would appear, which looked odd. - Adding multiple tags caused the field size to increase, which was inappropriate. **Updated Behaviour:** - The saved notification will only appear when exiting the document. - A CSS class has been added to maintain a fixed size when adding multiple tags. task-4164151 Forward-Port-Of: odoo/enterprise#72664 Forward-Port-Of: odoo/enterpris
Original PR description
**Version:** - 17.0 **Current Behaviour:** - Whenever tags were added to the document, the saved notification would appear, which looked odd. - Adding multiple tags caused the field size to increase, which was inappropriate. **Updated Behaviour:** - The saved notification will only appear when exiting the document. - A CSS class has been added to maintain a fixed size when adding multiple tags. task-4164151 Forward-Port-Of: odoo/enterprise#72664 Forward-Port-Of: odoo/enterprise#70195