Thursday, October 12, 2023
6 changes
New functionality added to Odoo
Kiosk orders are now automatically sent to the preparation display once completed, helping kitchen staff see and prepare them without extra steps. The display also shows each order's tracking number and whether it is for takeaway or eat-in, improving clarity for fulfillment.
Original PR description
pos*: pos_order_tracking_display, pos_preparation_display, (new) pos_self_order_preparation_display This module is a bridge module between the preparation display and the kiosk mode. It sends the order to the preparation display when the order is done. It also adds the tracking number of the order on the up-right corner of the order-card and an indication if this order is to take away or to eat in. task-id: 3495477 Community PR: odoo/odoo#134980
Enhancements to existing features
Appraisal screens now rely on employee fields that automatically show the right employee records based on the user's access level. This helps keep appraisal and feedback workflows aligned with permissions while reducing manual view configuration.
Original PR description
In the community counterpart of this PR, we change the employee custom fields to stop using always 'hr.employee.public' as the relation, but dynamically decide which relation it should use depending on the group that the current user has. Also, we allow forcing a relation by passing it as an option in the view. So, this commit removes the relation of the fields that would benefit from having this feature of showing different records depending on the user group. task-3524305
Odoo now loads the rich text editor only when it is actually needed, helping the backend open faster for users. The update also makes the supporting assets available ahead of time to keep automated processes and tests more reliable.
Original PR description
[IMP] knowledge: lazy load wysiwyg In order to improve the loading time of the odoo backend, only load the wysiwyg before starting an html_field. task-3493014
Field service teams can now use the newer product catalog experience when adding products to service tasks and related sales lines. This makes product selection more consistent with sales workflows while preserving the specific update behavior needed for field service operations.
Original PR description
Purpose of this PR: Sales team implemented a new catalog option to select product to add on a Sale Order (https://github.com/odoo/odoo/pull/106382) We want to replace the actual FSM stat button…
Purpose of this PR: Sales team implemented a new catalog option to select product to add on a Sale Order (https://github.com/odoo/odoo/pull/106382) We want to replace the actual FSM stat button product by an access to this catalog ## Details about the implementation: ### Original product.catalog architecture product.catalog view is created in the *sale* module (odoo/addons/sale/views/product_product_views.xml) this product.catalog is using the js_class 'sale_product_kanban' to represent the kanban records of each product (odoo/addons/sale/static/src/js/product_catalog/kanban_view.js) as well as a new componant sale_order_line.js (present at the bottom of the product kanban card, displays the actual number of products in the SOL ) 'sale_product_kanban' record uses RPC call on a specific route to update and fetch informations about the product, this routing is handled by the controller (odoo/addons/sale/controllers/[catalog.py](https://catalog.py/)) The product.catalog view is then inherited by the *sale_stock* module to add the on Hand quantity of product ### Modifications made: Added a new controller with a new route to update the fsm product, this is because the logic of updating a SOL line from the sale module is quite different from updating a sale order line from the industry_fsm module, we just created a new method/route sale_product_catalog_update_sale_order_line_fsm_info which is called by the new kanban_record class we also inherit the method `sale_product_catalog_get_sale_order_lines_info` just to update the context with the task_fsm_id Added the task-id to the product_catalog/kanban_record env Adapted industry_fsm tours accordingly Task-3343547 Community PR: https://github.com/odoo/odoo/pull/127161 Upgrade PR: https://github.com/odoo/upgrade/pull/4887 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
A fillable Danish accounting procedure PDF has been added to the Documents accounting app. This helps Danish businesses document accounting procedures in line with updated government guidance and compliance expectations.
Original PR description
The Danish Tax Agency and the Danish Business Authority are launching an updated common standard chart of accounts. For the accounting act, we need to provide a way to support the function that users can enter an accounting guide for the individual account This commit adds a text file of danish accounting procedure in documents_account, following the strucure from Danish government's documentation task-id: 3531476
The Mongolia VAT report is now handled in the Community edition and uses the standard tax tag reporting approach. This keeps the report aligned with Odoo’s common reporting framework and makes it easier to maintain across editions.
Original PR description
- The VAT report was moved to the Community repo Community PR: https://github.com/odoo/odoo/pull/134590 Upgrade PR: https://github.com/odoo/upgrade/pull/5122