#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

Merge names.nsf contacts into maildatabase.

Problem: a secretary updates the contact information of her supervisor in his names.nsf. Traveler does only sync from maildb.nsf to mobildevices. But the change is not synced from names.nsf to maildb.nsf because this is only done in the replicator page of the supervisor, and he is on the road with closed Laptop... 

Very bad conception and probably the reason was in the time where not "allways online" was usual....

Today the change of a contact MUST be in a few seconds on all connected mobile devices.

so truncate all this overdue concepts and streamline domino/notes.

  • Guest
  • Jan 28 2020
  • Already exists
  • Attach files
  • Guest commented
    30 Jan, 2020 07:13am

    The main problem why nobody uses the contacts in the maildb.nsf is the contact icon on the left side of notes. It opens the names.nsf. Everybody from director to assistance knows this button. But if the sync of the users local replicator item ("contact sync to maildb.nsf") is not activated no changes get synced to names.nsf if the director changes (on the road) a contact. Then he called me why this does not work.

     

    The sync possibilities are to much in the age where you are every time online. It is not necessary anymore to have this lot of possibilities. (i.e. deactivate a replicator item or additionaly a "high priority" sync, or even a sync from this hour to this hour. (sync makes sense shurely 24h in 2020). If i dont want a ring on my phone i make it silent...

  • Guest commented
    29 Jan, 2020 03:29pm

    ok, i understand the concept of delegated access. The names.nsf is of course on the server while adding a user to support roaming of the user. My intention was to remove the two places of contacts because the concept is riddled with mistakes. Either with duplicates/missing (when not synced properly) and also with misleading of users. This does not work properly. Could you explain why it must have two contacts locations for one account?

  • Admin
    Thomas Hampel commented
    29 Jan, 2020 01:30pm

    Delegated access is managed by the owner of the mail file. It is possible to delegate access to the entire maildb or just calendar/todo/contacts. So in this scenario the secretary would have delegated access and would be able to manage contacts in the mail file of the user.

    the personal names.nsf is supposed to be located only on the workstation of the user and is not supposed to be shared by replicating to a server. So this idea is being closed with either 'already exists' or 'shipped'

  • Guest commented
    29 Jan, 2020 08:55am

    The secretary/assistance shall not have access to maildb.nsf. In common, the sytem is to complex.

  • Guest commented
    28 Jan, 2020 05:41pm

    Why does the secretary have to access his names.nsf ? With delegation in place, she accesses directly the "Mail Contacts" part inside maildb.nsf, which is then directly accessible on all connected mobile devices.