Daily updates from Odoo
Friday, February 28, 2025
14 changes
12 changes
Enhancements to existing features
The appraisal feedback email template now uses the correct employee and appraisal information when preparing messages. This helps ensure recipients see accurate names and subject lines in appraisal feedback requests.
Original PR description
As validation is done through _generate_template, the object is survey.user_input. Therefore we access the employee name using appraisal_id. Also changing the model to use in the render method of the subject. Task-3389374
The Chilean electronic invoicing features now include the needed PDF417 barcode generator directly in Odoo, reducing reliance on an external package. This helps keep barcode creation stable for invoices and stock documents while adding regression testing to prevent output changes.
Original PR description
Cloned from https://github.com/ihabunek/pdf417-py
License is permissive, just needs copyright and permission notices to be included.
Version ported is 0.8.1, but has some changes to it:
- Method names have all been prefixed like `f"{filename}_{old_method_name}"`
- Removed the `console` interface so we don't have security warnings.
- Inlined all files.
- Added an Odoo test to check regression on the PDF417 PNG output.
Note that `PIL` is `Pillow`, and it's in `requirements.txt`
Task [link](https://www.odoo.com/odoo/project/967/tasks/4378417)
task-4378417The Frontdesk host search now stays inactive when the search field is blank. This prevents unnecessary results from appearing and avoids extra background lookups, making the visitor check-in flow cleaner and more predictable.
Original PR description
Ensures that the host search does not fetch or display results when the input field is empty task-4416130
This update simplifies how translated text is handled in the Enterprise web sharing feature by using newly supported translation parsing. It should make translations easier to maintain without changing the user experience.
Original PR description
Thanks to the related community commit, we now support parsing `_t` functions inside template strings. We replace the workaround cases for it. Related to https://github.com/odoo/odoo/pull/194064
The Documents app now includes required access information when a user session starts, so it no longer needs extra checks during web client loading. This reduces unnecessary waiting time and helps the interface open more smoothly for users.
Original PR description
Add necessary groups inside the session_info to avoid RPCs on `document_service` startup to avoid useless waiting time on web client startup.
Payroll officers now see a dashboard warning when a payslip has been overdue for more than 30 days after its creation date. This helps teams spot delayed payroll payments sooner and take action before the issue escalates.
Original PR description
A new warning has been added to the payroll dashboard warning appears when a payslip is overdue by more than 30 days from the payslip creation date This warning serves as a reminder to the payroll officer of their obligation to make timely payments and emphasizes the need to resolve the issue before it escalates further. task-4496735
Payroll structure names can now be translated, making payroll setup clearer for teams working in multiple languages. This improves usability for international organizations without changing payroll calculations or processes.
Original PR description
- add the translate attribute to struct name Task: 4603749
The demo company now has key Indian GST-related options enabled by default. This makes demonstrations and testing of GST e-filing, GSTIN status checks, and vendor EDI retrieval easier without extra setup.
Original PR description
This PR enables `l10n_in_gst_efiling_feature`, `l10n_in_gstin_status_feature`, `l10n_in_fetch_vendor_edi_feature` boolean fields True for demo company. These fields need to be checked true for using different Indian Localization features. making them true for better demo data usability.
Project scheduling from the Gantt view now defaults to showing only open tasks. This helps users focus on active work and reduces clutter from completed or closed tasks when planning schedules.
Original PR description
- Added a default `open_tasks` filter to display only open tasks when scheduling from the Gantt view. Technical: In the search_model.js file, the `_extractSearchDefaultsFromGlobalContext` function deletes matching `search_default_` keys, which is why we have to forcefully pass them when opening a dialog task-4593268
The IoT app cards have been simplified to show the most useful device and box information more clearly. Connection problems now appear as a lightweight notification instead of blocking users with a popup, making day-to-day IoT management smoother.
Original PR description
- removed url to homepage from IoT Box cards, - removed device icon + amount of devices from IoT Box cards, - replaced "connected"/"disconnected" tags by green/red circles on IoT Device cards, - inlined connection type with IoT Box name on IoT Device cards, - removed `IoTConnectionErrorDialog` popup blocking user when the connection between the db and the IoT Box fails (replaced by simple notification). Task: 4603315  
The Sign template top bar has been simplified by moving access-related fields into a dedicated Share Access menu. This reduces visual clutter and gives users a clearer place to manage who can access signing templates.
Original PR description
**Before this PR** - The `authorized_ids` and `group_ids` fields were displayed directly in the SignTemplateTopBar. when we turn the access setting on from the configuration - Having multiple items in these fields cluttered the UI, negatively affecting usability and aesthetics. - There was no dedicated interface for managing access control efficiently. **After this PR** - The top bar UI is improved by removing the `authorized_ids` and `group_ids` fields. - A new Share Access cog menu is added to the control panel. - Clicking the menu opens a dialog that displays these fields, providing a cleaner and more user-friendly interface for managing access control. task-4333304
The signing app’s activity type settings view was updated to match a recent change in the shared Odoo base. This keeps the signing configuration screens aligned and avoids issues caused by relying on a view that no longer exists.
Original PR description
'mail_activity_type_form_inherit' is removed in community.
2 changes
Enhancements to existing features
Unpublished products used as choices inside an eCommerce combo can now still show their images to public and portal shoppers. This makes the combo selection experience clearer without requiring each individual combo item to be published separately.
Original PR description
Similarly to other types of products, combo products must be published to make them available in eCommerce. However, combo item products (i.e. the different choices in a combo) don't need to be published. Unfortunately, if a product is unpublished, public/portal users don't have access to its images, so they won't be shown in the combo configurator. This is a bad UX, as public/portal users are expected to make a product selection, but we don't show them the corresponding images. This PR uses the `src` attribute of the `img` tag to show the raw combo item's image instead of using the image url, bypassing access checks. This is done only for combo items that are not published. task-4337641 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Consolidation reports can now be configured to group accounting entries by account code and account name without requiring a strict one-to-one account mapping between companies. This makes consolidation setup more flexible for businesses with multiple accounts sharing the same code, while avoiding impact on existing accounting flows.
Original PR description
Since https://github.com/odoo/enterprise/commit/a94227b6f305ffabbe18a5ea98335a3b17659d2d, it is possible in standard report engines to group by non-stored related fields. Thanks to this, it is now…
Since https://github.com/odoo/enterprise/commit/a94227b6f305ffabbe18a5ea98335a3b17659d2d, it is possible in standard report engines to group by non-stored related fields. Thanks to this, it is now possible to greatly improve the configuration of consolidation reports, by grouping the move lines by account_id.code, then account_id.name, provided that non-stored related fields are added on account.move.line for those values. This way, it becomes possible to configure multiple accounts mapped to the same code, without having to ensure a 1 to 1 relationship between the accounts of the source and consolidating company. We received a lot of feedback from people wanting to avoir the 1 to 1 mapping, and needing to configure such customized groupby on the report. The add of a related fields is a bit too technical to be explained in any kind of functional documentation; therefore we make the choice to add them in the standard code. They are non-stored, and will have no impact on any other flow. Note that this groupby customization only works on standard engines at the moment. Custom engines still need to be adapted, but this will come in a future PR.