Thursday, October 24, 2024
13 changes
4 changes
Enhancements to existing features
The Field Service planning view now shows only deadlines and milestones linked to Field Service projects when FSM mode is active. This reduces clutter for field service teams and helps them focus on the work that is relevant to their operations.
Original PR description
In this PR, we implement the following changes: 1. Refactor get_all_deadlines Method: The get_all_deadlines method has been refactored by splitting it into two distinct methods: one for preparing the domain and another for retrieving all the necessary fields. This refactor enhances flexibility by enabling easier method overrides, allowing for the addition of fields or adjustment of the domain as required. 2. Hide Non-FSM Deadlines and Milestones in FSM Gantt View: Deadlines and milestones that do not belong to FSM projects are now hidden in the Gantt view when FSM mode is active. This visibility is controlled by a domain, ensuring that only FSM project deadlines and milestones are displayed in the FSM. task-4037284
Indian GST reports and tax group labels now use SGST/UTGST instead of SGST. This makes the wording more accurate for businesses operating in Union Territories and improves compliance-related reporting clarity.
Original PR description
with this PR: Renamed SGST to SGST/UTGST in Tax Groups and GST Report Heading task - 4231745
Public users now see a close button on the thank-you dialog after signing a document. This makes the signing flow easier to exit and keeps the experience consistent with portal users.
Original PR description
**Before this PR:** - Previously, when portal users signed documents, they received a "Thank You" dialog that included a close button for convenience. However, public users did not have this close button in their "Thank You" dialog, potentially leading to a less intuitive experience. **After this PR:** - To enhance the user experience for public users, a close button has now been added to the "Thank You" dialog. This adjustment aligns the experience of public users with that of portal users, providing a consistent and user-friendly interface. task-4069539 --- I confirm I have signed the CLA and read the PR guidelines at [www.odoo.com/submit-pr](http://www.odoo.com/submit-pr)
WhatsApp discussion users now get one consistent search experience for finding conversations from the sidebar. This replaces separate channel-specific search controls with the existing quick search, making navigation faster and more predictable with Ctrl-K.
Original PR description
replaced the channel selector search on the discuss sidebar categories with a unified search extending the existing quick search feature. replaced ChannelSelector component with the new DiscussSearch. community PR: https://github.com/odoo/odoo/pull/176652 task-4100945
8 changes
Enhancements to existing features
Electronic invoicing options are now selected more reliably based on each customer’s country and Peppol eligibility. Italian customers will default to the local FatturaPA format, and users will see fewer irrelevant Peppol options when their company cannot use them.
1 change
Enhancements to existing features
This update improves how users in Argentina are informed about AFIP error 10016 during invoice validation. Instead of a generic error message, users now receive specific guidance based on the actual cause—whether it's a date issue, numbering mismatch, or date range requirements. This helps users quickly resolve validation problems without contacting support.
Original PR description
Original PR description
### Commit 1: [IMP] l10n_it_edi: add FatturaPA as the preferred edi format for IT partners Add FatturaPA as the preferred EDI format set by default on Italian partners. task-no --- ### Commit 2:…
### Commit 1: [IMP] l10n_it_edi: add FatturaPA as the preferred edi format for IT partners Add FatturaPA as the preferred EDI format set by default on Italian partners. task-no --- ### Commit 2: [FIX] account_\*,l10n_\*: EDI formats computation fixes 1. Before this commit, there was multiple lists of UBL/CII formats that needed to be maintained. This was error prone because each implementation needed to overrive each of these lists. We now have one dict with all formats informations that is parsed in different ways depending on the need. (By Country, Peppol compatible, ...) 2. Before this commit, if a country had two possible UBL/CII formats, one always override the other, we now have the possibility to have multiple formats per country and set a priority on them (trough a sequence number). 3. Before this commit, we maintained a list of NON-PEPPOL formats, this had multiple drawbacks: it's hard to maintain, error prone, unecessary negation that made condition tricky to understand. We now set a value on the dictionnary of UBL/CII formats that marks the format as compliant with Peppol Network. task-4240924 --- ### Commit 3: [IMP] account_peppol: refine displayed EDI formats and sending methods in partner form Make the displayed information on partner form more relevant: - the sending method "by Peppol" is no longer visible when the current company can't enable Peppol (for example an US company). - the EDI formats displayed when "by Peppol" is the preferred sending method are now only EDI formats supported by the Peppol Network. task-4240924
Inviting someone as a follower in Mail will no longer send an invitation notification automatically. This reduces duplicate emails when users are adding followers before sending them an actual message.
Technical users can now import attachments while preserving their links to related records and fields. This makes controlled attachment data migrations easier from the debug-only technical menu.
Original PR description
readonly=True on `res_model`/`res_field`/`res_id` of ir_attachment making these fields not importable. Attachment menu is only accessible in debug mode in the technical menu anyway. Then we suppose that user in attachment views understand what he does (hopefully). task-4252555
The Point of Sale apps have been adapted to meet Belgian restaurant certification requirements. This helps restaurants using Odoo in Belgium stay compliant while continuing to use related POS features such as staff login, loyalty, restaurant workflows, and self-ordering.
Original PR description
pos*: point_of_sale, pos_hr, pos_loyalty, pos_restaurant, pos_self_order In this commit, we adapt the point of sale modules to be compliant with the belgian restaurant certification. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The mail search panel was cleaned up by removing an unused setting that had no effect on how it appeared or behaved. This keeps the code simpler and easier to maintain without changing the user experience.
Original PR description
Purpose of this commit: This commit removes the unused `className` prop from the SearchMessagePanel, as it was never utilized in the component's template.
Online food orders from UrbanPiper, Swiggy, and Zomato now show merchant-paid GST taxes on order lines when the tax rate is not the aggregator-paid 5% GST. This helps merchants in India better understand and reconcile taxes they are responsible for collecting and paying.
Original PR description
**=pos_urban_piper, pos_urban_piper_swiggy After this commit: - In India there is a special case that 5% GST is collected by the aggregator and paid by the aggregator directly but other than this like 12% or 18% GST is collected by the merchant and paid by the merchant itself. - This commit targets to display taxes in the order line if they are other than 5% GST. task- 4190283
Point of Sale has been updated to better meet Belgian restaurant certification requirements. Businesses can now use QR code ordering without requiring online payment, and product prices can be adjusted directly in the cart where permitted.
Original PR description
pos*: pos_blackbox_be, pos_iot, pos_restaurant_preparation_display In this commit, we adapt the point of sale modules to be compliant with the belgian restaurant certification. A summary of the changes since last version: - QR ordering: QR code ordering is available without online payment. Just a simple ordering configuration. - Price can be changed: The price of a product can be changed in the cart.
Signing requests now automatically select the partner linked to the record as the default signer. This reduces manual selection work and helps send documents to the right person more consistently.
This pr is created to help de user to know the origin of the afip error 10016. The error 10016 can be caused by different origins, so here we give the user more precision about the origin. The…
This pr is created to help de user to know the origin of the afip error 10016.
The error 10016 can be caused by different origins, so here we give the user more precision about the origin. The objective of this pr is to be able to differentiate what is the origin of error 10016 and to be able to give a more precise message to the client.
1) If the last afip invoice validated has a higher date than the date of the invoice that is being validated then the message shown to the user is '10016-1': 'The invoice date cannot be after the last invoice validated in AFIP.'
2) If the last afip invoice number is higher than the current invoice number being validated in Odoo, then the message shown to the user is '10016-2': 'There may have been a mismatch in the numbering of this type of document between Odoo and AFIP.'
3) If any other reason cause the error '10016' then the message shown to the user is:
* Please note that if you are trying to validate an invoice with a date other than today, you must verify if it falls within the date range according to the AFIP concept or document type:
a) If it is Product: N+5 or N-5 with N being today's date.
b) If it is Services or Products and services: N+10 or N-10 with N being today's date.
c) If it is a MiPyme Invoice: N-5 0 N+1 with N being today's date. For Debit Note or Credit Note only N-5"
Task Adhoc side: 37771
Task latam side: 1194
This pr replaces https://github.com/odoo/enterprise/pull/65675