Views in HCL Domino can look clean or confusing depending on how you handle categories. A common issue is empty categories that appear for some users and disappear for others. This happens when the view depends on documents the user cannot read.
Domino shows a category only when at least one document in that category is visible. If all documents are restricted by Readers or Authors fields, the category stays hidden.
The problem starts when a response document is readable but the main document is not. The user can open the response through a link or lookup. The user cannot see the main document in the view. The category that the main document belongs to stays hidden. Domino treats the category as empty even if the response document exists. The response document does not create a category on its own.
You will notice this when users report that they see a response but cannot find it in the view. They think the category is missing. The real issue is access control on the main document.
You can reduce this problem with some simple checks.
• Keep Readers fields aligned across main and response documents.
• Avoid workflows where main documents are more restricted than their responses.
• Review the view selection so it includes documents users can read.
• Test with different user roles to see how categories collapse.
If you want to expose response documents even when the main document is hidden. Change so response documents is not displayed in a hierarchy . If you want predictable category behavior, give the parent and response documents the same visibility thru the readers and authors fields.
This keeps your views stable. It keeps users from wondering why a category disappears even when they know a response exists.
0 Comments.