Strange logic

As every morning, I read the new entries in the Lotus Software KnowledgeBase. Today I stumbled upon one entry and even reading it again and again, it still seems to be a bit obscure.

Deleting a person using Adminp process removes the user name from fields on custom application.

When a user is removed from the Domino Directory using the “Delete Person” button, AdminP removes the user’s name from a Names field in a custom application.

This is working as designed.

You need to change the ACL setting on any application where you don’t want specific Names fields updated :

Go to the application -> Access Control->Advanced-> Action.  Set this to “Do not modify Names Fields.” This setting prevents AdminP from modifying the Readers, Authors, and Names fields.

OK, this is clear so far. But then the next sentence

Another option is to set the field to “Modify all Readers and Authors fields,” which will prevent AdminP from modifying Readers and Authors fields.

What kind of logic is this? I explicit say “YES, go ahead and modify all Readers and Authors fields!!” and this will AdminP prevent from doing so ?? I don’t get it!

{Technote #1288486}

3 thoughts on “Strange logic

  1. Hello

    Thx for this news

    can you post the url for acces to the new lotus software knowledgeBase.
    I try de find them.

    Thank you

  2. I believe the technote has a typo. I think what they mean tto explain is that if the customer application’s Names field is not a reader/author field, then you can use “Modify all Reader / Author fields”. Domino will not clear the name from the custom Names field, since it isn’t a reader/author field.

    The Admin help is more clear:

    Each server in the domain deletes the name from Reader / Author fields of databases for which it is an administration server and that have the advanced ACL option “Modify all Reader / Author fields” selected.

Comments are closed.