#dominoforever | Product Ideas Portal
Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
reducing the chatlogging lifetime makes no sense at all.
This is totally contrary to the concept of Persistent Chats and doesn't solve the problem.
Attachments Open full size
4 months later .. are there any news ?
Attachments Open full size
This is on our roadmap after the November release. There are a lot of implications and policies to consider when we provide this e.g. it'll have to be a setting that can be controlled at org level by the admin due to archival needs by certain orgs. We are looking into how best to provide this option to end users considering all scenarios e.g. does the chat get deleted from the sender and all receivers client? Does it also get deleted from server side or does it get archived and flagged on server so it doesn't show up in user's clients? All this is being considered for the release after November one.
Attachments Open full size
Are there sny news? We urgently need this. Otherwise we cannot upgrade our users to Sametime 11.
Our Sametime Server 11.0FP1 is StandBy since April,
the updates Sametime 11.0FP2 is StandBy since August
But we cannot switch our users to the new server if the users cannot delete its own chat history.
Attachments Open full size
I have worked with another customer today also interested in this enhancement.
Best Regards, Keith Kopanski
Senior Product Support Engineer, HCL Sametime
Attachments Open full size
Are there any news? When can we expect the implementation? Our Sametime Server 11.0FP1 is StandBy since April, but we cannot switch our users to the new server if the users cannot delete its own chat history.
Attachments Open full size
For us having the possibilities for the user to delete themself parts and full chat history is an absolute must. Without that user delete function we will not be able to use Sametime anymore.
Attachments Open full size
Passwords do not belong in a chat - everyone should know that. But there are certainly other examples where trustworthy content may be transmitted, but the sender did not see it that way.
@Thomas
BTW: default for chatlogging lifetime is 90d / see administration guide or chatlogging.ini
CL_MONGO_HISTORY_TTL=90
Attachments Open full size
The thing is: Even if it is GDPR- compliant: Some times I chat with colleagues and they e.g chat me a password for me to test something... and this password now sits there... in their and in my chat... visible for every bypasser without any possibility to be removed before the 30day or even 7day limit...
Attachments Open full size
Nevertheless, the user should always have the possibility to delete it himself. Status changed to Likely to implement. That gives us hope. Thank you.
Attachments Open full size
Default lifetime of the chat history is 30 days. Administrators can reduce this time to (e.g.) 7 days. While the response time for a GDPR deletion request is 30 days. So even the default setting would be supporting the timeline requested by GDPR.
Attachments Open full size
Is there a plan when it will be possible that a user can delete its specific persistent chat on its own? We want to rollout Sametime 11, but if the user cannot delete it, the the user will not accept Sametime. This is very urgent !
Attachments Open full size
Please implement this as soon as possible. The users expect this. If a user couldn't delete its chat history this will result in non-acceptance and consequently in not using Sametime
Attachments Open full size
Please implement this as soon as possible. The users expect this. If a user couldn't delete its chat history this will result in non-acceptance and consequently in not using Sametime. #GDPR #DSGVO
Attachments Open full size