Wednesday, July 10, 2024
19 changes
18 changes
Enhancements to existing features
The WhatsApp module’s security test was updated after an old signup/reset password token field was removed from the database. This keeps automated checks aligned with the current system behavior without changing customer-facing functionality.
Original PR description
Change a test that used the token to prove an operation was not done as an admin. Replaced with the only field that still exist in this context
This update renames an internal search permission parameter to make its purpose clearer for developers maintaining Odoo. It affects manufacturing lifecycle, quality, and barcode inventory areas, with no expected change to day-to-day user workflows.
Marketing campaign activities now show a clearer summary of what each activity will do, including its starting point, related action or message template, trigger, and expiry timing. This helps users understand and review campaign steps more easily, with a small wording correction in a campaign template.
Original PR description
### Purpose Clarify what an Activity of a Campaign will do, while cleaning up the form view as well. ### After this PR ##### Commit 1 This commit adds a summary to the activity wizard form view. This summary describes the activity with its starting point, linked Server Action or Mail/SMS Template, trigger type, and its expiry duration. This commit also cleans up the form view. ##### Commit 2 Fixed typo mistake in Marketing Activity Campaign Template. - address → addresses Task-3603463
This update adds support for tracking when a WhatsApp contact or user was last seen. It helps teams better understand recent activity while keeping related security checks covered.
Original PR description
PR community: https://github.com/odoo/odoo/pull/169737
Warehouse users can collect a customer signature directly while processing outgoing delivery orders in the barcode app. This helps ensure deliveries that require proof of receipt are signed before validation, reducing missing-signature follow-up work.
Original PR description
Added in this PR 1. If the user has `stock.group_stock_sign_delivery` activated, a `Sign` button is added to the gear context menu for `outgoing` pickings. 2. When the `Sign` button is pressed, a dialog box is opened to take the signature drawing input from the user. `partner_id` is supplied as a default name for convenience too. The dialog box approximately replicates the functionality of `SignatureWidget` in the backend. 3. Signatures are checked before validation for `outgoing` pickings: if they are not supplied, the sign dialog is opened. After the signature is supplied from the user, picking gets validated automatically. 4. Batch pickings are not included in this PR. task-3601184
This update modernizes internal data access used across accounting, reporting, payments, knowledge, and quality features after a core platform change. It should preserve existing business workflows while improving maintainability and reducing reliance on outdated internal code.
Original PR description
odoo/odoo#172378
The subscription demo data has been updated to provide clearer and more useful sample scenarios, including related stock examples and test data. This helps teams better understand and validate subscription workflows using more realistic starting data.
Colombian electronic invoicing can now handle separate operation modes for different document types, such as electronic invoices and support documents. This lets a company configure the right software credentials for each document flow instead of being limited to a single setup.
Original PR description
[IMP] l10n_co_dian: enable multi operation mode The issue is that Odoo will offer the solution to generate multiple Types of Documents: Electronic Invoices, Support Documents..etc At the moment, Odoo will only let us input one Software ID, so it will not be possible to generate 2 or more Types of Documents Solution: create new model 'l10n_co_dian_operation_modes' with the required fields to allow having multiple operation mode for the same company and decide which mode we should take based on the move type task-id#3998165 upgrade-pr#https://github.com/odoo/upgrade/pull/6219
The Belgian payroll accounting test module’s kanban views were updated to use newer, cleaner interface building blocks. This makes the test screens easier to maintain and keeps them aligned with current Odoo standards, with minimal direct business impact.
Original PR description
In this commit we have simplified the kanban arch for the test_l10n_be_hr_payroll_account module. 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 - oe_kanban_colorpicker is deprecated, use kanban_color_picker widget instead Task-3992107
Account reports now use a cleaner way to identify and categorize report lines, such as grouped rows, totals, and load-more sections. This reduces fragile internal handling and helps keep financial report behavior consistent as reports become more complex.
Original PR description
Improves slightly the markup of account report lines ids such that it can contain a dictionary, therefore enabling a key-value pair. Previously, it was made using strings, which was quite a hacky way of doing. This markup is used for example either to group lines, indicate a line is a total line, or for 'load more' lines. We standardize this by putting json into the markups in case of dictionary. task-3791247
Brazilian electronic invoices sent through Avatax now include the invoice payment terms. This helps meet government and customer expectations while keeping discount-related amounts reported at their full value until actual payment behavior is known.
Original PR description
To conform to government and customer expectations, we have to inform them of the payment terms set on the invoice. The vNet, vOrig, grossValue and netValue keys are required but meant to record "payment discounts". In Odoo the closest concept is the early_discount feature on payment terms. But we don't know if this early discount applies when we e-invoice, it's only known when the customer pays. Because of this, we always send the full amounts in these fields. At a later stage we can see if/how we should support this. task-3968325
Sales documents, quotes, invoices, and portal previews for US and Brazil companies using AvaTax can now hide the crowded tax column. This keeps customer-facing documents easier to read when many taxes apply, while allowing the behavior to be controlled by company or localization rules.
Original PR description
[IMP] account_avatax, l10n_br_avatax, sale: Hide tax column for US & BR based companies in some scenarios users can see several taxes listed in the "Taxes" column in the PDF report (for SO, quotes, invoices, etc). Having the column oversaturated with all the taxes can represent a problem for our users. it's a pain currently and we predict that we are going to receive this kind of request also for other countries and in case of multi-company we enforce the company be a USA/Brazil country base Solution: 1- Add new stored column to control showing the tax column through allowing any module to overwrite it. 2- Use the new column 'show_tax_column' to hide the tax column in portal preview and PDF report for US/BR that has avatax active Task-3864811 odoo-pr#https://github.com/odoo/odoo/pull/170705
This update removes obsolete internal code from Belgian and Swedish point-of-sale localization features. It helps keep the system easier to maintain while preserving existing fiscal compliance behavior for affected localizations.
Original PR description
remove dead code and modify some from the previous implementations in BE, SE and IN. Related: https://github.com/odoo/odoo/pull/167012
The payroll and contract salary kanban card layouts were simplified to use newer standard interface components. This makes the views easier to maintain and helps keep the employee contract and payroll screens consistent with current Odoo interface practices.
Original PR description
In this commit we have simplified the kanban arch for the hr_payroll module. 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 Task-3992107
The Data Cleaning manual merge view has been renamed from the less clear “merge action manager” label. It is now available without enabling debug mode, making it easier for regular users to access data merge tools.
Original PR description
With this commit, manual merge view's name will replace "merge action manager" and will be accesible without debug mode. task-3861100
Point of Sale can now use a customer's email address and mobile number for marketing communication. This helps businesses follow up with shoppers more easily after in-store purchases, including through WhatsApp-enabled workflows.
Original PR description
*: whatsapp, whatsapp_pos Before this commit: ========== - There is no feature for marketing in Point of Sale. After this commit: ========== - Now, we can use the customer's email and mobile number for marketing in Point of Sale. task-3872538
Bank reconciliation can now be created directly from the Kanban view without opening a separate popup. This streamlines the workflow and makes the process feel more consistent with other Odoo apps such as CRM and Project.
Original PR description
This commit adds the quick create feature to the bank reconciliation kanban view. (no more popup) In order to make bank reconciliation more intuitive and overall easier to use, we are opting for a quick create feature that is similar to the way it currently works in apps like CRM or Project. This makes the reconciliation flow a lot more streamlined. Task ID: 3916563
Graph views and some pivot-related components now load only when they are needed. This can make affected apps open faster and reduce unnecessary browser work, while keeping reporting features available when users access them.
Original PR description
We make the graph view and its js classes be lazy loaded. For simplicity some js classes of the pivot view are lazy loaded too. We plan to lazy load the pivot view and its other extensions/patches in the near future. Task ID: `3546321`
1 change
Enhancements to existing features
Added keyboard shortcuts (SHIFT+1 through SHIFT+5) to quickly select reconciliation models in the bank reconciliation widget, making the reconciliation process faster and more efficient. Also updated the "To Check" shortcut from "c" to "e" to avoid conflicts with other shortcuts.
Original PR description
Add shortcut keys to the recon model buttons in the reco widget. The keys are SHIFT+Number (1 to 5 for the 5 visible buttons) Task-4024471