HCL Domino 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
Hi.
Does this also resolve the whole "Remain Online" situation where if there are no notifications if the user idles past the remain online time set?
Like the competing products we need to get notifications to the user's device irrespective of if the user is actively having the app on screen or not. One complaint we have heard is that after a device reboot, the user has to manually open the app again before they will get push notifications, and there isn't a forever option for "remain onine" either, which means the user has to manually call the app up once the time is met to reset the timer. While everyone is OK with the session expiring after a timer, it isn't user friendly in it's current form.
While the latter wouldn't be much of an issue if Sametime was the primary IM tool, currently due to the userability issues, it isn't and this only makes it more difficult for adoption as users don't get messages notifications in so many different use cases.
Thank you.
In recent versions of Sametime, a notification limiter was added to manage the notifications sent to mobile devices. We are focusing on improving this functionality with every release. There are scenarios where notifications are not immediately sent when multiple active clients are detected. One example is if a Connect or Embedded client is detected the most recently active, a notification would not be sent immediately to the mobile client. Once the Mobile Client is used, it's the most recent and would receive all notifications while remaining logged in from other clients. With focus on improving the limiter, new chats "not read" will be recognized, resulting in a notification sent to mobile device even when they are not the most recently active.
The limiter can be disabled, resulting in all chat notifications sent to active mobile clients. There are also policies or potentially server issues that can prevent notifications from being sent.
Setting this Idea as "Shipped", as not sending PUSH notifications to active clients would be considered a defect with version 12.0.1 FP1. If you are finding issues with the PUSH notifications for mobile clients (when simultaneously logged in anywhere) or interested in disabling the limiter, please open a support case for review.
Thank you for this feedback!
I am convinced this used to work on iphones. It seemed to stop perhaps a year back? We have ugraded to the lated server version today and turned the logs on and nothing is reported. The client log says 'INFO==> Stopping Push Notifications'
In our environment/scenario it would be good if an APNS notification is sent when HCL Notes is open but Windows is locked. Then Notes changes to the "absent" status (yellow). Here the mobile notification would be useful. Because Notes is not always closed when we are on campus on the way.
Can you discuss this with development?