Daily updates from Odoo
Wednesday, September 18, 2024
20 changes · master
Enhancements to existing features
Australian payroll now automates more Single Touch Payroll steps by adding payslips to STP records, creating STP records for pay runs, and warning users about unsubmitted records. The update also improves compliance handling for SuperStream, backpayments, child support, Medicare, STP finalisation, and file replacement, reducing manual work and reporting risk.
Original PR description
- Adds new payslips to STP automatically when they are created.
- Creates a new STP record for each Payrun. Adds warnings to the
dashboard for any STP records that have not been submitted.
3494990Odoo financial reports now apply the appropriate currency conversion method when consolidating companies with different currencies, using average, historical, or period-end rates depending on the account type. This improves the accuracy of consolidated statements and period comparisons, while related sales and manufacturing reports keep their existing behavior.
Original PR description
The CTA conversion method is used when consolidating multiple companies with different main currencies. The general idea is to use different rates depending on the account we're consolidating: -…
The CTA conversion method is used when consolidating multiple companies with different main currencies. The general idea is to use different rates depending on the account we're consolidating:
- Income/Expense accounts should use the average rate on the considered period
- Equity accounts should use the historical rate at the date they were made
- Other accounts should use the current rate, the one that applies at the end of the considered period
Before this commit, Odoo handled such conversions by always applying the current rate everywhere. For this, a structure called the currency table was used.
The community counterpart commit modifies the currency table in order to handle CTA conversion. This commit converts the reports to this new structure, and adds a field on account.report to control whether the report should use 'current' rates or CTA in case of multi-currency consolidation.
We also change the way the comparison feature of the reports works with multi-currency consolidation. In the past, the 'current' rate at the date_to chosen in the reports filter was used for every compared period. Now, each compared period computes a different rate depending on its date bounds. So, the 'current' rate will correspond in each period to the rate applying at the end of the period. The 'average' rate is also computed on each period individually.
Non-accounting reports defined in some sale and mrp modules are also impacted by this commit, to update the way they call the currency table. Their behavior is unaffected, they still make use of the current rates at the time they're opened.
task-4129647The project module’s automated tests were updated to use a newer testing framework and no longer rely on older mail testing helpers. This is an internal quality improvement that helps keep testing infrastructure current without changing user-facing project features.
Original PR description
Purpose of this PR: To convert QUnit tests which depends on mail/test_utils to hoot. part of: 3818666
Subscriptions can now be billed at the end of a period based on what customers actually received or used, making recurring contracts better suited for usage-based services and delivered goods. The update also clarifies delivery timing for subscription products and prevents invoices from being created for already finished contracts.
Original PR description
Currently we always create invoice for the [period next_invoice_date --> next_invoice_date + period] but for products with an invoicing policy based on delivered quantity it is on non-sense.
There are also a lot of use cases requiring periodic invoicing but at the end of the period with an invoicing based on what the customers "received". Some examples:
Subscription for a service where the usage made affects the price:
Electricity
mobile subscriptions
...
Subscription of a physical product that can fail during the period preventing the customer to use it.
Leasing / renting of cars
Tracking device in truck (existing client)
Subscriptions of fresh produce
taskid: 3071118Quality reporting now focuses on more useful information by removing fields that were not meaningful in pivot and graph reports. New passed and failed quantity measures make it easier to understand quality outcomes and spot production issues.
Original PR description
This commit removes some fields from the pivot view of `quality.check` model that doesn't make sense in this view. The removed fields are: `worksheet_page` and `finished_product_sequence`. The commit also adds new two fields that help provide better insights: `qty_passed` and `qty_failed` with the expected meaning. Upgrade PR: odoo/upgrade#6519 Task-3981694
Invoice extraction now combines OCR and autocomplete results when users select a VAT number or partner name. This helps fill in missing partner details automatically, reducing manual entry and improving data completeness.
Original PR description
The OCR and autocomplete functionalities have been integrated to provide more comprehensive data for partners. Now, when a user clicks on a VAT number, the data is enriched using OCR values. Similarly, clicking on a partner name triggers simultaneous retrieval of autocomplete data. This integration reduces the need for manual data entry by automatically filling in missing information. task-4161150
Advanced configuration menu items for tax units, horizontal report groups, and 1099 boxes are now shown only in debug mode. This keeps everyday menus simpler while still allowing administrators and support teams to access specialized setup options when needed.
Original PR description
This Pr will put different menu item in debug mode: - Tax unit - Horizontal group - 1099 boxes Task: 4192465
Appointment and website appointment dashboard cards were simplified to use newer Odoo interface building blocks. This makes the screens easier to maintain and keeps the appointment experience aligned with current platform standards, with minimal change for end users.
Original PR description
In this commit we have simplified the kanban arch for the appointment and it's related module dashboard. The goal is to simplify them, make them easier to read and use bootstrap utility classnames. - Previously, we used kanban-box, but now we are using kanban-card instead. - Deprecated oe_kanban_global_click and oe_kanban_global_click_edit. - More use of <field/> tags - Removed the oe_kanban_colorpicker class and replaced it with the kanban_color_picker widget. - Changed type='edit' to type='open' to open records. since version 16, records always open in edit mode by default. - kanban_image from rendering context, is deprecated so we use <field name="..." widget="image"/> instead - kanban_color, kanban_getcolor and kanban_getcolorname are deprecated use new attribute highlight_color="color_field_name" on root node Task-3992107
The Quality Control dashboard layout was cleaned up to use newer Odoo interface patterns. This makes the dashboard easier to maintain and helps keep the user experience consistent with current Odoo standards.
Original PR description
In this commit we have simplified the kanban arch for the quality_control module dashboard. the goal is to simplify them, make them easier to read and use bootstrap utility classnames. - Previously, we used kanban-box, but now we are using kanban-card instead. - Deprecated oe_kanban_global_click and oe_kanban_global_click_edit. - More use of `<field/>` tags - Removed the oe_kanban_colorpicker class and replaced it with the kanban_color_picker widget. - Changed type='edit' to type='open' to open records. since version 16, records always open in edit mode by default. - kanban_image from rendering context, is deprecated so we use `<field name=... widget=image/>` instead - kanban_color, kanban_getcolor and kanban_getcolorname are deprecated use new attribute highlight_color=color_field_name on root node Task-3992107
The POS preparation and order tracking dashboard layouts were cleaned up to use newer interface building blocks. This makes the screens easier to maintain and keeps them aligned with current Odoo standards, with little expected change for everyday users.
Original PR description
In this commit we have simplified the kanban arch for the pos_preparation_display module dashboard. the goal is to simplify them, make them easier to read and use bootstrap utility classnames. - Previously, we used kanban-box, but now we are using kanban-card instead. - Deprecated oe_kanban_global_click and oe_kanban_global_click_edit. - More use of `<field/>` tags - Removed the oe_kanban_colorpicker class and replaced it with the kanban_color_picker widget. - Changed type='edit' to type='open' to open records. since version 16, records always open in edit mode by default. - kanban_image from rendering context, is deprecated so we use `<field name=... widget=image/>` instead - kanban_color, kanban_getcolor and kanban_getcolorname are deprecated use new attribute highlight_color=color_field_name on root node Task-3992107
Bank and credit card journal audits are now easier to read with a dedicated view that removes unnecessary grouping and highlights the most relevant details. Users can review dates, partners, and matching information more directly, making reconciliation and audit work faster and clearer.
Original PR description
This commit aims to facilitate reading and handling the audit of the Bank and Credit Card journals. This view should be tailored, as it is not the same as suditing sales/purchase ledgers. Beyond showing only the counterpart lines, already addressed by #67611, the view should: - Remove the grouping by Partner > Journal Entry - Show columns Date, Partner and Matching This commit adds a view for the bank/credit card audit, and edits the function journal_report_open_aml_by_move to achieve this tailored audit view. It also edits the List Renderer for the audit view to ensure it can also handle the case where no default groupings exist. task-4147336
Batch payments can now specify who should pay transfer fees instead of always using the standard SEPA option. This helps businesses support more ISO 20022 payment formats and align bank files with local or bank-specific requirements.
Original PR description
In SEPA payments, `ChrgBr` indicates who pays the transfer fees. Currently, the only supported value for this field is `SLEV`. However in other ISO20022 variants, we can use other values. This commit allows user to specify the charge bearer in batch payments. Task ID: 3774253
The sales commission app now supports forecasting and improves how commission achievements and reports are calculated and displayed. These changes help sales teams and managers better plan, review, and understand commission progress, while also improving performance and reducing irrelevant community commission visibility in sales teams.
The project dashboard now better reflects subscription-related information in project profitability views. This helps business users get a more complete view of project revenue and margins when subscriptions are involved.
Original PR description
This commit's purpose is to handle the subscription part of the dashboard. Community part: task - 4150611 affected version: master
Workcenter overview links now take users directly to the work order list instead of the shopfloor view. This creates a more consistent navigation path for teams reviewing manufacturing work from the overview.
Original PR description
This PR removes the links to the shopfloor from the workcenter overview. Instead, all links now redirect to the WO list view. task 4081617
Message reactions are now shown from oldest to newest when loaded from the server. This makes conversation history easier to follow and keeps reaction displays consistent for users.
Original PR description
This commit ensures that message reactions are displayed in chronological order, from the earliest to the most recent when getting the data from the server. https://github.com/odoo/odoo/pull/180198
WhatsApp discussions in Odoo can now be organized with sub-threads inside channels, helping teams keep related replies and follow-ups grouped together. This makes busy WhatsApp conversations easier to navigate and reduces the risk of important context getting lost.
Original PR description
community: https://github.com/odoo/odoo/pull/179348 part of task-3605717
Recruitment screens now show more accurate candidate and application information, especially for companies using multiple company records. Interviewers regain appropriate editing ability on assigned applications, reporting no longer counts archived hires incorrectly, and views better reflect user permissions.
Original PR description
This pr adds various fixes and improvements to recruitment. - The `Similar Candidates` smart button counter now displays accurate numbers when in a multi company environment. Before it would search…
This pr adds various fixes and improvements to recruitment. - The `Similar Candidates` smart button counter now displays accurate numbers when in a multi company environment. Before it would search across companies for candidates, often making the number higher than actual similar candidates in the selected company leading to confusion and despair. - Since the split of the applicant model into applications and candidates, interviewers could no longer edit any information on a application (a candidate by extension) they were assigned to. This has been fixed with new access rules, allowing interviewers to edit candidates, but only through the application form. - Some buttons/fields are now hidden/read-only if you don't have access to them. - The`Other Applications` smart button now also displays applications by similar candidates, not only applications by the viewed candidate. - The `All applications` view now allows grouping by `Candidate`. - A bug in `Applicant Analysis` which cause archived applicants to still be counted as hired was fixed.
This update streamlines the subscription sales workflow, including plan setup, sales order handling, demos, and guided tour content. It helps teams manage recurring sales more easily with clearer views and improved subscription behavior.
Original PR description
task-id: 3750550
Subscription sale orders now create the first delivery as soon as the order is confirmed, instead of waiting until the first invoice is posted. This makes fulfillment start earlier and avoids duplicate or delayed delivery creation during invoicing.
Original PR description
Before this PR, after confirming a sale order, the first invoice is created and posted. then, the first delivery is created. After this PR, the first delivery is created immediately upon sale order confirmation. No delivery is created when the first invoice is posted. task-3866918