Daily updates from Odoo
Monday, August 19, 2019
6 changes
New functionality added to Odoo
Odoo now records website visitor activity, links visitors to leads or customer records when they engage, and gives live chat operators the ability to start conversations with available visitors. This helps sales and support teams understand recent visitor behavior and reach out at the right moment.
Original PR description
This merge adds the website_visitor model that will be used to track website visitor activity (page viewed, number of visits and more general info about the visitor (country, lang, etc..) This model…
This merge adds the website_visitor model that will be used to track website visitor activity (page viewed, number of visits and more general info about the visitor (country, lang, etc..) This model will, in later commit, be used to send chat requests and push notification from the operators (or backend users) directly to the visitor. To keep a detailed history of the visitor page views, we add a website.visitor.page model that makes the link between visitor and website.page but that keeps the visit date. So that we can see if a visitor went mulitple times on the same page and when. It's useful to see his last page views. If a website_visitor submit a contact form (and becomes a lead), the website_visitor is linked to the crm.lead. If a website_visitor logs in, the website_visitor is linked to the user's res.partner. This also allows a livechat operator to send a chat request to a connected and available website_visitor. See sub commits for more detailed informations about functional flows and technical changes/decisions. Task : https://www.odoo.com/web?#id=2028059&action=327&model=project.task&view_type=form&menu_id=4720 Linked to enterprise PR odoo/enterprise#4834
Odoo can now value delivered stock based on the exact serial or lot numbers selected, rather than only using the oldest available stock costs. This improves warehouse accounting accuracy when identical products are received at different costs and later shipped by specific serial number.
Original PR description
This PR adds Stock Valuation Identification Method support for Warehouse Accounting. Assume that we have - Day 1: stock `in 2` pc @ `$100` with Seials `0001` and `0002` - Day 2: stock `in 2` pc @…
This PR adds Stock Valuation Identification Method support for Warehouse Accounting. Assume that we have - Day 1: stock `in 2` pc @ `$100` with Seials `0001` and `0002` - Day 2: stock `in 2` pc @ `$200` with Seials `0004` and `0005` - Day 3: stock `in 2` pc @ `$300` with Seials `0006` and `0007` - Day 4: stock `out 3` pc `0001`, `0004`, `0007` ### Current behavior before PR: Odoo does not respect the serials input during delivery then it valuates only 100+100+200 = 400 (serials 0001, 0002, 0004 respectively) ### Desired behavior after PR is merged: The out valuation should be 100 + 200 + 300 (serials 0001, 0004, 0007 respectively) ### What this PR does 1. [IMP] move methods `_create_%s_svl` from stock move to stock move line for more relevant and shorter code. It also helps later development of Valuation Identification Method 2. [ADD] fields `stock_move_line_id` and `lot_id` to stock.valuation.layer 3. [ADD] method `_run_fifo` now supports Stock Valuation Identification Method if lots are passed into the method. It does the job by * finding back incomming stock valuation layers having lot/serial first * comparing the quantity with lots with the initial fifo quantity. If the quantity with lots is less, continuing to find other candidate. * after these operations, the candidates with lots will be on the top of the recordset for later valuation -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Enhancements to existing features
Restaurant staff can now work from the same Point of Sale configuration and share a single session across devices. Orders and table activity are synchronized when switching tables, helping multiple waiters serve the same floor without blocking each other.
Original PR description
PURPOSE ========= When working in restaurants, there are often more than one waiter working on the same floor. But Odoo doesn't support that. There can only be one person working on one session for…
PURPOSE
=========
When working in restaurants, there are often more than one waiter working on the same floor.
But Odoo doesn't support that.
There can only be one person working on one session for the same tables.
The purpose of this task to allow several people to work on the same session (while synchronizing sessions).
SPECIFICATIONS
===============
- MultiUser is active by default.
- Allow multiple waiters to login on one PoS Config.
- All waiters login to the same session, the waiter that does the paiment is the responsible for the order (same as now).
- Synchonize the information across the multiple instances running on same floors.
Syncronisation will take place at switch of table.
(close tables automaticly if no activity, to force sync)
- Syncro cannot be done if no internet : how do we manage it ? We should inform the user the internet connection has been lost and that synchro cannot be done. What impacts? To check
Useful links
https://github.com/it-projects-llc/pos-addons
https://apps.odoo.com/apps/modules/11.0/pos_bus_restaurant/
Related PR:
https://github.com/odoo/odoo/pull/32789
task: https://www.odoo.com/web#id=1891130&model=project.task&view_type=form&menu_id=Restaurant staff can now work together on the same point-of-sale session for shared tables and floors. This helps teams serve customers more smoothly by keeping activity synchronized between multiple waiters.
Original PR description
PURPOSE
=========
When working in restaurants, there are often more than one waiter working on the same floor.
But Odoo doesn't support that.
There can only be one person working on one session for the same tables.
The purpose of this task to allow several people to work on the same session (while synchronizing sessions).
TASK-ID: 1891130The Field Service app now has clearer menus, ready-made filters, map and calendar views, planning views, and task reporting to help teams organize daily work faster. Managers can more easily review all jobs, assign work, see customer locations, and analyze field service tasks, while some complex setup options were simplified.
Original PR description
This merges provides many UI changes in order to improve the usability and day to day work of FSM application. This adds - news menus - news predefined filters - reorganise some views - reporting for worksheet - simplify some options (allowed products, ...) See subcommits for more details Task-2009563
Code cleanup and technical improvements
This update streamlines subcontracting by moving key actions directly onto operations, supporting extra received quantities, dropshipping flows, and easier tracking of lots and components. It also simplifies setup by allowing any supplier to be assigned on a bill of materials, reducing configuration overhead and improving day-to-day accuracy.
Original PR description
This PR modify the subcontracting process: - Support extra quantity - No more interaction with the subcontract order. Everything is directly accessible on the operation - Dropshipping with subcontracting - Bypass reservation process - The partner type subcontractor is removed and every partner could be set on the BoM - Update the initial demand will trigger the rules. - Demo data - Subcontractor is required on the BoM (no more BoM for all partners of type subcontractor) Visually: - Remove the stat button for linked operation. - Register Components is only available when a subcontract component is tracked - Button on operations in order to correct tracked components - Show Operation button will ask to record components until the total quantity is provided(correction on finish lines are allowed after) More details available in each commit Task 1962187