Welcome to the #dominoforever Product Ideas Lab! 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 jointly by the IBM & 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.


Add status field (Active/Inactive) to Person document

Many staff are contracted as a fixed term hire on a repeating basis. (i.e. hired for a fixed period of time e.g. 3 months each year)

The ability of a Domino Administrator to be able to change the status of a person from Active to inactive  inactive to active would remove the need to delete the person and then re-register them the next time they are hired again.

When a person document is inactive it should not appear in Notes user email lookups, directory lookups or email delivery.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Oct 13 2018
  • Attach files
  • Admin
    Thomas Hampel commented
    16 Oct 09:47

    What is the reason for keeping a person document in the Domino Directory then if you don't want to have the name showing up in name lookups, etc?

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    16 Oct 11:15

    Hi Thomas thanks for your question.  The benefit of being able to keeping a person document is to

    1. Save the time not having to re-register the person including any alias' names that may have accrued due to historic renames.

    2. This also preserves the person's email history as their mail db is not deleted.

    Hope that assists.

    Mark

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    16 Oct 11:35

    Also : the person's name is kept in ACL, ACL groups and delegation settings.

  • Admin
    Thomas Hampel commented
    16 Oct 12:15

    you could remove the person document, e.g. cut/paste it into another backup nsf. However, the user would still have access, the notesID would still be alive. 
    To deny access, add the user to a deny access group.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    16 Oct 12:33

    Thank you for the tip but this is what we do today. We would like a friendlier, easier and more intuive way of doing it.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    17 Oct 00:14

    Yes that seems like a messy workaround. where a Active/inactive status field on the person document would be much simpler.

    Putting the person in a deny access group stops access at server level, but still allows other users to see and select the person from the Dom dir. when they are inactive.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    25 Oct 19:35

    Actually one way to implement it could be to change the form & type  to "PersonInactive" that would remove it from all views. Than have a separate view to just show the person-docs there to be able to re-activate them.

    Just as an idea how to implement it.

    We have many customers where removing users completely who are in a long term away situation is causes a lof of overhead.

    On the other side this would still cause non delivery reports. Having a way to return a proper "not availability message" would be very helpful! Having a separate field with that information could be an idea. But than the user needs to be listed in $users I guess.

    It's not a simple change if it should make sense and help.

    Else doing a cut and past into a separate directory would give us the same functionality. If this would be implemented it should add some value.

    [ Daniel Nashed / blog.nashcom.de ]