Sametime 12.0.2 offline chat

I do some tests with ST 12.0.2 before rolling out to customers live system (docker/kubernetes).

With 12.0.2 you made a great job to change sametime policies easier with the admin ui.

It seems that you also removed some (old?) entries from the polcies.users.xml that exists in ST12.0.1FP1 and before versions.

> e.g. im.enableOfflineMessages: current-value="1"

Now i am not sure if this is working as designed

This worked from the Notes client in Sametime 12.0.1 FP1

Also an additional question - there are new features within the browser client

> Delete last chat / chat deletion & chat reactions

I love these new features, but i see big problems for customers using the Notes embedded client or mixed environment, because of different behavior (this will create support tickets.)

hi Alexander -

Yes , we removed that policy item as it is now defaulted to being enabled. You can always add it back to the policy.xml file manually and we can see if that resolves your issue with the older client.

Please open a case if you need assistance with this.

On the second question - you are correct in that the Installed clients can only view reactions and do not get the ability to delete messages - this is something we plan to correct in an upcoming release. These features are currently 'web only'.

Hello Alexander,

For 12.0.2, reactions and deletions were features added to Web, PWA and Mobile clients. We are evaluating and working on better supporting these features from Connect and Embedded clients and I encourage voting on this idea: https://domino-ideas.hcltechsw.com/ideas/STC-I-546

In Notes 14.0 clients, adding the following parameter will enable the clients to view deletions and reactions:
com.ibm.collaboration.realtime.chatwindow.conversation/isChatReactionPrefEnabled=true
This does not allow these actions to be performed, but supports viewing them when they are performed on the supported clients.

Thanks,
Trevor

Did a little internal testing -

a) the policy item still appears to be in the xml file - but is not displayed in the UI, as it is enabled by default and should not be disabled.

b) in some client testing - the only time we got the message you display above is from what appears to be invalid buddylist entries - possibly old/corrupt or for some reason the lookup for the entry failed.

Try re-adding the user to your buddylist and see if you can then initiate an offline message to them.

Please open a case if you need assistance.