Tuesday, September 24, 2024
17 changes · master
New functionality added to Odoo
This change appears to add a new approval hierarchy view in Odoo Studio, helping users better visualize and manage approval flows. It matters because business teams can more easily understand who approves what and how approval chains are structured.
Enhancements to existing features
Online delivery orders can now include additional charges, making totals more accurate for customers and restaurants. The update also adds automatic order acceptance and fixes tax calculations when multiple delivery providers are installed.
Original PR description
Before this commit: === - Delivery orders did not support charges. After this commit: === - Delivery orders now support charges. Additional Improvements: === - Automatic accept of delivery orders has been added. Fix: === - Resolved tax issue when multiple modules (e.g., pos_urban_piper_zomato, pos_urban_piper_ubereats) are installed, ensuring correct tax calculation per provider.
Resolved issues and error corrections
Uploading vendor bills with OCR now correctly completes the automatic posting step after the bill details are refreshed. This prevents bills from being incorrectly treated as manually changed, reducing follow-up work and keeping invoice processing smoother.
Original PR description
When uploading a bill and using the OCR, autoposting of the bill is broken. This is because when clicking the "Refresh" button, the OCR updates the values of the bill therefore `is_manually_modified` is set to `True`. Adding the context key `is_manually_modified` to the `_check_ocr_status` fixes this. Also, after filling all fields with the OCR, we now automatically post the bill using the helper method `_autopost_bill` of `account.move`. task-id: none Community PR: https://github.com/odoo/odoo/pull/180184
Businesses can now start a return before the original stock transfer is validated and add extra products to that return. When the transfer is tied to a sales order, those added products are recorded as negative quantities, helping teams manage reusable packaging such as crates or containers in food and beverage operations.
Original PR description
Possibility to make a return from a picking before the validation. If the picking is linked to a sales order, adding new product in the return will add them into the sales order with a negative quantity. This will be mainly used in food and beverage business to handle reusable packaging. task: 4191982
Inventory and manufacturing dashboards have been updated and reordered so teams can find the most relevant operational information faster. Standard inventory users can now access the Warehouse daily operations dashboard, improving day-to-day visibility without extra permissions.
Original PR description
[[IMP] spreadsheet_dashboard_mrp_account: Update Manufacturing dashboard](https://github.com/odoo/enterprise/commit/3486ab395fbfa69c9f05d3c6219319567a616372) & [[IMP] spreadsheet_dashboard/*: Re-order stock dashboards](https://github.com/odoo/enterprise/commit/ce0e3d9732b41fb7fb90353ced92a7b84e562e09)
Businesses can now publish and accept bookings for anytime and custom appointment types, making these options work like other appointment categories. The update also improves invitation and website snippet availability, adjusts related screens, and simplifies publishing behavior for a smoother setup experience.
Original PR description
-This PR allows 'anytime' and 'custom' appointments to publish and book like other appointments. -Remove default filters and domain. -Some UI changes -Remove unnecessary computation for the 'is_published' field. Task-3919395
Users can now display trend lines on Odoo spreadsheet bar and line charts, making it easier to spot patterns in business data. The option applies consistently across all data series in a chart, providing clearer visual analysis without complex per-series setup.
Original PR description
## Task Description This task adds the possibility to display trending lines for odoo bar/line charts. As we are not able to customize each data series (like in o-spreadsheet), we have here a global options to allows the trending line for each data series with the same parameters. ## Related Tasks/PR - Task: 3997500 - https://github.com/odoo/odoo/pull/175366 - https://github.com/odoo/o-spreadsheet/pull/4747
This update adds missing web path definitions across Helpdesk, Field Service, Planning, Forecasting, and related sales planning screens. It makes navigation links more consistent and shareable, helping users land on the right views when moving between apps or opening saved URLs.
Original PR description
_*=industry_fsm, industry_fsm_sale, industry_fsm _report, planing, project_forecast ,project_timesheet_forecast, sale_planning after this commit: added path for that so many missing actions Consider the following example with multiple actions: - the default kanban view for project - the project update of the project with id "2" These actions would generate the following path segments respectively: - /project (the default action for project, no res_id or active_id) - 2/project-update (the project update for project 2: no res_id, active_id=2) This would generate the following url: /odoo/project/2/project-update For instance, in both the project and field service modules, the same action is called for activity types. For accessing activity types in the project module the path is straightforward: odoo/project-activity-types However, to access activity types in the field service module, use the following path: odoo/field-service/project-activity-types task-3816177
Spreadsheet dashboard filters can now limit which related records users may choose, such as restricting a product filter to only relevant products or categories. This helps keep dashboards easier to use and reduces the chance of selecting values that do not make sense for a given report.
Helpdesk ticket descriptions now expand to use more available space on the form, making longer details easier to read and edit. A related Knowledge app loading issue was also adjusted so knowledge article search remains available on customized forms.
Original PR description
Before this commit, the description field displayed in the form view of `helpdesk.ticket` just has a standard height instead of directly taking the most available spaces as it is the case in the form view of `project.task` model. This commit uses the form view with html expander for the form view of `helpdesk.ticket` model to have the same behavior then the html field displayed in the form view. That is, compute the height of the description field to take the highest height possible. task-3258533
Mexican electronic invoice (CFDI) information is now visible in list views for all accounting documents, including vendor bills, not just customer invoices. Payment records also show the fiscal folio, making it easier for finance teams to identify and reconcile CFDI-related transactions.
Original PR description
Allow viewing CFDI information in the list view for all account moves, not only outgoing invoices. Also, display the fiscal folio as part of the CFDI information in payments.
Belgian payroll now lets HR mark when a sick leave is a relapse of a previous illness where legal conditions apply. This helps ensure long-term sickness handling and payroll calculations better align with Belgian requirements.
Original PR description
Added a field to mark a sick leave as a relapse(or not) of a previous sick leave when certain conditions are met to align with Belgian law. task-3877927
Subscription customers will no longer receive two separate emails when an invoice is created after a successful payment. The change keeps the plan-specific email as the main communication, reducing customer confusion and unnecessary notifications.
Original PR description
Before this commit, two mails were sent when invoices are created: 1) the mail template saved on the plan 2) the "Payment Success and invoice" template sent when the payment.transaction goes into the 'done' state.
Approval rules now better distinguish directly assigned approvers from people added through delegation, preventing delegated approvals from unintentionally replacing or expiring the original approver list. Notifications and tracking around approval groups, approver changes, and kanban delegation are also clearer, helping teams manage approval responsibilities with more confidence.
Point of Sale sessions in Belgium now always load the special products needed for enabled features such as tips or discounts, even when a database has more than 20,000 products. This prevents missing functionality during session startup for large product catalogs.
Original PR description
Steps to reproduce : -------------------------- - Install point_of_sale - Enable some special functionalities (ex. tip, discount etc) - Open session with lots of products. (More than loading limit 20,000) Issue : --------- Sometimes the special products required to smoothly run all functionalities enabled are not loaded. Cause : ---------- We have set a limit of 20,000 and if the special product is not in those products it won't be loaded. Fix : ----- Now we ensured that all special products must be loaded without the interference of the products loading limit and no need to apply domain on those 20,000 products so removed _get_available_product_domain() function. Related PR: https://github.com/odoo/odoo/pull/175796 task: 4072726
Field Service mobile task views now better preserve navigation context, so users can move between tasks and return from signed reports without losing the correct menus or simplified layout. The update also keeps the project field hidden when only one Field Service project exists and clarifies the phone field on mobile.
Original PR description
## [FIX] industry_fsm: hide project in form view if only 1 fsm project exists Before this commit, the project in the form view is no longer hidden in mobile in My Tasks of Field Services due to some…
## [FIX] industry_fsm: hide project in form view if only 1 fsm project exists
Before this commit, the project in the form view is no longer hidden in
mobile in My Tasks of Field Services due to some changes in the form
view of tasks.
This commit updates the form view to make sure to project field is
correctly hidden in mobile when there is only one fsm project.
This commit also adds a placeholder to partner_phone to make sure the
user knows which field it is in mobile view since its label is not
displayed in mobile view.
## [IMP] industry_fsm{_report}: make sure to keep the right context for pager
Before this commit, when the user is in mobile and go to field service
app and click on a task in the kanban view, he cannot use the pager in
the form view, because a new action is called and the action does not
have the active_ids, that is the records displayed in the kanban view.
This commit makes sure the action called to open a simplified form view
in mobile get the active_ids to be able to use the pager.
## [FIX] industry_fsm: make sure to go to backend with the right action
Before this commit, when the user goes to fsm task, start a timer and
stop it and then sign report. The user will go to the portal view, if he
clicks on the button to go back to the backend view, he first no longer
have tags, SO, project, ... fields hidden if he was in mobile view.
Second, he has no longer the different menus available in the mobile dashboard
or the menu bar in desktop.
This commit makes sure to load the main action to correctly get the
different menu in FSM when the user goes back to the backend view.
task-4189791When creating a field service task, users now receive a warning if the assigned person is unavailable during the selected dates. This helps planners avoid assigning work to people who are on leave, matching the behavior already available in the planning app.
Original PR description
Steps to reproduce: 1- Field service app > planning by user 2- Open form to create a new task 3- Choose a user and dates where the user is off => No warning displayed like in planning app Source: On creation, self.user_ids = res.users(<NewId origin=1>,). Accessing self.user_ids.employee_id returns empty record Solution: Accessing self.user_ids._origin.employee_id task-3965161