Saturday, January 11, 2025
3 changes · saas-18.1
Enhancements to existing features
Live chat operators can now leave a conversation instead of only hiding it, which frees up capacity when concurrent chat limits are in place. If the visitor or the last operator leaves, the chat is clearly ended and operators receive a confirmation before closing the final active session.
Original PR description
Live chat operators currently cannot leave live chats, and visitors do not systematically leave chats either. This poses an issue when a limit on the number of concurrent sessions is set, as operators cannot free up sessions. This PR replaces the unpin action with an unfollow action, allowing operators to leave live chats. task-4440366 
Deleted messages in Mail are no longer hidden completely; they remain visible as placeholders with their content removed. This preserves useful references such as starred, pinned, or historical messages while still respecting the sender’s decision to delete the original content.
Original PR description
Before this commit, deleted messages were completely removed from UI, as if they never existed. This require custom JS code to adjust counters and change display of message list to hide deleted…
Before this commit, deleted messages were completely removed from UI, as if they never existed. This require custom JS code to adjust counters and change display of message list to hide deleted messages. The main advantage of this approach is that deleted messages are visually pretty much deleted, in the sense they are not visible on UI (though we still receive messages that are considered as "empty") There are 2 main cons however with this approach: - more LOCs to pretend these messages no longer exist. - when we had a reference to the deleted message (starred, history, pinned message, etc.), it's frustrating to loose a quick access to the message and thread. Many features are expected to work for the most part even when the record is deleted by a user, but by choosing to pretend the message never exists, we also pretend that people that pinned the message and starred it never existed... Which is very annoying when the deletion of message is not decided by these people. We get that humans make mistakes, so it's good to correct themselves by editing messages or deleting them. But that doesn't mean we should go all the way: we can find a in-between solution that encompass the concerns of message author while not completely disrupting people that wanted to keep at the very least a reference to the message, even if the content is erased because mistakes happen. Task-4423068   
Users connecting an IoT box to Wi-Fi will now see a clear confirmation message instead of an endless loading spinner. This improves the setup experience by explaining that the device has joined the selected network after its temporary hotspot turns off.
Original PR description
When connecting an IoT box to a Wi-Fi network, the user is left on an infinite loading spinner due to the fact that the IoT box disables the hotspot before the user receives a response. This commit instead displays a blocking message to the user explaining that the IoT box is now connected to the desired network. task-4456765 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr