Locking Workflow (0.2)
- Locking Workflow download link: http://plone.org/products/lockingworkflow/releases
- Homepage of Locking Workflow: http://plone.org/products/lockingworkflow/
- Locking Workflow repository: https://svn.plone.org/svn/collective/LockingWorkflow
- Description source: https://svn.plone.org/svn/collective/LockingWorkflow/trunk/README.txt
The locking workflow is a simple two state workflow (unlocked and locked)
restricting the edit permission in the locked state to the newly introduced
Editor
role.
Per default, nobody has this editor role but it gets assigned as local
role to the current user as soon as (s)he invokes the edit action which also
triggers the lock
transitions which takes the content item into
the locked state. Saving the edit form triggers the unlock
transition which takes the content item back to the unlocked
state. The unlock
transition can also be triggered TTW like any
other workflow transition.
The locking workflow can be combined with any other workflow as it exploits the fact that content types can be subject to several workflows at once.
Caveats
When adding the locking workflow to a type in ZMI make sure that you also
change the edit action of this type to invoke lock_and_edit
,
the form controller settings for the actions of lock_and_edit
and the form controller settings of the method that invokes the view after
successful editing (for Archetypes that's validate_integrity
).
If you add further types in the locking workflow's config file instead, a
simple (re)install should take care of all of this.