Comments on: Edit other peoples documents (web)

By: Mrg

Mrg — Mon, 20 Jul 2009 13:43:19 +0000

Perfect… I’ll keep them as editors for now, but will work on that method.
Mucho thanks!

By: Stiletto

Stiletto — Thu, 16 Jul 2009 16:55:30 +0000

Wait. Ignore most of that. I forgot your interests were web-based. You could probably do the same with WebQueryOpen - using it to only display the doc, not edit it. But, you’d also need to perform the same security checking with WebQuerySave (if you’re worried about users trying to circumvent your security).

By: Stiletto

Stiletto — Thu, 16 Jul 2009 15:13:13 +0000

Relatively simple. Just use some code in the PostOpen event to set the EditMode property of the uidoc to True if they’re allowed to edit or False if they’re not. Just remember to perform similar check in the QueryModeChange event, too.

What I do is declare a variable called ReadOnly. Then, in QueryOpen, I check if it’s a new doc. If it is, I set the variable to False. If it’s not, then I check if the doc is being edited by someone else (record lock). If it is, I set the variable to True. If it’s not, then I do my other security checking and set the variable appropriately. Then, in PostOpen, I check the value of ReadOnly and set EditMode appropriately. In QueryModeChange, if ReadOnly is True, I set Continue to False. HTH.

By: Mrg

Mrg — Thu, 16 Jul 2009 14:28:16 +0000

Yeah, I see what you are saying…
As for Roles, that could be a nightmare, because you’d have to add all the individuals to the ACL, and then assign the Role.
For now I’ve changed them to be editors. We already have a system that to access to edit their own documents, they are only shown documents relative to them by using the an ‘embedded selection’ with a ’show single category’ formula. So it’s not like they can see other users docs.
Could you please elaborate on… “…use code to keep people out of docs that you don’t want them mucking with.” ?
Thanks again…

By: Stiletto

Stiletto — Thu, 16 Jul 2009 13:32:08 +0000

Well that really depends on the security requirements of your app, now doesn’t it? If it’s okay, or even desirable, for someone with editor rights to be able to edit any document that someone else created, then you’re all set. If not, then your faced with some other options. For example, you could still grant the editor rights, and use code to keep people out of docs that you don’t want them mucking with. Or, you could leave everyone with author rights, and use code to alter the list of authors on a doc to select the people that you want to allow to make changed to it. As for roles, you might be able to use them to simplify matters somewhat, but when it comes right down to it, the choices are still the same.

By: Mrg

Mrg — Wed, 15 Jul 2009 13:22:34 +0000

Hmm… So how dumb would it be to change them over to an editor? What sort of doors/pitfalls am I opening if I did something like that?
Would it help at all if I created a Role for *?

By: Stiletto

Stiletto — Wed, 15 Jul 2009 13:12:09 +0000

If a person has “Author” rights granted in the ACL, then the only documents they can edit are their own documents. In order to be able to edit documents that have been created by somone else, the person needs “Editor” rights granted to them via the ACL.

By: Mrg

Mrg — Tue, 14 Jul 2009 13:32:49 +0000

ACL as such:
Default: No access; *: Person Group/Author — Create, Delete, Replicate or copy documents.
No SSO.
Users can browse the site anonymously, but to enter a certain section to view/create/modify, they must login to the site. (I use the !Login url cmd.)
Once they have logged in, they are able to view/create/modify. They have no problems with their own records. And they can view other people’s records, but if they click to edit, they are prompted to log in to the site. The only way around this is to either enter in the credentials of the author of that record, or the admin to log in.
I had thought when I first developed this, other staff could edit other records, but now when I test again, it’s not working.