Wednesday, February 19, 2025
6 changes · saas-18.1
Resolved issues and error corrections
Live chat operators can now still see and use the message composer in the Discuss app after a live chat has ended. This helps operators follow up with visitors, create leads, or send a final message when needed.
Original PR description
Follow-up of https://github.com/odoo/odoo/pull/195734 PR above reintroduced composer when livechat is inactive for operators, so that they can still make leads or post a message to visitor as a last resort. However the showing of composer was only made in chat window: the discuss app was still hiding the composer for operator on livechat end. This commit fixes the issue in discuss app, by showing the composer to livechat operators when the livechat has ended. Part of Task-4528331 Before  After 
The Discuss call sidebar now makes the collapse and expand control for participants easier to notice. Hover styling clarifies that the control is clickable without distracting from the participant list.
Original PR description
Before this commit, the button to collapse/expand participants in the discuss sidebar was not easy to spot. The button has low impact on UI, which makes sense because the most important elements are the call participants. However, the lack of style change on mouse hovering doesn't help noticing its presence. This commit improves by changing its visibility slightly on mouse-hovering the call participants. A background effect is also added when mouse-hovering precisely this button, so that it's very obvious that this is a clickable button.  
This fix adjusts the delay used when the live chat chatbot appears to be typing. It makes automated chat responses feel more natural and avoids timing issues that could affect the customer support experience.
Original PR description
Task-4577776
This fix ensures newly created partners are saved automatically when adding bank account details from an invoice. It prevents the account holder field from being left empty, reducing errors during invoice setup.
Original PR description
In this pr https://github.com/odoo/odoo/commit/0b8bd891fad1c84607fe147a32d705917341fed7 we improved the partner form but by doing that we removed the use of the auto_save_partner widget which was wrong since we need it in the following case: - Create an invoice - Create and edit a new partner - Trying to add a bank account - The account holder was empty since the partner was not saved task-4507042 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Installing the Point of Sale discount and sales modules no longer fails if the default Services product category was previously deleted. This avoids a setup-blocking error and lets businesses install these POS features even after customizing invoicing categories.
Original PR description
Currently a `ParseError` arises when the user installs the `pos_discount` and `pos_sale` modules after deleting the `Service` category in `Invoicing`. Steps to reproduce: --- - Install `Invoicing`…
Currently a `ParseError` arises when the user installs the `pos_discount` and `pos_sale` modules after deleting the `Service` category in `Invoicing`.
Steps to reproduce:
---
- Install `Invoicing` application (without demo data)
- Invoicing > Configuration > Categories > Delete `Services`
- Now install `pos_discount` and `pos_sale` modules
Traceback:
---
```
ValueError: External ID not found in the system: product.product_category_services
ParseError: while parsing /home/odoo/src/odoo/saas-18.1/addons/pos_discount/data/pos_discount_data.xml:4, somewhere inside <record id="product_product_consumable" model="product.product">
<field name="name">Discount</field>
<field name="available_in_pos">False</field>
<field name="standard_price">0.00</field>
<field name="list_price">0.00</field>
<field name="weight">0.00</field>
<field name="type">consu</field>
<field name="categ_id" ref="product.product_category_services"/>
<field name="uom_id" ref="uom.product_uom_unit"/>
<field name="default_code">DISC</field>
<field name="purchase_ok">False</field>
</record>
```
The error occurs because the user deleted the category and then installed `pos_discount` and `pos_sale` modules, which reference the missing product category.
This commit resolves the error by providing a False value for the field if the product category is missing.
sentry-6291223593
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prPayroll declaration documents now list the related employee as the contact when they are generated. This ensures employees can see their own declarations in the My Profile document area, rather than only having background read access.
Original PR description
Since the employees see in their 'My Profile' tab the documents on which they are 'Contact'. We need to set them as contact when generating declaration and not only 'read' access.