Profile document woes

HCL Domino Domino Forum
1

I have a problem with a profile document. Users with Author access cannot put the form into edit mode.

  • The profile document does not have any authors fields on it.

  • None of the fields on the form have any InputEnabled code in them.

  • The form properties has “All authors and above” checked for who can create documents.

  • The form properties does not have the “Available to public access users” checked.

  • The users are authors in the ACL

  • The users have the create documents privilege in the ACL

  • The users do not have the write public documents privilege in the ACL

The users have no problem reading values off the profile document, they are only having problems editing it with the form. Users with editor or higher access to the database have no problem at all putting the form into edit mode.

Any help or advice would be appreciated.

2

Subject: Profile document woes

Put a hidden field of type ‘Authors’ on the form. It sounds like you have a profile document for each user. In that case, use @UserName as the (computed) value of authors field (since some of the forms have been created, it’s too late to use ‘compute when composed’).

3

Subject: RE: Profile document woes

Thanks for your reply Stuart,

No this is a shared profile document for global configuration options (contents of lists, pathnames, replica IDs of other databases, etc).

4

Subject: RE: Profile document woes

So for a shared profile document, the author field will need to have a value that identifies the group or role that can edit it. for example, I use “[Admin]” to allow my administrators (those with the ‘Admin’ role) to edit the document. After you add the field to the design, use an ID with editor or manager access to the database to edit and save the profile document.

5

Subject: RE: Profile document woes

Thanks very much for your response.

So are you saying that users with a role less than “editor” cannot edit the shared profile document? The crux of my problem is that users with the “author” role cannot edit the global profile document. Giving these users the “editor” role so that they can edit it will kill all document security in my application since author fields only work on users with “author” role.

6

Subject: RE: Profile document woes

I must not be explaining this clearly…you can have exactly what you want. Leave your users with ‘author’ access in the ACL, and create an ‘authors field’ in the profile document form.

Editor ACL access allows a user to edit any document they can see in the database. Author ACL access allows a user to edit only those documents in which they are named in an ‘authors’ field type (they can be named explicitly, by group membership, or by role).

I hope that is clearer. Take a look at ‘authors field’ in the designer help for more details.

7

Subject: RE: Profile document woes

Thanks very much for your help. Based on your excellent explanation of the concepts we have now got it working properly. Much appreciated.

8

Subject: RE: Profile document woes

As Stuart suggests add an Authors field to the document, you cold just set it to “" or "/<your domain” so anyone can edit the profile document.