Daily updates from Odoo
Monday, August 5, 2019
7 changes
New functionality added to Odoo
Discuss now includes a History mailbox where read messages are moved, helping users find previous conversations without cluttering their inbox. The history is based on Odoo-managed notifications and keeps messages for up to six months, with related cleanup changes to manage older notification records.
Original PR description
Task: https://www.odoo.com/web#id=40597&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.69e9cabdb6eab7ac13caa30c7639ed5b -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This change lets companies manage multiple operating units and assign them to key business documents such as invoices, sales orders, purchase orders, point-of-sale orders, payments, expenses, and journal entries. When enabled, reports and document headers can show the relevant operating unit's details instead of only the parent company, improving accuracy for multi-branch or multi-division operations.
Original PR description
Task: https://www.odoo.com/web#id=1917619&action=327&model=project.task&view_type=form&menu_id=4720 Pad : https://pad.odoo.com/p/r.9da01f115c928cde4b8eb85243999c84 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
Enhancements to existing features
Customers can now preview and sign field service worksheets from the portal, while emailed worksheet reports have a clearer layout and better content. The update also streamlines material handling by using sales order lines directly, improving pricing, discounts, quantities, and consistency with sales documents.
Original PR description
This merge improves the worksheet flow and design. It provides: - a portal interface: the customer can see its worksheet from its tasks on the portal - refresh the worksheet report to be clearer - improve the flow of report sending to the final customer - display, on the portal preview, the information of material products. As we need the same informations as if the material was added on the sales order, we remove the product map and directly use the sales lines. See sub commits for more details. Task-2009558
Mexican electronic invoicing features that were previously split across separate add-ons are now included in the main Mexican EDI module. This simplifies setup and ensures cancellation, payment, customs, external trade, and cash-basis tax processes work together more consistently with Mexican SAT requirements.
Original PR description
Because a lot of modules were added in stable in order to add features/fixes, it is an opportunity to merge the modules in master.
Document managers can now give selected groups read-only access to folders and limit folder contents so users only see documents owned by them. Shared document access is also checked against the share creator's current permissions, making access behavior more consistent and controlled.
Original PR description
This commit allows documents managers to add readonly groups to folders and to restrict the content by document owner. adds two new fields (`read_group_ids` and `user_specific`) to `documents.folder`. Task: #1915003
Field Service projects are now easier to configure with one setting that prepares billing, timesheets, worksheets, and planning defaults automatically. Task screens and buttons were cleaned up so users better understand the next step and avoid confusion between regular project work and Field Service workflows.
Original PR description
This merge brings small and big changes related to the flow of an FSM tasks and the FSM project configuration. * task flow - clean views in order to make the user better understand what is the next…
This merge brings small and big changes related to the flow of an FSM tasks and the FSM project configuration. * task flow - clean views in order to make the user better understand what is the next step to do in the FSM flow. - better split project and FSM buttons on task form view. The goal is to avoid confusion in user mind. A task can be FSM and follow the flow of the project app (stage by stage), and simutaneously follow the FSM flow (draft, sent, billed, done). * FSM project config In order to simplify this, we introduced the 'is_fsm' flag. Checking it on a project preconfigure the settings for the project to be in FSM mode. An FSM project is a "task rate" billable project with timesheets and worksheets. To do so, we - introduce the 'is_fsm' flag, and the onchange forcing the configuration - remove "allow planning": the gantt view and planned dates on task form view are always visible. This is not an option anymore. - remove "allow billable": we now use the flow of "task rate", meaning the project can not be billable, but each task is at a different rate (the one of the generated sale order line linked to the task, based on the service product of the project). Task-2009567
Code cleanup and technical improvements
Odoo’s eLearning area is now promoted from a Website subsection into its own application with clearer menus for courses, content, reviews, forums, certifications, reporting, and settings. This makes it easier for teams to manage learning content, track performance, sell courses, and communicate with attendees from one dedicated backend workspace.
Original PR description
PURPOSE eLearning should have its own application in manager. Indeed this is becoming a big application and having it embedded inside Website application is not enough anymore. It should also hold…
PURPOSE
eLearning should have its own application in manager. Indeed this is becoming
a big application and having it embedded inside Website application is not
enough anymore. It should also hold updated and easy-to-use menus,
navigation, actions and views in backend.
SPECIFICATIONS
Update manifest and make website_slides an application separated from
website embedded menus.
Implement new menu structure
* Courses
* Courses
List view: Course Name, # Views, # Attendees, # Ratings, Revenues,
Reviews
* Contents
* Reviews: kanban view of channel reviews
* Certifications: kanban view of surveys of type certificate
* Forum
* Forums: add columns to list view: Posts (questions count), Views
(sum of views of each post), Answers (sum of child_count on each post),
Favorites (sum of favourite_count on each post)
* Posts: add columns to list view: Views / Answers / Favourites
* Reporting
* Courses: list view on slide.channel model, ordered by # views.
List view: Course Name, # Views, # Attendees, # Ratings, Revenues;
* Contents: graph view on slide.slide model
Area Graph: X month
Y measure: # Views (others measures: Attendees, ...)
Group by: course (color)
* Revenues: graph view on sale.report model showing revenues of eLearning
courses.
Area chart, X: monthn Y: €, Color: course
* Certifications: list view on surveys of type certificate
Columns: Title, Survey Stage, Registered People, Certified People, Attempts
Success Rate (certified/attempts), Average Results
* Reviews: see kanban of latest reviews;
* Quiz: list view on slide.question model.
List view: Add # Quizz Trials, # Quizz Passed, Avg Attempts
* Forum: graph view on forum.post model
Area chart: # Posts created by months, color=forum
* Configuration
* Settings
* Allow Forum on Courses (installs website_slides_forum)
* Allow Certifications (installs website_slides_survey)
* Allow Selling Courses (installs website_sale_slides)
* Course Tags
* See channel.tags.group with label Course Tags, form view allow to
configure group tags
* https://drive.google.com/a/odoo.com/file/d/1G0g2UnG5cZG55EXQ5icbgwe7T2eSZskT/view?usp=drivesdk
* On click: open :https://drive.google.com/a/odoo.com/file/d/1I_PW3aZAbrslXadiYqmVF-_6dGXx8knd/view?usp=drivesdk
* Content Tags
Add course (slide.channel) kanban view. Each tile should contain
* Title of the course
* Tags below the title
* Primary button "New Lesson"
* Statistics :
* Attendees
* Running (progress != 100%)
* (if one content is certificate) Certified or Finished
* See : https://drive.google.com/a/odoo.com/file/d/13K8FmkbwmBG4JQ5gH3Q5T8OlWPs3blcu/view?usp=drivesdk
* With FP remarks https://drive.google.com/a/odoo.com/file/d/1mb7LUT0VUNs5fMcKB9c0Bfaqk2-XFFuu/view?usp=drivesdk
* Add "Sales 150.00$" below "Watch Time" if type "on payment". Same
info than the smart/stat button on the course itself. Click on the amount
sends to Reporting Revenues (same than on the stat btn)
Add review (rating.rating) kanban view. Each tile should contain
* Kanban view, full width, no default group by
* Order by date (most recent on top)
* See: https://drive.google.com/a/odoo.com/file/d/1IYE1QBIJa26BLugRiafyBop-srkYwndC/view?usp=drivesdk
* add a tag for unpublished comments
* Add the pic of the user above the stars
* Click on card, send to front-end and able to (un)publish the comment
* Kind of what's on the front-end: https://drive.g
Improve course form view: add a revenue stat button displaying the total
of sale order linked to the course's product.
Integrate a button on slide.channel form view allowing to perform a mass
mailing on course attendees. Do a flow similar to event.
Remove "Our Documentation" dummy default existing data. It makes no sense
to have void data. Instead just add a small explanation text in eLearning
front-end telling the user to create its first course if he has rights to
do so.
In order to better show the new backend add some demo data for missing
numbers, notably
* sales: add confirmed sale orders in order to have revenues value;
* forum: add some posts and answers;
* quiz: update slide.slide.partner demo data to hold quiz attempts count
LINKS
Task 1978729
PR #35061
Co-Authored-By: Thibault Delavallée <tde@odoo.com>
Co-Authored-By: Jérémy Hennecart <jeh@odoo.com>