Domino 9 und frühere Versionen > Entwicklung

Leserfeld: kann trotzdem Doks sehen

<< < (4/5) > >>

Manfred Dillmann:
Hallo Semaphoros!

>>Problem ist ganz eindeutig, dass die Hilfe in diesem Zusammenhang kaum als Hilfe bezeichnet werden kann, die Infos sind total zerstreut und überall, wo diese Felder erwähnt werden, nicht vollständig.<<

Hat man das schon jemals anders erlebt? ;-)
Oft erzählt einem die Hilfe leider nur, was man eh schon wusste oder sich gedacht hat. Aber die Kerninfo fehlt dann leider sooooo oft...

Wenn mir sowas unter kommt, mache ich mir halt schnell eine kleine Test-DB und kläre das so ein für alle mal.

Gruss
Manfred

Glombi:
Hier die Lösung aus der Knowledge Base (#113202 vom 24.04.2001):

Author Name Fields, Reader Name Fields and Document Security

Problem:

If a document contains an Author Names field and a Reader Names field, which one takes precedence in terms of reader access?

Solution:

Reader Access is cumulative.  If UserA is listed in the Reader Names field and UserB is listed in the Author Names field of a document then both UserA and UserB will be able to read the document.  UserB will also be able to edit the document.

This scenario also holds true for a Reader Access List created at the form level and an Author Names field.


Grüße
Andreas

Glombi:
Und das ist sicher auch interessant (#113732 vom 21.01.2000):

What is the Difference Between Reader Name and Author Name Fields?

Problem:

What are Reader Names and Author Names Fields and how are they different?

Solution:

Reader Names fields determine who may read a document and Author Names fields determine who may edit a document.  Both types of fields can contain combinations of individual user names, server names, group names, and access roles.  Documents and forms may contain more than one of either kind of these two fields.

You can read a document if any of the following are true:

1.   The database is local to you (i.e. you are not accessing it via a Notes Server).

2.   There is no Reader Access List for the document, and you have at least Reader Access to the database.

3.   There is a Reader Access List, but you are included in the form's Reader Access List (Design>>Form Attributes>>Read Access), or in any of the Reader Names fields in the form, or in the document's Reader Access List (Edit>>Security>>Read Access), or in any of the Author Names fields in the form.  As stated above, you can be included as part of a group or role, in addition to having your name specifically written in.

You can edit a document if any of the following are true:

1.   You can read the document (see above) and you have at least Editor Access to the database.

2.   You have Author Access to the database and you are included in an Author Names field in the form / document.

Notes to Application Developers or Managers:

1.   When creating Reader or Author Names fields, it is wise to check ON the Allow multi-value check box otherwise, you may end up with an invalid list of people, servers, groups, and roles who can access that document.  In such a circumstance, you would need to access the database locally (at the server's client) to fix the problem (presumably by running a macro or performing a Tools>>Refresh Fields after making the appropriate changes to the form).

2.   No one can edit a document which they cannot read.

3.   An Author Names field grants reader's rights as well as author rights.

4.    Failure to include a person/group/role/server from a Reader Names or Author Names field or Reader Access List denies the appropriate access to the person/group/role/server.

5.   Users with Reader Access to a database can never edit any documents.

6.   Running aa agent which places names into a Reader or Author Names field will result in that field being a plain Summary Text field.  To make the field Summary Read-Access Names or Summary Read/Write-Access Names, respectively, you would have to either:

-   manually edit and save the document,
-   in Notes 4.x or 5.x, create an agent which runs @Command(ToolsRefreshSelectedDocs) or @Command(ToolsRefreshAllDocs) to refresh the Data type of those documents.

Lotus Quality Engineering is aware of this issue.

7.   The API can place names into a Reader or Author Names field and preserve the special Summary status of the field.

**   Note:  The LotusScript back-end methods for populating Reader and Author Names fields do not preserve the Summary status unless the New method is used, in combination with the IsReader or IsAuthor property, to create the field.  If this is not the case, the IsSummary flag must be set manually to TRUE.

8.   The creator of a document cannot edit the document after it is saved unless he or she is included in an Authors field or has Editor access to the database.

9.   A document with multiple Reader Names fields or Author Names fields will allow access to the entire list of these fields.  Notes concatenates these fields when determining who may read or edit a document.

Semeaphoros:
Manfred:
Stimmt, wobei ich das nicht wirklich als ein Problem empfand und deswegen nicht weiter überprüfte. In so eine Situation wie TMC hier geraten ist, bin ich ganz einfach nie reingelaufen, somit ergab sich kein Anlass daran zu zweifeln und somit auch kein Testbedarf.

Andreas:
Das gibt mal eine offizielle Dokumentation, das ist gut so, trotzdem, woher kommt diese Aussage über die Autorenfelder? Diese Aussage ist derart verbreitet, dass sie an "hevorragender Stelle", sprich sehr nah von Lotus/Iris (das ist eindeutig vor der Integration in die IBM Struktur) aufgetaucht sein muss.

Semeaphoros:
Danke Andreas, Dieses zweite Dokument ist das erste Mal, dass ich die Sache wirklich durchgehend in einem Dokument beschrieben sehe. Das würde doch eigentlich in die Hilfe gehören. Es zeigt übrigens auch, dass das Testen in diesem Bereich recht schwierig ist, da es eine Unzahl von Kombinationen gibt: Dokument selbst, Dokument-Access, Form-Felder, Form-Access und ACL und erst der Coktail von allem zusammen ergibt das Endresultat.

Navigation

[0] Themen-Index

[#] Nächste Seite

[*] Vorherige Sete