Tuesday, October 8, 2024
8 changes
3 changes
Enhancements to existing features
This update improves compatibility with newer OpenSSL and PyOpenSSL versions used for secure certificate handling. It helps electronic invoicing and related localization services continue working reliably across supported environments.
Original PR description
The OpenSSL API X509_get_notBefore got renamed to X509_getm_notBefore in OpenSSL v.1.0.0a. PyOpenSSL v19.0.0 calls the old name, PyOpenSSL v20.0.0 calls the new one. The related community PR also contains a small refactor of the _monkeypatches.py to allow simple import and creation of possible new monkeypatches and to put order onto the ones that are already in odoo.tools.misc Community PR: https://github.com/odoo/odoo/pull/95524
The Approvals app is easier to use with keyboards and screen readers. Menus, report printing, view buttons, selection states, and page landmarks now provide clearer accessibility cues, helping more users navigate the app confidently.
Original PR description
Improved accessibility for keyboard navigation and screen readers
- Added aria-labels:
- 'Actions menu' to action menu cog item
- Dynamic aria-label 'Print report: {report_name}' to print menu entry
- {view_name view} to view mode buttons
- Converted state_selection to use CheckBoxItem instead of DropdownItem:
- Improves audio narration to announce checked items properly.
- Updated main container landmarks:
- Used `<main>` node instead of `<div>` in views layout.
Task: 3603393
community:-https://github.com/odoo/odoo/pull/168878The Knowledge app now loads some interface parts only when they are needed. This should reduce initial loading work and make Knowledge feel faster, especially for users opening pages with complex views or navigation.
Original PR description
locs (js, xml, scss): ... Total lazy loaded locs: ? Task ID: `3546321`
2 changes
Enhancements to existing features
List views now handle selected records more cleanly on small screens by grouping selection actions into one menu and showing the selection count as a floating notice. This reduces horizontal scrolling and keeps more records visible on mobile devices.
Original PR description
Ths List view allows to select one or multiple records. While doing so, an indicator is displayed, showing how much records are selected and providing actions to perform on them. On regular computer's screen, the central part of the ControlPanel is used to display this indicator and its related buttons, hiding the SearchBar. On smaller screens, all those visual elements take a lot of space, easily triggering an horizontal scrolling and taking an additional line in the ControlPanel, which push the records a bit down on the screen. This commit reuses the CogMenu paradigm to group all the actions/buttons in a single element. To avoid the records being pushed down, the selection indicator is transformed into a floating "Toast" as an overlay to the Navbar (similar to what was previously done to the Pager). task-3336242 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
3 changes
Enhancements to existing features
This update fixes how accounting reports are formatted when exported to Excel files. The changes improve the layout by moving account codes to a more logical position in the spreadsheet and fixing indentation issues that previously limited reports to three levels. Users will now see cleaner, better-organized Excel exports with proper indentation support for complex report structures.
Original PR description
### [FIX] account_report: fix indentation in xlsx export Currently the indentation of XLSX export of reports was sometimes broken. The current implementation only supported up to three levels of indentation in the export as well. This fix supports a virtually infinite number of indentation levels and fixes the indentation in the XLSX exports. ### [I18N] account_reports: update terms ### [IMP] account_reports: move account code column to the right in xlsx Currently, when exporting an accounting report as XLSX file, we add a column for the account codes on the very left of the sheet. This looks a bit weird and is not the most important information to have as a first column. In this commit, we move the column to the right so the name of the line will be first, followed by the account code (if applicable). We also add a column name for the account codes. task-3986483
The accounting secure entries wizard now alerts users when securing entries may also lock older-dated records outside the selected date. The warning includes a review action so users can inspect those affected entries before proceeding, improving visibility and reducing surprises in accounting workflows.
Original PR description
Consider the Secure Entries wizard. There it can happen that entries that are past the selected date are secured. This is possible since the hash chain corresponds to the sequence prefix, ordered by…
Consider the Secure Entries wizard.
There it can happen that entries that are past the selected date are secured. This is possible since the hash chain corresponds to the sequence prefix, ordered by sequence number.
Currently the user is not warned in case this happened.
This commit introduces a warning containing an action to show all moves that are past the selected date.
To generate the warning on runbot
1. Ensure there are no invoices with prefix INV/2020
(There should not be any on the runbot)
2. Create an invoice with (accounting) date 2020/01/02 (2 Jan 2020)
It should have name INV/2020/0001
3. Create an invoice with (accounting) date 2020/01/01 (1 Jan 2020)
It should have name INV/2020/0002
4. Activate debug mode (to see the wizard)
5. Go to Accounting (app) -> Accounting (menu) -> Secure Entries Wizard
6. Select 2020/01/01 as date (to include INV/2020/0002 but not INV/2020/0001)
7. The warning should show up
Clicking "Review" leads to a list view that includes INV/2020/0001 .
(INV/2020/002 has a higher sequence number but lower accounting date than INV/2020/0001).The demo data for Argentina's reporting module has been updated to remove real partner information and replace it with fictional data. This improvement protects actual customer privacy while maintaining the ability to test and demonstrate the system's functionality.
Original PR description
This task was created to modify the demo data for Argentina, to avoid using real partner information. latam-task-1239 adhoc-task-41734 Forward-Port-Of: odoo/enterprise#71230
The system now correctly identifies late bills in GST Return-2B reports by comparing the bill date against the return period start date, rather than using an inaccurate comparison method. This ensures businesses get accurate reporting of late vendor invoices, which is important for GST compliance and financial accuracy.
Original PR description
Previous behavior: - Late bills were determined by comparing `supprd` with the `return period`, which led to inaccuracies. New behavior: - Late bills are now identified by checking if the `bill date` is earlier than the `return period start date`, ensuring more precise classification of late bills. OPW: 4210068 Forward-Port-Of: odoo/enterprise#70225