Daily updates from Odoo
Wednesday, February 19, 2025
5 changes · master
Enhancements to existing features
Sales teams can now quickly identify subscriptions that are close to ending without opening each record individually. Subscriptions approaching closure are highlighted and can be filtered, helping teams prioritize renewals and closure follow-up more efficiently.
Original PR description
Before this PR, it was necessary to open each subscription individually to identify those nearing their end dates, which was time-consuming and reduced efficiency. There was no filter available. After this PR, a new to_be_closing field flags subscriptions that are approaching closure, specifically when the end date is on or before the next_invoice_date. The list view now displays the end_date as an optional column, and subscriptions marked as closing show the next invoice date in orange to make them easily recognizable. Additionally, a closing filter has been added to quickly list all subscriptions set to end soon, allowing sales teams to manage renewals and closures more efficiently. task-4282552
The India GST integration no longer asks users to choose whether they are using production or test credentials. Odoo now detects test mode automatically from a specific dummy GST number, reducing setup mistakes and support issues.
Original PR description
There are multiple tickets where users did not select the `Production Environment` option and proceeded with test credentials. Additionally, since users cannot generate their own test credentials, the field is unnecessary and confusing. With this commit, the `l10n_in_edi_production_env` field is removed. Instead, the system will determine the environment based on the GST Number. The specific GST Number `24DUMMY1234AAZA` will be used to identify the test environment. task-4574504 **COM PR**: https://github.com/odoo/odoo/pull/197722
Resolved issues and error corrections
This fix prevents WhatsApp message button links from being accidentally altered in a way that could create incorrect destinations. It also improves validation so buttons load in the right order and generate the correct link details.
Original PR description
Incorrect dynamic button behaviour is fixed. Dynamic web buttons have fixed base, only last part can be modified, therefore making base part readonly is essential, otherwise meta appends any modified base url to originally submitted base url. Additionally, test is added to make sure that buttons are loaded correctly, according to their sequence number and also base and short_url calculation is correct. task-3908799
The Spanish Modelo 390 BOE export has been updated for the 2024 requirements and now correctly generates files from the report wizard. It also adjusts required identity fields so self-employed individuals and companies can complete the export using the appropriate information.
Original PR description
This commit updates the BOE mod390 export for 2024 and set some fields as not mandatory that should not be as you are either a self-employed (and then you use the natural person fields), or you are a company and the other fields are needed. Task: 4453629 Fwd port of https://github.com/odoo/enterprise/commit/fd14c05bcf238d2da7de825d1a6c751381c153b7 Odoo PR: https://github.com/odoo/odoo/pull/196578
This update corrects how VoIP stores and reads landline and mobile phone numbers after recent field name changes. It helps ensure the softphone shows the right contact numbers and avoids errors when viewing correspondence details.
Original PR description
This commit fixes the naming of the `landlineNumber` field. Previously, this field was referred to as the `phone` field. This commit changes its name to `phoneNumber`. Also, we had a `mobile` field that was removed in this PR: https://github.com/odoo/odoo/pull/189739 and it resulted in a bug in the `mobileNumber` getter in `correspondence_details.js` as it was retrieving a `phoneNumber` attribute from the `partner` model. In contrast, it doesn't have this attribute. Community: https://github.com/odoo/odoo/pull/197205