Thursday, November 23, 2023
5 changes · master
Enhancements to existing features
Activity reminders for private To-Do tasks now appear in their own To-Do group, while regular project task reminders remain under Project. This makes the activity menu clearer for users who manage both personal tasks and project work, helping them find the right reminders faster.
Original PR description
Currently, all activities related to project.task records are listed in the systray in a single group with the Project icon. This commit modifies this behavior to split those activities in two groups. The activities related to private tasks are now listed in a group with the icon of To-Do while the other activities related to project.task records remain in another group with the icon of Project. This commit uses an implementation similar to the one existing in mass_mailing_sms used to split activities related to mass.mailing records linked to sms/email marketing (see https://github.com/odoo/odoo/pull/43272). The drawback of this implementation is that it will add extra requests in each module that modifies the existing groups. As this functionality becomes needed in more than one module, a more flexible implementation has also been proposed in https://github.com/odoo/odoo/pull/128267. task-3410995
Fleet users can now send emails to drivers in bulk directly from the vehicle list. This makes it easier to communicate updates, reminders, or policy changes to many drivers without contacting each person individually.
Original PR description
task-3459884
When XML assets contain configuration problems, Odoo now returns a clear error template instead of only showing a generic missing asset response. This helps teams identify and resolve website or interface asset issues faster, reducing troubleshooting time.
Original PR description
Before this commit, if there is an issue on the XML assets (i.e.: Invalid inherit mode; Duplicated template name; template to inherit not found; Module not loaded or inexistent); the issue is log on the python console, and the assets return a not found error. Now, the issue is log on the python console, and the assets returns a template with the error, which will also be logged on the JS console. Not that, this was already the behavior if there were an issue parsing an XML file when creating the assets. And, it's also the behavior, if there is an error creating the CSS assets. task-id:3574505
Scrap actions in barcode workflows now use the same tablet-friendly calculator for both warehouse pickings and manufacturing orders. This makes mobile use easier and creates a more consistent experience, with clearer fields for scrap location, quantity, lots or serial numbers, and replenishment options.
Original PR description
Currently, the scrap views for pickings and MOs are significantly different. The MO one uses a tablet friendly, "digipad" widget, while the picking one displays a simplified popup. After this change…
Currently, the scrap views for pickings and MOs are significantly different. The MO one uses a tablet friendly, "digipad" widget, while the picking one displays a simplified popup. After this change is merged, the scrap view for pickings will use the same "digipad" widget as the scrap view for MOs. This will improve user experience on mobile devices and will make the scrap operation consistent between different models. As part of this task, a few additional changes were made in the scrap calculator view (digipad): A few improvements were made in the scrap calculator view (digipad): * source location is no longer displayed * scrap location placeholder was changed from "Destination Location" to "Scrap Location" * scrap location is now editable * icon for "Serial/Lot Number" is shown together with the input field * unit of measure is displayed in the same line as quantity * quantity input field is much more narrow * "Scrap Location" and "Serial/Lot Number" fields are a bit wider * scrap products cannot be created in the digipad view * domain now shows all products from moves, not only from move lines * tracking number cannot be set if product is not set
Administrators can now edit Knowledge template content using a code editor instead of a plain text field. This makes HTML template updates easier and safer by adding helpful editing features like highlighting, shortcuts, and automatic tag completion.
Original PR description
For the template gallery of Knowledge, we added a view to enable the administrators to debug and edit the templates. Currently, the view uses a `Text` widget for the `body` field. To ease the edition of the HTML contained in that field, we will use a widget loading a code editor rather than loading a `Text` widget. The editor will highlight the HTML tags, include keyboard shortcuts, support auto-closing tags, etc. It will be way more convenient to use than the current widget. task-3527741