Re: Workflow permissions per item doesn't work correctly!

["Jeff Garman [MSFT]"]

There are a couple of things that I would suggest here:

> I ran a couple of tests on a test server that I use and don't see exactly 
> what you are seeing.  Is there anything else that is running on this 
> Public folder?
The ItemAuthors and ItemReaders should only refer to Item level permissions 
and provide the interface to manipulating those permissions.  Looking at 
items in the Public Folder using the tool below, I do see the inherited 
permissions, specifically the permissions that are associated with the item 
level permissions that are in place
> This also leads to my next question, what tool are you viewing these 
> permissions of these items with?  I looked at them using a tool that we 
> often use in support, PFDAVAdmin.  You can try this here:

http://www.microsoft.com/downloads/details.aspx?FamilyID=635be792-d8ad-49e3-ada4-e2422c0ab424&DisplayLang=en

I would have look at the permissions using something like PFDAVAdmin and 
verify what you are seeing.  And then you can compare this with with what 
you are seeing on that other server, and should be able to tell the 
differences.

--
-Jeff


"topper" <topper@xxxxxx> wrote in message 
news:%23vvv51f8GHA.5020@xxxxxxxxxxxxxxxxxxxxxxx
> Jeff, thank you for answering, but i think it is not so simple in my case.
>
> I'll try to describe it detally.
> I use WorkflowSession.ItemAuthors and WorkflowSession.ItemReaders 
> collections for manipulate of item permissions, but
> after clear and set permissions by .ItemAuthors and .ItemReaders 
> collection and after workflow state transition completed, item has also 
> folder permissions (as additional) =(
>
> I'll show it in my next workflow script code example:
> '
> ' Current Folder has access permissions for 4 custom users/groups.
> ' Default and Anonimous accounts haven't any permissions on this folder
> '
> ...
> ' check accounts count before permissions modification
> WorkflowSession.AddAuditEntry "Authors count - " & 
> WorkflowSession.ItemAuthors.Count    ' result - 5
> WorkflowSession.AddAuditEntry "Readers count - " & 
> WorkflowSession.ItemReaders.Count   ' result - 5
>
> ' clear permissions
> WorkflowSession.ItemAuthors.Clear
> WorkflowSession.ItemReaders.Clear
>
> ' check accounts count  again
> WorkflowSession.AddAuditEntry "Authors count - " & 
> WorkflowSession.ItemAuthors.Count    ' result - 0
> WorkflowSession.AddAuditEntry "Readers count - " & 
> WorkflowSession.ItemReaders.Count   ' result - 0
>
> 'sets permissions
> WorkflowSession.ItemAuthors.Add  "USER1@MAILSRV", 0
> WorkflowSession.ItemReaders.Add  "USER1@MAILSRV", 0
>
>
> ' check accounts count  again
> WorkflowSession.AddAuditEntry "Authors count - " & 
> WorkflowSession.ItemAuthors.Count    ' result - 1
> WorkflowSession.AddAuditEntry "Readers count - " & 
> WorkflowSession.ItemReaders.Count   ' result - 1
> ...
>
> As result, item will have 5 accounts that have access to item - 4 of them 
> automatically sets (and i don't know why!)
>
> I was test this workflow application in 2 different domains (W2k3 SP1, 
> Exch 2k3 SP2). In one case permissions work correctly, in another - don't 
> =(
>
> First domain has NATIVE functionality mode and MIXED functionality mode 
> of Exchange (item permissions work correctly)
> The Second has domain and Exchnage in NATIVE func. mode (item permissions 
> don't work correctly) =((
>
>
> Why it has strange behavior of  item permissions?
>
>
>
> "Jeff Garman [MSFT]" <JeffGa@xxxxxxxxxxxxxxxxxxxx> wrote in message 
> news:uiqV0657GHA.244@xxxxxxxxxxxxxxxxxxxxxxx
> > It depends on what you are doing in your workflow process.  Have you 
> > changed any permissions in your workflow at all?  If not, you may be 
> > seeing that you are getting the default from the folder.
> >
> > This is noted here:
> >                                 msdn.microsoft.com/library/default.asp?url=/library/en-us/wss/wss/_cdo_iworkflowsession_itemauthors.asp">http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wss/wss/_cdo_iworkflowsession_itemauthors.asp
> >
> > ItemAuthors Property:
> > You can use this collection to maintain per-item modify and delete 
> > privileges. When the collection has members, only members of the 
> > collection can modify or delete an item. This allows you to give certain 
> > users or groups temporary exclusive author access to an item. When this 
> > collection is empty, the default author privileges for the folder apply. 
> > This collection uses the properties and methods of the IMembers 
> > interface.
> >
> > You can also clear, add, and delete privileges using the IMembers 
> > interface in the workflow project:
> >
> >                                 msdn.microsoft.com/library/en-us/wss/wss/_cdo_imembers_interface.asp">http://msdn.microsoft.com/library/en-us/wss/wss/_cdo_imembers_interface.asp
> >
> > - Jeff
> > "topper" <topper@xxxxxx> wrote in message 
> > news:%2325nbAf7GHA.728@xxxxxxxxxxxxxxxxxxxxxxx
> > > Hello All.
> > > Why permissions that sets to public folder inherited by item 
> > > permissions? I sets permissions per item by workflow script but folders 
> > > permissions also sets (automatically?) to item after workflow 
> > > processing.
> > >
> > > Why it has strange behavior?
> > >
> > > Thank You?
> > > Alexander.