Subject: Synchronizing e mail notification and doc updates
We have solved this issue with a really low tech solution. In teh email that we send out we have inserted one line that says something like this — "If this link does not work please wait 1 hour to allow the database to replicate and then retry."set the wait time based on the replication interval. I do not know of any way to delay receipt of the email until the document has arrived on the particular server, but you could have a server based agent that acts on New or Modified Documents that would determine if this server is the receipiants mail server, but the effort exceeds the utility. A simple message in teh email does the trick. after awhile people learn that there is no need to immediatly click on the link but to wait for a few minutes. It’s amazing what a little training can accomplish.
Subject: RE: Synchronizing e mail notification and doc updates
We took a different approach to this - our problem was notifications going off about approvals, when the users/approvers hadn’t yet replicated - so approval - email goes out - approver forgets to replicate result next approver complains the document isn’t ready for him…
Our approach to solve was probably a little “ott”, basically our infrastructure allows for “staging servers” (basically where our agents run) - however these servers are also “furthest point” so when the document has replicated to there we send it out via an agent - all the email is simply saved in the application and a simple agent runs which sends out the emails when the have replicated to it.
but essentially yes, it’s a user education/training issue - the sooner your users understand the benefits of replication they’ll work with it!