I agree: add a placeful workflow policy via Site Setup then on the folder in
question use the State->Advanced menu to add that policy on the current folder.
You will be able to select your static workflow for the current folder and any
other workflow you want for children of the current folder.
Kim
On Dec 19, 2011, at 6:09 AM, Mikko Ohtamaa <[email protected]>
wrote:
>> in my intra-net there are certain folders that only I should be able to
>> change.
>> Therefore, I created a new workflow state 'static' in which only I have Add
>> permissions, and applied this workflow state to these nodes. However, these
>> permissions propagate to child nodes that have the 'inherit permissions'
>> checkbox
>> set. I would like these child nodes to inherit permissions, but not from this
>> specific 'static' parent node. Is there some way to exclude a node from the
>> inheritance chain?
>
> One way is to re-define (all) child content types workflows to not to
> have "Acquired" checkbox ticket.
> Local workflows could work here, but I am not expert on how they work.
>
> -Mikko
>
>>
>> Thanks
>> Maarten
>>
>> _______________________________________________
>> Product-Developers mailing list
>> [email protected]
>> https://lists.plone.org/mailman/listinfo/plone-product-developers
>
>
>
> --
> Mikko Ohtamaa
> http://opensourcehacker.com
> http://twitter.com/moo9000
> _______________________________________________
> Product-Developers mailing list
> [email protected]
> https://lists.plone.org/mailman/listinfo/plone-product-developers
_______________________________________________
Product-Developers mailing list
[email protected]
https://lists.plone.org/mailman/listinfo/plone-product-developers
