#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

Protect 'People & Groups' tab in Admin client from accidental Replace design and Replica creation

In Domino Administrator client's tab 'People & Groups' it should NOT be possible to use menu functions to Replace design or to create a new replica.

Justification:

Consider the scenario where the human administrator works on 'People & Groups' tab but due to lack of her/his attention (being tired or stressed) administrator thinks that it is a Files tab with mail files (after all both tabs show user names in first column).

Administrator wants to replace design of single user's mail file but instead the design of the server's address book gets replaced which quickly propagates and naturally leads to servers being unresponsive.

Creation of the new replica in the same context can lead to having the second replica of names.nsf on server (while the initial intention was to create a selected user's mail file replica). It is also very undesirable situation that can lead to trouble.

Now, of course it's a human error but I've seen it happen so many times - even with experienced administrators. Needles to say, each time it leads to a disaster.

Domino Administrator client should not be prone to such human error.

  • Guest
  • Apr 9 2022
  • Under Consideration
  • Attach files
  • Admin
    Timothy Clark commented
    27 Apr 03:10pm

    I could suggest that a "Best Practise" would be to not do your admin with an id that has manager access to the names.nsf and that would work around this issue.
    But we do understand that this could be improved. ;o)