Daily updates from Odoo
Sunday, April 19, 2026
2 changes
New functionality added to Odoo
This update separates stock management logic into a dedicated module, offering enterprise users greater control over whether they use point of sale with stock operations. The changes also adjust other modules to avoid unnecessary dependencies on the stock module, streamlining the system and improving performance. This enhances the overall POS experience for our business customers.
Original PR description
Similarly to `point_of_sale` and `pos_stock`; This commit moves the complex stock logic to its own module, to give enterprise users the flexibility of using point of sale with or without stock operations. This commit also adapts modules that might need `pos_stock_enterprise.` While some other modules don't need the stock module, so their xpaths and methods were modified to prevent depending on `pos_stock` (or `pos_stock_enterprise`) when its not needed. Task: 5418116
This update introduces a live map feature for planning managers, allowing them to see the real-time locations of technicians during interventions. The system uses automatic tracking with refresh capabilities for accurate location updates, enhancing operational visibility and efficiency.
Original PR description
# [IMP] planning: compute for user_ids in planning slot mock This commit adds the compute method on the user_ids field in planning slot. # [IMP] planning_field_service: introduce semi-live map In…
# [IMP] planning: compute for user_ids in planning slot mock This commit adds the compute method on the user_ids field in planning slot. # [IMP] planning_field_service: introduce semi-live map In this commit, we implement a semi real-time system for tracking technicians. In the new "Live Map" menu, planning managers will be able to view the live locations of their technicians having an intervention scheduled at the moment. The system is semi-live: geolocation is updated in the background while the user is active on the page, allowing managers to view their latest locations. However, the map does not update automatically, managers have to refresh the page or reopen the view to fetch and display the latest coordinates. A tracking watch starts automatically when a user signs in or completes an intervention, provided that the geolocation feature is enabled in the settings and that they have authorized location tracking on their device. Importantly, the watch is only triggered if the person performing the action is one of the users assigned to the slot. This behavior is also applied to the geolocation logged in the chatter. For security purposes, the watch is automatically stopped either by refreshing the page, closing it, or one hour after the last intervention assigned to the user. Finally, a cron is executed every day to erase all geolocations that are dated more than one day ago. On the map, the planning manager also has the opportunity to hover the users' markers. The popup displays the latest tracked location of the technician. # [ADD] planning_field_service_hr_attendance: enhance live map integration This new bridge supplements the live map by adding conditions to start and stop tracking of technicians. In other words, it improves the coverage of the real-time geolocation tracking natively available in `planning_field_service`. Namely: - Start watching position on check-in - Stop watching position on check-out - Automatic check-out also removes tracked position - Tracking automatically resumes when opening the database, if the user is checked-in and previously had a watch running The last point is particularly important, so to resume the watch if the technician closed its device during the intervention. task-5259200