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
An employee number will not really work for us either.
Because unfortunately it was so far that this sometimes changed for a user. If he e.g.: changed from the wage area to the salary area.
Or some have two or three, if the person has another function in the company and an extra access card.
It doesn't make sense, I know.
And we also have smaller subsidiary companies on the system that don't have an employee number at all.
And an extra list with unique numbers would have to be managed additionally.
Another point is that if a user calls because he has problems with his mail DB, I can find them relatively quickly by name. An employee number or another unique number I would have to find out first.
"Why not use a different file name at first hand that is never changing, e.g. employeeID, or a random number??"
Well, that isn't a bad idea but ironically you would need this rename function for implementing it now.
I would like to have it too. Shortname still is the default and when people marry they sometimes still change their last name. Sometimes a user asks for their webmail url, keeping the filenames in sync helps for consistency.
You want the file name on disk to be changed if the user is deleted? Why ?
User rename is a pain, admin is not in control of setting ACL-Advanced, Modify All Names(reader/Author) fields. When user is deleted, not always we whant users to be removed from Names field, but we want it to be renamed when surname changed.
Yes, you're right, that's a good idea. But I need a renaming function to change the filenames and the location documents for all the mailfiles created in my company in the last 20 (25 ?) years.
The file name does not have to correspond with the user name of the owner. Why not use a different file name at first hand that is never changing, e.g. employeeID, or a random number??