Tuesday, October 3, 2023
11 changes · master
Enhancements to existing features
The renting setup has been reorganized so that installing rental features no longer automatically brings in the full Sales app. Sales-management-specific rental features now live in a separate bridge module, keeping installations lighter and better aligned with business needs.
Original PR description
Before this commit, sale_renting inherits of sale_management, which leads to the installation of Sales app. This is not the desired behavior. Hence, dependencies to sale_management are moved to a bridge module sale_management_renting. And dependency to sale_management is removed in sale_temporal task-3535488
The account follow-up report title can now be edited more easily in Studio, making it simpler for businesses to tailor customer-facing payment reminders. The report structure was also cleaned up and made clearer, including more helpful labels when editing the report layout.
Original PR description
The main goal of this PR was to make the title of the followup report editable (and to make the report a bit more standard in the process). In the process the code was cleaned up a bit. There were…
The main goal of this PR was to make the title of the followup report editable (and to make the report a bit more standard in the process). In the process the code was cleaned up a bit. There were the following technical challenges in making the report title editable. The render values are not passed to the report like for other standard qweb reports (e.g. with _get_report_values or computed in the template). To generate the html of the report (except the external layout including address etc) the report template just uses a function (res.partner.get_followup_html). In studio thus only this function call is visible. The actual report generation basically happens in get_followup_report_html (from account_followup_report.py). There the render values are computed and the actual report template (template_followup_report) is rendered with these values. To make the report title editable the call to get_followup_html is removed. To do this the the necessary values to render the report templates are obtained directly in the report template (i.e. template_followup_report); instead of taking the indirection via get_followup_report_html. task-3446724
The global filters side panel now lets users collapse the field matching section, reducing visual clutter while editing filters. For existing filters, this section starts collapsed by default so users can focus on the main filter settings first.
Original PR description
In the global filters side panel, the field matching section is now collapsible. It is collapsed by default when editing existing filters. Task: [3516319](https://www.odoo.com/web#id=3516319&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form)
Documents and Knowledge now better recognize when the chatter panel is displayed at the side of the screen. This helps keep the interface layout consistent and easier to use when reviewing documents or knowledge content.
Original PR description
See https://github.com/odoo/odoo/pull/118794 task-2359037
Odoo now supports more US banks when generating NACHA payment files by allowing businesses to choose the right payment entry type and create balanced files when required. Payments are also grouped by payment date, making files closer to bank expectations and potentially reducing per-batch fees.
Original PR description
These two commits makes Odoo support more American banks. For details please see the individual commits. task-3515444 task-3431827
Signature request emails for employee contracts now use the employee's work email instead of the public email field. The request screen also shows the email value, helping HR teams confirm documents are sent to the right address before requesting signatures.
Point of Sale and self-order workflows now show selected product attributes, including multiple checkbox choices, on tickets and preparation displays. This helps kitchen or preparation teams see customer selections clearly and prepare orders more accurately.
Original PR description
Previously, it was not possible to select multiple values for an attribute in Point of sale and self order. Now that this functionality has been added, we now support "multi" or checkbox attribute types. When an order is placed with products containing attributes, these are displayed on the ticket and on the preparation display.
Resolved issues and error corrections
This fix makes exchange difference entries use the correct accounting date when payments or invoices are reconciled. It keeps reconciliation behavior consistent with unreconciliation, helping financial reports reflect currency gains or losses in the right period.
Original PR description
We align how the date is computed on exchange differences on how it already works when unreconciling. See _get_accounting_date(). Task-id:3516687 Community: https://github.com/odoo/odoo/pull/136911
The consolidation report now prepares its custom column headers in the right step of the reporting process. This prevents crashes when users open reports that rely on custom consolidation columns, restoring reliable access to those reports.
Original PR description
6c570325dc64adba441c748d834cee2c0fe488b7 changed the way javascript handles options. They are now generated by a different RPC call than the lines. It is hence not possible anymore to assign option keys within the functions computing the lines (or more generally speaking, subfunctions called by _get_report_information). Because of that, the column_headers option key of the consolidation report was always computed with a standard value, causing the report's custom components to crash when trying to opening it.
Web Studio approval indicators now refresh when users move between records or save changes that affect which approvals apply. This prevents outdated approval thumbnails from being shown, helping users see the right approval status without manually refreshing.
Original PR description
This commit fixes two issues: - Have a button that has two approvals: one with a domain, the other without with the pager change record from one that has the two approvals, to the one that has only one (or vice versa). Before this change, the approvals thumbnails did not update - Same case, but save one record that did have only one approval to make it have two (or vice versa) Before this commit, the approvals thumbnails did not update. This change set corrects those two use cases, and technically adapts the approval_hook to the new relational model, with which the record is itself reactive, meaning that we don't always go through willUpdateProps, rather, we use useRecordObserver. opw-3498555 opw-3382099
The appointment calendar now shows the next available date correctly when a user's month is fully booked. This prevents customers from seeing an "Invalid DateTime" message, making the booking experience clearer and more reliable.
Original PR description
Steps to Reproduce =================== 1. Book the whole month of any user. 2. Now try to access the monthly view of the user from the front end. 3. There we can see the 'Invalid DateTime'. Technical ========== Changing fromJSDate() to fromISO() because fromJSDate() only takes date object as an argument but in our case it is a string so it shows like 'Invalid DateTime' on the UI side. This issue is coming after the refactoring of the moment to Luxon. Task-3510350