Odoo Changelog — 2024-10-08

Tuesday, October 8, 2024

2 changes · 18.0

Improvements(2)

Enhancements to existing features

[IMP] web: list selection box on mobile

Core18.0webMedium

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

#mobile#list view#usability

[IMP] account: past selected date warning in secure entries wizard

PR #181652

Core18.0accountMedium

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 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).

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

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).