Reader fields best practices

This documentation had been extended. Please follow up with Part II linked in the comments section! 

Speaking about best practices there is one item to remember.

IBM describes in the users’ guide how user can prevent others from accessing their documents by changing the security settings of the document. Unfortunately nobody mentions the implications of this action for replication purposes.

Changing the access settings within the option dialogue shown below actually creates a $Readers field within the document which restrict, beneath all possible other reader fields, the access to the document to the IDs listed.

Since the user usually does not care about access settings for the server, which is necessary for replication purposes, I consider the creation of an additional reader field containing the LocalDomainServers group within each form as a best practice to make sure that these documents are going to be replicated even if the appropriate servers or server groups are not explicitly added by the user. Same could be true for OutsideDomainServers, depending on the environment the application is going to be used.

Golden Key

One thought on “Reader fields best practices

  1. Pingback: cubetoon

Leave a Reply

Your email address will not be published. Required fields are marked *