Tuesday, June 22, 2021
10 changes · master
Enhancements to existing features
Users can no longer manually create and post journal entries using purchase, sales, or bank journals from the wrong view. This reduces posting mistakes by ensuring these entries are handled through the appropriate dedicated journal workflow.
Original PR description
To avoid any unnecessary user errors when posting, we need to block the user from posting journal entries from any view that is not the dedicated one. This is done by blocking the selection of purchase/sale/bank journals when manually creating a journal entry. task id #2358954 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
When users schedule a new activity from a colored activity cell, the form now opens with the activity type matching the selected column instead of defaulting to To Do. This reduces manual correction and makes activity planning faster and more accurate.
Original PR description
**PURPOSE** In activity view, if there's already an activity scheduled of some Activity type, user clicks on the colored cell, and then click "+ Schedule an activity". In this case the pop up opens but the Activity type is always To do. **SPECIFICATION** If user clicks on the colored cell and then click "+ Schedule an activity", pop up will open with the activity type from the column where the user clicks. **Task**-2528111
The mail chatter interface has been refreshed to better align with recent web client design updates. This improves the look and feel of messages, composer controls, follower actions, and related chatter elements for a more consistent user experience.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Asset-related accounting entries will now default to posting on the first day of the month instead of the last. This helps keep entries in chronological order and supports cleaner accounting timelines.
Original PR description
For the moment, the dafault accounting date for auto-posting is the last date of the month. In order to help respecting chronological order for entries, we are changing this to post on the first of the month instead. Task id #2411154
The Field Service and Helpdesk apps now provide clearer helper text and onboarding tour messages. This makes it easier for new users to understand key menus and complete initial setup steps without extra support.
Original PR description
Purpose of the commit is to improve the onboarding tour and helper content of field service app. So in this commit, improve the helper content of the various menu and onboarding tour steps messages. Related Community PR: https://github.com/odoo/odoo/pull/71896 TaskID: 2542382
Resolved issues and error corrections
This fix prevents Odoo from crashing when certain actions contain an empty context value. It improves reliability for users opening areas such as eLearning course contents and Fleet odometer records.
Original PR description
Before this commit, calling "evaluateExpr" with the empty string as argument crashed. For instance, this happened with at least two actions in Odoo: - Elearning > Courses > Contents - Fleet > Vehicules > Odometers In both cases, the context in the action is the empty string. Issue spotted thanks to the clickEverywhere test.
Odoo now handles actions that have an empty context value without crashing. This fixes navigation problems in areas such as eLearning course contents and Fleet odometer views, improving reliability for users.
Original PR description
Before this commit, calling "makeContext" with an empty string as context description crashed. For instance, this happened with at least two actions in Odoo: Elearning > Courses > Contents Fleet > Vehicules > Odometers In both cases, the context in the action is the empty string. Issue spotted thanks to the clickEverywhere test. The crash was caused by the pyjs parser. This is correct (even though the error was not clear), since an empty list of token do not represent a valid python AST. So, the fix is to make the makeContext function more tolerant. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes a delay in Odoo's web client when a new live update channel is added. Users should receive refreshed real-time updates immediately instead of waiting several seconds for polling to restart.
Original PR description
Previously, adding a new channel to the longpolling bus would abort the current longpolling request, and was supposed to immediately send a new longpolling request with the new channels, but didn't. This was caused by the fact that the code that restarts the longpolling when aborting a previous request relies on the error message of the aborted request. While rewriting the web client in owl in 0573aca, a new RPC service was written which did not reject the promise the the same error message, causing the longpoll to wait for a few seconds before sending the next request. This request fixes that by rejecting the promise with the expected error message.
The activities shortcut in the top menu now responds when users click it. This restores quick access to planned activities and prevents confusion from an unresponsive navigation item.
Original PR description
The activities systray item didn't work anymore. Nothing happened on click. It was because the do action event was never caught. The systray item logic had a different flow and didn't go through the ViewAdapter code. We fix this by factoring the do action code and adding a listener on window (through legacy service provider) to execute this code when the do_action bubbles up. Instead of using the legacy service provided, we could have done this in the SystrayItemAdapter, but we then have the legacy environment and would need more work for the same result.
This fixes the Odoo Studio option for adding a custom field from the optional fields menu in list views. Business users can now customize list views as expected without needing a workaround.
Original PR description
Before this commit, the "Add custom field" entry in the optional fields dropdown in list views didn't work. The code handling the "studio_icon_clicked" had been removed by the wowl refactoring [1]. This commit makes this work again. [1] https://github.com/odoo/enterprise/commit/6563c16c2b2786efdbf175ae8254e242c10a9be7