HELP: $Readers Form Default seems to override People

HCL Domino Domino Forum
1

Hi,

I’ve got a database with 2 forms (one is normal, the other confidential). The main difference between the forms is that default read access on the form (properties) for confidential is: “[Confidential]”.

We thought that having a readers field (which is setup correctly according to the FAQ) would allow us to override the form and restrict access to just a subset of the “[Confidential]” role. It seems to be letting everyone with the role in.

We thought it was working in the test environment, but it isnt working now.

Any ideas???

Thanks.

2

Subject: HELP: $Readers Form Default seems to override People

Reader names fields are additive, unlike ACL rights (where a group can have Editor rights and an individual in that group can have only Author rights, and the individual entry wins). You will need to come up with a different strategy.

3

Subject: RE: HELP: $Readers Form Default seems to override People

Thanks Ben,

I’m sorry to be a little stupid… but can you just clarify it for me.

In this case, I don’t have two reader fields on the form, I only have the one and it has people’s names in it.

The other $Reader value seems to be coming from the form properties.

ie: If I open the form up in designer, and go to form properties and click the key tab. I have default read access for documents created with this form set to [Confidential].

Does the additive thing still apply?

4

Subject: RE: HELP: $Readers Form Default seems to override People

Yes. Basically, anybody specified ihn any way in one or more readers fields is a reader, so whether you go from the properties box or programmatically or whatever, this is additive.

5

Subject: RE: HELP: $Readers Form Default seems to override People

Gavin, it looks to me that you’re confused about what “Default read access for documents created with this form” means. You appear to believe that it means who will have read access to documents created with that form unless you add your own Readers(s) fields to override it. That’s not it, however.

First of all, a general explanation of how the term “Default” is used in form properties: It indicates a property/value which is set when a document is initially created from that form, but not reset on subsequent saves, so you can change that property/value on the document without the form changing it back later. In the case of “Default read access for documents created with this form,” the result is to add a Readers field called $Readers to all documents created with that form, and then not change it on subsequent saves, so if you change it via the document’s properties box later, those changes will stick, and not be overwritten by the form property.

Therefore, when you add your own Reader(s) fields to the document (whether you did so by adding them to the form or programmatically directly to the document), you see the behavior that Ben (and Andre’s FAQ) cite: the additive effect.

6

Subject: Thanks for your help.

Thanks everyone - your input was extremely helpful.

I think I have the problem licked.