Where should I request new functionality: doc.replicate(server)

I would love to see a new method: doc.replicate(server).

We have a very disparate organisation - up to 20 servers globally - and many workflow and reminder apps, that send emails.

Inevitably the email arrives with the recipient before the document ( or change to document ) replicates to the correct server, and we end up with confused users, or replication Save conflicts.

Having investigated several methods of making sure the mail arrives at the same time as the document, It seems to me that my only solution is a doc.replicate method, but I cannot see where is the best place to go to request that, or to find out if this will be in a future release.

Many Thanks

Subject: RE: Where should I request new functionality: doc.replicate(server)

The best way to request features is to come to Lotusphere and talk to the developers and product planners in person. The feedback we get there informs our product planning process – we collect all the suggestions we have gotten and have long meetings to evaluate them.

Another good way is to participate in a beta program, and enter feedback in the beta forum.

For programming what you want to do with existing functionality: you can, of course, use LotusScript replicate the whole database, which is quick if people are doing it all the time, and will get whatever document you wanted updated.

Clustering your servers will let you make the replication happen faster.

Subject: Where should I request new functionality: doc.replicate(server)

It comes down to a training issue for your end users or a design issue. If you’re sending e-mails for workflow, instead of users firing off the e-mails just flag the documents then run agents to fire off the e-mails on a delayed schedule to allow time for the docs to replicate to all servers. If you need it to happens fatser then you need to re-evaluate your replication/server topology.

Subject: Where should I request new functionality: doc.replicate(server)

Take a look at ‘db.Replicate(server)’ - which already exists.

( I would think that replicating multiple single documents would be a lot more overhead that replicating the database. )

Set up a background agent that calls ‘db.Replicate(server)’ for each server, THEN send the workflow email.

The server name must be specified in its canonical format.