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
This idea was posted by HCL Domino Server Team as a result from a Case (CS0079329)
Can you please open a support case to investigate this issue ? Unread mark issues should not exist anymore, and if it still is, then its most likely a bug that we want to have fixed.
Having just moved multiple users from one server to another I can vouch that there is a problem with unread marks replicating.
For mail databases there were instances where the unread counts didn't match between servers. And other instances where all documents on the new server showed as unread.
There have been issues with unread marks for decades. It needs attention.
Unfortunately, no. On odd occasions users report that their unread marks (and/or unread counts) are inconsistent between replicas on different servers (even clustered ones).
As Administrator, it would be nice to be able to see and fix such issues before the user needs to report it (as this is something that lowers the acceptance of Notes for users).
The setting "Sync unread marks" does not already resolve this ?
This idea does not address the number of unread documents on the desktop/workspace, it addresses the issue that Administrators have if there are multiple replicas of a database on different servers (even cluster servers) that have different unread marks. E.g the database on Server1 has 102 documents marked as "unread" and the replica on Server2 does only have 10 documents marked as "unread" even if the database settings are all correct. This is a basic feature that should work without needing some workarounds like stacking/unstacking icons on the workspace that needs to be done by the user, not the Administrator.
The number displayed on your desktop is the last known number of unread documents. Updating this figure is not possible without actually touching/opening the database. So refreshing all unread counters for a desktop with a large number of applications would take a significant amount of time.