|
|
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:
> 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.
>>
>
|
|