Daily updates from Odoo
Thursday, July 24, 2025
11 changes · master
Enhancements to existing features
This update adjusts Odoo Studio tests and behavior to stay aligned with a related messaging system change. It helps ensure Studio form editing continues to work reliably after the underlying recipient field lookup was removed.
Original PR description
PR community: https://github.com/odoo/odoo/pull/208393 Task-4685400 Forward-Port-Of: odoo/enterprise#90375 Forward-Port-Of: odoo/enterprise#84661
Automatic bank reconciliation messages now show OdooBot as the author instead of the current user. This makes it clearer in the chatter when an accounting action was performed by the system rather than manually by a person.
Original PR description
- Before this pr: When bank statement lines were automatically reconciled, the system posted related messages in the chatter with the current user set as the author. - After this pr: Messages posted in the chatter as a result of automatic reconciliation now correctly use OdooBot as the author, reflecting that the operation was system-driven rather than manual. Task: 4852073
This update adjusts mail-related integrations for AI, VoIP, and WhatsApp after an internal contact/persona model was removed. It helps keep messaging, calling, and chat assistant features working consistently without changing the user-facing workflow.
Original PR description
Adapte code to the removing of persona model. task-4675821
This update removes reliance on an older anonymous visitor name field in helpdesk livechat flows. Because livechat now usually has a guest or user name available, this simplifies the system and prepares for future cleanup without changing the customer-facing chat experience.
Original PR description
Now that we have guests in livechat, we almost always have a guest or user name. Over time, those values have replaced the usage of the anonymous_name field. This change removes the use of this field from method params and demo files. If we address the channel naming in a few corner cases (e.g., using the name field for a deleted visitor or partner) in the next step, then we can remove the anonymous_name field from the discuss channel model. part of task-4675719 Related to : odoo/odoo#210785
The Knowledge app tour was updated to match recent user experience changes in the history dialog. This helps keep guided testing and demonstrations aligned with the latest interface, reducing confusion and maintenance issues.
Original PR description
* Adapt knowledge tour after UX changes task-3560677
The Belgian POS fiscal compliance screens now use clearer wording for the required INSZ field, describing it as the social security identification number. This helps employees and administrators understand what information is needed and reduces confusion during setup or validation.
Original PR description
INSZ number check wasn't explicit enough for users, so we improved helper messages to "Social security identification number" to ease the understanding of the requirement. Forward-Port-Of: odoo/enterprise#90754
Resolved issues and error corrections
A small internal fix makes the web editor available consistently across automated tours. This helps reduce test issues and supports more reliable validation of Studio-related behavior without changing day-to-day user workflows.
Original PR description
This commit moves the patch of editor into html_editor to expose the editor instance globally for all the tours. Community PR: https://github.com/odoo/odoo/pull/212032 Forward-Port-Of: odoo/enterprise#90764
The AI assistant no longer sends the latest user question twice when building conversation context. This helps produce cleaner, more accurate AI responses and avoids unnecessary processing.
Original PR description
Prior to this commit, we send messages to the llm like the following:
```
[
{'content': Markup('<p>first question</p>'), 'role': 'user'},
{'content': Markup("<p>Sure, I'm here to help. What's your first question?</p>"), 'role': 'assistant'},
{'content': Markup('<p>second question</p>'), 'role': 'user'},
{'role': 'system', 'content': "You are a RAG assistant.\n\nToday's date to be used: 2025-07-18"},
{'role': 'user', 'content': 'second question'}
]
```
We're actually duplicating the user's prompt and this is because of the retrieval of the chat history. Before calling generate_response, we post the user's message. Therefore, he's message is already recorded in the db. We should then skip the most recent message to assemble the chat history since its just the same to the prompt.
Forward-Port-Of: odoo/enterprise#90665
Forward-Port-Of: odoo/enterprise#90502The automated Field Service stock test was adjusted to match the updated task list behavior. This keeps quality checks aligned with the product and helps prevent false test failures after related platform changes.
Original PR description
This commit adapts the `industry_fsm_stock_test_tour` tour according to the changes made in community. That is, now the main list view of tasks will now be readonly as before instead of editable with a open form view button. Forward-Port-Of: odoo/enterprise#89585
Point of Sale now stops zero-amount customer deposits before they are processed and shows a warning instead. This prevents an unexpected error screen and helps cashiers continue their workflow smoothly.
Original PR description
Steps to reproduce: =================== - From the POS UI, select a customer - Select Deposit Money - Try to deposit `0` amount by clicking Validate button Issue: ====== A traceback is raised when attempting to validate a deposit with zero amount. Cause: ====== The system does not check for zero-amount orders when creating a deposit payment line. Fix: ==== Add a dialog warning when the deposit amount is zero to prevent further processing. Task: 4862811 Forward-Port-Of: odoo/enterprise#90739 Forward-Port-Of: odoo/enterprise#87709
Miscellaneous changes
Related to https://github.com/odoo/odoo/pull/220031 Forward-Port-Of: odoo/enterprise#90736
Original PR description
Related to https://github.com/odoo/odoo/pull/220031 Forward-Port-Of: odoo/enterprise#90736