Random fields are not updated as expected when documents are edited by users with Author access
On your Lotus® Domino® server, you have a secondary address book (listed in a Directory Assistance document). You find that when a user with Author access attempts to edit a document within the secondary address book, that some of the field updates are not saved. On closer look, you find that the relative fields have the flag Summary Protected, even though the field's Security Options property is set to "None". The Summary Protected flag is only expected in cases where a field's Security Options property is set to "Must have at least Editor access to use".
This issue was reported to Quality Engineering as SPR# SLED6LRN9K, and is fixed in the following releases:
Domino 6.5.5 Fix Pack 2 (FP2)
Domino 7.0.2 Fix Pack 1 (FP1)
Excerpt from the Lotus Domino fix lists (available at http://www.ibm.com/developerworks/lotus):
SPR# SLED6LRN9K - This fix stops Domino from incorrectly setting items protected when a note was modified by a user with Author access and the database was included in Directory Assistance. The item name was also not a reserved item name.
Refer to the Upgrade Central site for details on upgrading Notes/Domino.
This issue has been observed in cases where the relative form's design has been modified from the original Domino Directory template design (pubnames.ntf). One or more fields which were originally set with Security Option property of "Must have at least Editor access to use", have either had the property set to "None" or the field has been removed from the form altogether. Additionally, the issue may be observed in a new additional form design which was not included in the template design.
This issue can be avoided if one of the protected fields (see the list below) from the original Domino Directory template design is added to the form design with the Security Option property set to "Must have at least Editor access to use". The field should be added with the correct Type (see list below). In cases where the field is already present in the form's design then be sure to enable the Security Property as noted. In either case, the field can be hidden if desired.
Note: If the issue continues to occur with a form based on a form design from the Domino Directory template (Pubnames.ntf) then it is suggested that the form's original design be reinstated to avoid the issue.
The following is a list of the fields that are protected in the Domino Directory template design. They are listed by Type.
The Security Options property is found on the Beanie tab of the Field Properties, when a field is selected in a form opened using the Lotus® Domino Designer® client.
|Messaging Applications||Lotus End of Support Products||Lotus Domino||7.0, 6.5|
Translate this page: