Are you deploying a bookmark database to your users via replication?

If yes, what ACL do you use?

I tried setting the ACL for -Default- to Reader but get errors because Notes apparantly creates “history” documents (Form=”HistoryListEntry” – scanEZ to the rescue) in the database so Reader isn’t enough. I guess I could allow higher access but how do I then control the amount of “history” documents created and avoid replicating them to all users (without setting selective replication formulas)? The whole idea is to have a bookmark database you can control centrally and push to users using replication – I hope this isn’t a pipe dream

Insights?

Published by

lekkim

Positive, competent, out-spoken, frank and customer focused architect and developer with a strong foundation in web, cloud and product development. I'm a strong advocate for API first and cloud based solutions and development. I have a knack for being able to communicate and present technically complicated matters in conference, customer and training settings. I've previously acted as team member and leader in a product organisation.

2 thoughts on “Are you deploying a bookmark database to your users via replication?”

  1. We use policies and desktop settings to push out shortcuts and welcome page – is this what you’re after?

  2. Yes – but more some information on the ACL you have set on the bookmark.nsf database you replicate to your users. Do you have any issues with lots of history documents replicating between clients?

Comments are closed.