Daily updates from Odoo
Friday, February 7, 2025
11 changes
10 changes
Enhancements to existing features
Test coverage across several Odoo Enterprise apps was updated to match a change in how scheduled jobs are run directly. This keeps automated validation reliable and helps prevent regressions without changing day-to-day user workflows.
Original PR description
We need to adapt the calls to `method_direct_trigger` in tests. The method creates a new cursor now, so we need to be in test mode. task-4433571 odoo/odoo#193740
Users now see a clear message when they try to validate or download documents that have not been fully signed. This avoids confusing redirects and helps users understand what action is still needed before completing the signing process.
Original PR description
Before this commit, if a document wasn't fully signed, the system redirected to a new page and triggered a UserError, but the user couldn't see the error message. With this commit, the validation is improved to properly show a clear error message when documents are not fully signed, ensuring the user is informed. task-4268726
Subscription reminders now skip contracts that are not yet close enough to needing action. This reduces daily background processing for subscriptions where no reminder or closure is needed, improving efficiency without changing customer-facing behavior.
Original PR description
Before this commit, once the next_invoice_date was passed, the cron would process it everyday even if no reminder was necessary and the sub should not be closed. This commit ensure no contract is processed too soon. We decided to look for the minimal auto_close_limit value available and no contract is processed while his next_invoice_date + min_auto_close_limit is still in the future. This should reduce the amount of contract processed for "nothing". Once the auto_close_limit is passed, the contracts are still processed as they could be automatically closed before the 14 days delay is passed. task: 4295613
Belgian CODA bank statement imports now place note information directly in the transaction details. This makes payment information easier to review and helps users reconcile bank transactions with clearer context.
Original PR description
In this commit we will move the information that is placed in the note field in transaction details. task-4496857
This change updates an internal automated test to reflect recent behavior where related scheduled messages are removed when a record is deleted. It helps keep the document accounting test suite accurate and reduces false test failures, with no direct impact on end users.
Original PR description
Purpose: -------- In [this commit](https://github.com/odoo/odoo/commit/f9161cb), the messages scheduled on a record are now unlinked when unlinking this record (for models that inherit from `mail.thread`). This commit increases the query count in the test_move_document_unlink test accordingly. Task-4531402 [1]: https://github.com/odoo/odoo/commit/f9161cb7c132e97d78edef4a2a785f2bc3170b80
The restaurant preparation display setup now gives new point-of-sale users a clearer first step: they can load sample data or create their first product. This makes it easier for businesses to start using the POS restaurant workflow without needing technical guidance.
Original PR description
This commit improves the POS onboarding experience by giving users the option to either load sample data or create a new product for their first POS. Community PR: https://github.com/odoo/odoo/pull/192156 task-4430950
Payment status messages shown to customers on portal documents are now configured by payment method instead of payment provider. This makes messages more relevant for cases like bank transfers or asynchronous payment options and reduces the need to create separate providers just to show different instructions.
Original PR description
The job of transaction state messages is to show a message on top of paid documents on the portal. For example, if a confirmed transaction is linked to a sales order, the following message is shown…
The job of transaction state messages is to show a message on top of paid documents on the portal. For example, if a confirmed transaction is linked to a sales order, the following message is shown at the top of the page: "Your payment has been successfully processed, thank you!". Currently, these messages are configurable per provider, but it's unlikely that one will want Stripe to display something different than Adyen for a given transaction state. However, we definitively want to display a different message depending on the transaction's payment method. For example, wire transfer payments use the `pending_msg` field to display the payment instructions; payment methods like Karna are asynchronous by design, and we'll want to display the appropriate message regardless of the provider used to process the payment; etc. This will also allow modules like `payment_custom` to work with a single provider and multiple payment methods rather than multiple providers and one payment method each. task-2941756
New automated tests verify that planning slot templates are visible only to the right types of users. This helps ensure project users, managers, portal users, and public users get the correct level of access and reduces the risk of unintended shift visibility.
Original PR description
This commit adds test cases to validate planning slot template visibility
based on user roles and project access:
1) Project user:
- Project user can access only specific planning slot template
2) Project manager:
Can access all planning slot templates
Moved in the planning module
3) Public and portal users:
Cannot access any shifts.
task: 4480509The Sign app now has clearer labels, cleaner messages, and improved Terms & Conditions controls. Users can more easily edit or preview website terms pages and find archived templates when they need to restore them.
Original PR description
In this PR we did following changes: - Fixed typo in "Sign" button label. - Updated Terms & Conditions configuration: - Disabled in-place preview for "web page" configurations; introduced an - "Update Webpage" link for front-end editing and a separate "Preview" option. - Added filter to unarchive templates in the template menu list view. - Removed redundant exclamation mark in UI for a more polished finish. task-4231215
This update removes an obsolete styling reference from the Helpdesk portal templates. It has no expected impact on user workflows, but keeps the codebase cleaner and easier to maintain.
Original PR description
The SCSS for the `o_portal_contact_img` class was removed in a previous commit. As this class is no longer being used, it is safe to remove it from the codebase. Reff Commit- https://github.com/odoo/odoo/commit/df8535fbd40e1e5c09dbe616a3332c76c23525c8 task-3970088
1 change
Enhancements to existing features
Live chat chatbots can now include a step that ends the conversation immediately. This helps businesses control chatbot flows more clearly and prevents customers from receiving irrelevant follow-up messages after a session should be closed.
Original PR description
Purpose of this PR: Introduce a new 'end_session' step type to the chatbot. When the chatbot reaches this step, the live chat conversation will terminate, ensuring that any subsequent steps are not executed. task-id:4509331 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr