I want a property on databases that can prevent users from replicate local databases in to a server if it’s long time since they replicated.
This to prevent that old and deleted documents reappear in a database if a user has been away from the office for some months.
Admins need a way to prevent users from replicating a local db replica with the server if X days has passed since last replication. The trick here is that the last replication date/time does not get wiped out if the user clears replication history.
At the moment it is not possible to enable a database for scheduled replication or to control the 'Receive documents from server' and 'Send documents to server' flags on the basics tab of the replication settings dialog, using either Lotusscript or even C-API (at least none that I know of)....
I wish the Location document would include a section for how often mail should be sync'd. This should not be tied to other replication cycles, even High priority replications.
When mail is replicated on its own cycle, it should replicate even if another replication is occuring - never block ...
I love the new action in the Inbox in Notes Mail that replicates mail now. However, I work in several discussion and production databases where I find myself looking for the yin-yang "replicate now" icon that I've become used to in the Inbox. Often, I want to shut down but ...
Whenever you create a new local replica of a database, Notes automatically adds the database to the Replicator page so that future scheduled replications will include this new replica. For a person who uses only 1 Location, this is fine and works as it should be.
But if you ...
To manually replicate - if not set this option, then after the analysis (comparing the replicas) to issue a message about this situation with a choice of actions:
F9 to refresh document in read mode to display changes made after it was opened similar to view refresh.
If you have a document open and Notes detects someone has updated the document, display an indicator that the document has changed similar to the blue circular arrow indicating to refresh a view when the view has changed. Also provide ways to refresh (i.e. press F9, etc.) what is displayed ...
In a Citrix-environment there is no need for for the user to create replicas. It would be great to be able to hide "File - Replication - New replica..." on the client to prevent users from creating replicas of their mailbox on the file-server by mistake.
Laptop users may have ...
Asynchronous replication needs to become a real, supported function of the mail file. It's a great feature but very difficult to find documentation on it. I am hesitant to deploy to users without confidence that it will work as it should and be supported by Lotus. Asynchronous replication is event-based ...
When opening a truncated document, you can "retrive entire document" from the actions menu. If you have a replica of your mailfile on more than one server you will be presented with a list of servers. In case the server you selected is not available Notes prompts an error instead ...
Please update the unread marks on the chicklets when new/modified documents are added to the local database and poll unread counts for server ones (only displayed chicklets -> stacked DBs).
It's a pain to wait for F9 to complete and especially for local DBs notes already ...
I'd like an option to change the replication settings on the fly.
I update a template with a minor change - let's say a new column in a view
I refresh the design from the template of the app
I hit replicate, and it has to go through ...
When I choose to replicate a server-based database, I wish Notes would default to ANY other server than the one I'm on. It may well guess wrong, but if it acts as it does now, it's always going to be 100% wrong.
May it should just pick the first ...