Friday, December 11, 2020
6 changes · master
New functionality added to Odoo
Odoo can now schedule background jobs to run soon instead of waiting for their normal timing. This improves responsiveness for business processes that depend on automated tasks, while also making job processing more reliable when multiple workers run at the same time.
Original PR description
Introduce a way to schedule the execution of cron jobs *soon*. Heavy refactor of the `ir.cron` model so the various parallel queries use the (not so new) `SKIP LOCKED` postgresql select option which skip rows that are locked instead of throwing an exception like `NOWAIT` would do. Various methods has been renamed and the overall selection, execution and update of job records have been re-architectured. The cron worker threads can now to wake up early via a notification on the `cron_trigger` channel of the meta `postgres` database. Task: 2368911
Enhancements to existing features
Error reports shown during module installation or upgrades are now shorter and easier to act on when XML views are broken. Instead of overwhelming users with long internal tracebacks and full XML content, the message highlights the original problem, file location, and nearby lines needed to fix it.
Original PR description
When installing/upgrading a module with broken xml views, the module installation fails with an error message that should help the developer locate and correct the error. Before this commit, a…
Resolved issues and error corrections
Archived course content no longer remains visible on the course page. This removes confusion for users by clearly separating active learning content from items that have been archived.
Original PR description
Purpose when user archive a course content, it's still visible on the course itself, without real difference between active content and archived. it was confusing. Specifications remove the active test from context the other part, the archive mechanism, is not that dumb, keep it PR #63092 task-id: 2411211 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
When installing/upgrading a module with broken xml views, the module installation fails with an error message that should help the developer locate and correct the error. Before this commit, a 3-level traceback was thrown at the developer: 1. The initial ValueError containing the original error message and some view context information. 2. The noisy re-cast of the ValueError to a ValidationError with no additionnal information. 3. An additionnal re-cast of the exception to add the original source file path plus the entire XML source code that failed to be parsed. We argue the error contains too much noise as developers are mostly interrested in correcting their erronous tag of their view, they are not interrested in `ir_ui_view` internals. The new exception report is much less talkative, the two tracebacks from `ir_ui_view` are logged at the `DEBUG` level. The new exception still contains the original error message with some context on the view record and the original source file path but it only show 5 lines of XML around the erronous tag. Task: 2366612
Helpdesk teams can now create field service interventions in the right default project and automatically use the customer delivery address. Teams can also choose the correct worksheet when creating an intervention, helping field staff receive the right instructions and documentation.
The Gantt view now displays more cleanly on small screens, with better scrolling and a simpler range selector. This makes planning schedules easier to review and navigate from mobile devices.
Original PR description
Before, gantt view on a small screen looks very weird. Now, gantt view looks properly in a small screen with scrolling and better range button UI with dropdown selection Task ID: 2053857
Mobile users are returned to the same spot on a page after closing a dialog or pop-up, instead of being sent back to the top. This reduces frustration and saves time when working through longer pages or records on a phone.
Original PR description
Before ======= If any dialog is opened on mobile, the 'modal-open' class is added to body and with that class, position of body is set to fixed, and so body is always scrolled to top. And so, after closing the dialog, user has to scroll again to the element s/he was viewing. Now ===== We store current scroll position for mobile view when opening a dialog, which helps to maitain scroll positionwhile closing a last visible dialog. Task Id: 2152130