Changes for page 7. Changelog
Last modified by teamwire001 on 2025/04/02 13:12
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,138 +1,6 @@ 1 1 = (% class="mark" %)API 18(%%) = 2 2 3 3 4 -== 4.0.18 == 5 - 6 -(% class="lead" %) 7 -Jul 02, 2024 8 - 9 -**FEATURES AND CHANGES** 10 - 11 -* When clicking on an image or video shared in a chat, so far it’s opened inside Teamwire. From now on you’ll find the new option "Open file" that will allow you to directly open it in your desktop with an external app without having to download the file first. 12 -* From now on when performing a right-click on a chat bubble, a native menu will appear, showing the actions you can perform to that message. 13 -* You could already create new chat with users of your Enterprise Directory. From now on you will also be able to add them to already existing group chats. 14 -* Templates for automated registration have been added to our repository 15 - 16 -**FIXES** 17 - 18 -* Some Windows versions were not correctly named in the logs 19 -* In some edge cases the WebSockets connection of the App was lost and it was not automatically restarted 20 -* Sometimes the setting for not sending a text preview in the push notifications was not properly applied 21 -* In some Windows versions there was an edge case were some settings were not appearing in the App settings Section 22 -* When using the search bar you could find results of messages from chats that were already closed 23 -* In some cases after an LDAP sync was performed, some inactive chats appeared in the inbox until the next session was started. 24 -* Some users could have some synchronisation problems after a network failure 25 -* The setting “Send read confirmations” was visible in the App Settings section even after on dashboard the "Allow users to disable read receipts" option was disabled. 26 -* Users could send audio-messages although the “Allow Attachment” Dashboard permission was disabled. 27 -* In some edge cases the chat members in the chat settings section were not properly sorted by their first name and last name 28 -* In some Windows devices, when you clicked in a Push Notification, the app was not moved to the foreground. 29 -* In some cases you could receive an unexpected push notification from an archived chat 30 - 31 ----- 32 - 33 -== 4.0.17 == 34 - 35 -(% class="lead" %) 36 -Jun 04, 2024 37 - 38 -**FIXES** 39 - 40 -* Fix for a specific UI problem related to the indexing of search results of user IDs 41 - 42 ----- 43 - 44 -== 4.0.16 == 45 - 46 -(% class="lead" %) 47 -May 28, 2024 48 - 49 -**FEATURES AND CHANGES** 50 - 51 -* Have you missed the release of a new version of the App? That won’t happen anymore, from now on every time there is a new release a banner will appear at the top of your inbox informing you about it and allowing you to directly download it. This new feature could be turned off in you App Settings section. We’ve also created a new parameter in the config/registry file to manage that setting. 52 -* We have improved the flow for users whose session is removed: From now on, instead of showing an error, the user will be logged out and sent to the log-in screen. 53 -* Now it’s possible to log in with a one-time password and set a new password afterward. 54 -* If your administrator has set an expiration time for users' passwords, the next time your current password expires you will be able to set the new password directly from your Desktop app. 55 -* We have changed the default Windows user data folder path from {{code language="plain"}}%APPDATA%{{/code}} to {{code language="plain"}}%LOCALAPPDATA%{{/code}}. 56 -* We’ve enhanced the UI of the search results 57 -* And a few subtle updates for an even more reliable and pleasant experience 58 - 59 -**FIXES** 60 - 61 -* It was not possible to forward a video if you didn’t download it first. 62 -* In some cases when consulting the locations shared in a chat through the Shared Media section, the results were not the correct ones for that chat. 63 -* You could send a messages with just empty spaces. 64 -* In some cases you were receiving Push Notifications about messages in an archived chat. 65 - 66 ----- 67 - 68 -== 4.0.15 == 69 - 70 -(% class="lead" %) 71 -May 10, 2024 72 - 73 -**FEATURES AND CHANGES** 74 - 75 -* Based on your organisation's Privacy Settings, external users (from other organisations on the same server) are now available in the directory and can be used for chat creation. 76 -* And a few subtle updates for an even more reliable and pleasant experience 77 - 78 -**FIXES** 79 - 80 -* In some cases, when downloading media to the computer on Windows devices, the files were saved without their proper file extension. 81 -* Sometimes live locations were not updated in time 82 -* Some audio messages sent from the Teamwire Desktop version couldn’t be played properly on other devices. 83 -* When receiving a PDF in a chat, you couldn't open it the first time you were entering that chat. 84 -* In some logs we couldn’t properly collect the Windows version 85 -* There was still one edge case where some chats were not properly marked as read 86 - 87 ----- 88 - 89 -== 4.0.14 == 90 - 91 -(% class="lead" %) 92 -Apr 19, 2024 93 - 94 -**FEATURES AND CHANGES** 95 - 96 -* Now you can add/edit the chat picture of group chats 97 -* Search results are now displayed faster when using the search bar while adding new chat members 98 -* We’ve kept optimizing the reconnection of the websockets 99 -* And a few subtle updates for an even more reliable and pleasant experience 100 - 101 -**FIXES** 102 - 103 -* Sometimes you were informed by push notifications that you received a reaction to your attention message, although this reaction belonged to an attention message not sent by you. 104 -* In some cases, after reading new messages of a chat, the badge (blue dot) for the new messages was still displayed. 105 -* In some cases your sent messages were appearing multiple times in your chats 106 -* When changing the title of a Group Chat from the Webclient or an old Desktop version (3.X.X), that chat title was appearing encrypted in the new Desktop 4.0.X versions. 107 -* Sometimes the author of a message was also appearing in his read receipts section 108 - 109 ----- 110 - 111 -== 4.0.12 == 112 - 113 -(% class="lead" %) 114 -Apr 11, 2024 115 - 116 -**FEATURES AND CHANGES** 117 - 118 -* We’ve kept optimizing the reconnection of the websockets after having the computer in standby mode. 119 -* From now on, you will receive a push notification when someone reacts to one of your attention messages. 120 -* From now on, the app will be displayed by default in the language of your OS, and if it is not one of our 12 supported languages, it will be displayed in English. You can change the language in the app settings at any time. 121 -* And a few subtle updates for an even more reliable and pleasant experience 122 - 123 -**FIXES** 124 - 125 -* In some cases, the automated registration did not work correctly. 126 -* Sometimes it was not possible to perform a new login after doing a logout. 127 -* The proxy URL provided via the registry sometimes was not correctly applied to the app settings 128 -* When receiving attachments, the sender's name was not displayed in the preview of your message inbox. 129 -* In some cases some read receipts were not properly updated 130 -* In some cases, after reading new messages of a chat, the badge (blue dot) for the new messages was still displayed. 131 -* There was an edge case where your own messages were displayed as "New message". 132 -* If the title of a group chat was changed in the web client or in the Desktop 3.X.X versions, the title was displayed encrypted in the new Desktop 4.X.X versions. 133 - 134 ----- 135 - 136 136 == 4.0.11 == 137 137 138 138 (% class="lead" %)