Thursday, April 10, 2025
8 changes
5 changes
Enhancements to existing features
The public Knowledge website now loads article changes and the sidebar dynamically, reducing page reloads, flicker, and slow navigation. Visitors can also search articles by title or content, making information easier to find across the current knowledge site.
Original PR description
Purpose: ------- The current public view of knowledge has several flaws: - clicking on an article in the sidebar redirects to that article, which results in a complete page reload and a flicker. -…
Purpose: ------- The current public view of knowledge has several flaws: - clicking on an article in the sidebar redirects to that article, which results in a complete page reload and a flicker. - the sidebar's html is generated in backend and inserted in the dom, which makes it non reactive and slow to load. - searching for an article also generates a list of articles in backend which is inserted in the dom, and only matches article titles. To alleviate these issues, this commit introduces: - a minimalist `Article` class used as the article record in the public view. Changing article now fetches the article's data through a rpc instead of reload the public view template with the new article, avoiding the flicker and making it faster. - a component `knowledge_public_sidebar` that loads the data of the articles and render the sidebar in frontend. - a articleSearchDialog similar to the backend's command palette, which allows to find articles of the current subsite based on their title or their content. Some simplifications and feature changes have been done: - the unfolded article ids are not stored in the local storage anymore: main purpose was to keep the articles unfolded when clicking on an article in the sidebar, since the page was reloaded. But now since the sidebar isn't reloaded on article change, it's not necessary anymore. - the sidebar can be toggled in dekstop mode too. - the "load more" feature has been removed, as it was introduced for preventing the view from crashing. The new component approach prevents these crashes from happening. Task-4439155
The Chilean and Mexican e-invoicing checkout modules were updated to stay compatible with the redesigned online checkout flow. This helps customers continue entering required tax and invoicing details smoothly during website purchases.
Original PR description
See also: - https://github.com/odoo/odoo/pull/189650
The planning send wizard has been visually refreshed to make sending schedules clearer and easier for users. This improves the day-to-day experience for teams communicating planning information without changing the underlying workflow.
Original PR description
task-4701101
Copied shifts now respect an employee's actual working schedule instead of relying on broad half-day availability. Shifts outside a scheduled working time are copied as open, while flexible resources remain assigned because they are always considered available.
SEPA direct debit mandates created through online payments are now tracked more clearly and protected from accidental manual validation. Customer mandate PDFs now include the key payment validation details, making records more complete and easier to audit.
Original PR description
Prior to this commit:
- Users could validate SEPA mandates that were initiated by online payments manually without tracking.
- SEPA mandates sent as email attachments to customers had missing information (email, signature, etc.).
- Information regarding SEPA validation such as bank account, date, label, and amount was lost.
Post this commit:
- Implemented tracking for SEPA mandates created from online payments
- Added a warning popup for users attempting to manually validate a mandate
initiated from online payment.
- Added Transctions button to show all completed transactions linked to mandate.
- Modified the PDF report for mandates created from online payments, including:
- Updated introduction text to clarify the mandate's creation.
- Replaced the signature section with bank statement information, including bank account, date, label, and amount.
task-40763173 changes
Enhancements to existing features
Selection menus can now use customized filtering rules instead of relying only on the visible option label. This helps users find and display relevant choices even when extra search information is not shown on screen.
Original PR description
Purpose: allow customizing how options are filtered. In documents, we chose to limit the amount of information present in the `label` of `choice`s, but we should still be able to display all our fetched options, even those that do not match what is in the `label`, and is fixed in the related PR. Task-4656596
When a company’s GSTIN or API credentials are changed, Odoo now clears the related India e-invoicing and e-waybill connection tokens so new ones can be generated. Users also receive a warning that API connections must be re-established after changing the GSTIN, reducing the risk of failed compliance submissions with outdated credentials.
Original PR description
This **PR** refines the API token management system for l10n_in by introducing a dependency on the GSTIN number and on API's credentials. Consequently, whenever the GSTIN number or API's credentials are updated, all associated tokens and their validity are reset. New tokens must then be generated to ensure continued functionality. As part of this **PR** following will be affected: 1) edi_token used for E-Invoicing. 2) auth_validity of E-Waybill authentication. Additionally, a warning is added on GSTIN change, notifying users that re-establishing the connection for the APIs is required after updating the GSTIN. **task**-4430663 **IAP PR**: https://github.com/odoo/iap-apps/pull/971 **Enterprise PR**: https://github.com/odoo/enterprise/pull/76373
The customer statement button will now appear only when there is actual statement content for the selected customer, reducing confusing empty reports. Draft-entry warnings will also appear only when the selected customer has draft accounting entries, helping users focus on relevant alerts.
Original PR description
Description of the issue this commits addresses: The Customer Statement button is shown too often and leads to empty customer statements in some scenarios. The banner warning the user that some entries are draft is also shown too often and should only appear if the selected partner(s) have draft entries. --- Desired behavior after this commit is merged: The button only shows when the customer statement it will lead to has values to show. This means both making sure the partner has moves to show on the customer statement but also that the customer statement actually shows them. Same for the draft entries warning banner. It will only be shown when the selected parter(s) has(have) draft entries. --- task-4680249