Daily updates from Odoo
Friday, February 7, 2025
5 changes
4 changes
Enhancements to existing features
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
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
The 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
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