Monday, March 18, 2024
5 changes · 17.0
Enhancements to existing features
This update improves how Odoo fetches bank statements from CodaBox when users have multiple bank accounts. Previously, the system would download files based on the oldest inactive account, resulting in unnecessary downloads of old statements. Now, each account tracks its own last statement date, allowing the system to fetch only relevant recent files for each account separately. This makes the import process faster and more efficient.
Original PR description
Currently we send a list of ibans, and a single date from which to fetch the files. This is a bit problematic if the user has multiple journals and one of which is not used. In such a case, this old journal won't have transactions for months. Then we'll use the date of this old journal as the one from which to start fetching. So a journal that is up to date and gets documents everyday will still use this old date. Therefore we'll download lots of files (3 months or historic) even though the vast majority will not be used (only skipped because already imported) From now on, for each journal, we send the date of the last bank statement along with the IBAN of the journal, so that on IAP's side, we can filter out older bank statements. This allows faster fetching of the files. IAP: https://github.com/odoo/iap-apps/pull/771 task-id 3762743
IoT devices can now automatically send their logs to the Odoo server instead of requiring manual log file collection from customers. This improvement enables faster support troubleshooting by eliminating the need for customers to manually retrieve and share IoT logs, which previously required on-site access to the local network. The feature can be toggled on or off through the Handlers configuration page.
Original PR description
Before this commit: IoT logs are kept in an IoT log file. Any time the support would need IoT log information, we are forced to ask the customer to send it to us as it requires to be in the LAN.…
Before this commit: IoT logs are kept in an IoT log file. Any time the support would need IoT log information, we are forced to ask the customer to send it to us as it requires to be in the LAN. After this commit: Relevant* log lines will be automatically send out to the server using an HTTP route. This feature can be toggled within the Handlers list page  preview:  *: Relevant = - Any odoo logs (depending on the level set in the handlers list, see: https://github.com/odoo/odoo/pull/134174 ) - Any other logs (werkzeug, python libraries, etc.) except /hw_proxy/hello Note: IoT logs received by the server will ALWAYS be logged regardless of it level. So an Odoo server set in INFO which receive a DEBUG log from the IoT will log it in its log with the DEBUG level Related odoo PR: https://github.com/odoo/odoo/pull/150920 opw-3696519 Forward-Port-Of: odoo/enterprise#57836 Forward-Port-Of: odoo/enterprise#55055
This update improves how event registration confirmation emails are sent by allowing them to be processed asynchronously instead of immediately. When many people register for an event at the same time, this change prevents the system from slowing down by deferring email generation to scheduled background tasks. This is especially beneficial for events with high registration volumes.
Original PR description
This PR introduces a new configuration parameter 'event.event_mail_async' forcing registrations-based communication to be asynchronous. Instead of directly sending communication it triggers the cron to be run as soon as possible. When having large volume of registrations, and especially concurrent registrations it saves a DB to avoid generating tickets and preparing emails synchronously to the registration creation. Task-3764894: Event: Allow using cron triggers for communication Part of Task-3084943: Event: Improve communication scheduler scalability
IoT devices can now automatically send their logs to the central server instead of requiring manual log file collection from customers. This improvement enables faster support troubleshooting by eliminating the need for customers to manually share IoT logs, and includes a toggle to enable or disable this feature from the Handlers configuration page.
Original PR description
Before this commit: IoT logs are kept in an IoT log file. Any time the support would need IoT log information, we are forced to ask the customer to send it to us as it requires to be in the LAN.…
Before this commit: IoT logs are kept in an IoT log file. Any time the support would need IoT log information, we are forced to ask the customer to send it to us as it requires to be in the LAN. After this commit: Relevant* log lines will be automatically send out to the server using an HTTP route. This feature can be toggled within the Handlers list page  preview:  *: Relevant = - Any odoo logs (depending on the level set in the handlers list, see: https://github.com/odoo/odoo/pull/134174 ) - Any other logs (werkzeug, python libraries, etc.) except /hw_proxy/hello Note: IoT logs received by the server will ALWAYS be logged regardless of it level. So an Odoo server set in INFO which receive a DEBUG log from the IoT will log it in its log with the DEBUG level Related enterprise PR: https://github.com/odoo/enterprise/pull/55055 opw-3696519 Forward-Port-Of: odoo/odoo#155944 Forward-Port-Of: odoo/odoo#150920
The Indian localization module now automatically fills in the PAN (Permanent Account Number) field when users enter a GST number, since the PAN is already embedded within the GST number. This eliminates duplicate data entry and reduces the chance of mismatches between the two fields, making the process faster and more accurate for Indian businesses.
Original PR description
Previously, users were required to enter their PAN number even after manually inputting their GSTIN, even though the PAN is inherently part of the GSTIN (spanning from the 3rd to the 12th character). Furthermore, there was no mechanism to alert users if the manually entered PAN did not match the PAN segment within the GSTIN. This commit automates the filling of the PAN based on the entered GSTIN. Now upon entering a GSTIN, the corresponding PAN is auto-filled. Task link: https://www.odoo.com/web#model=project.task&id=3767627 task-3767627 Forward-Port-Of: odoo/odoo#157006