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