Hi Thorsten,
Thorsten Scherler wrote:
�hm, sorry, I just did a round trip:
edit -> user
publish -> user
publish -> revisor
deactivate -> revisor
...and now the user can edit again.
Maybe there was a misunderstanding :)
We do not want to allow the user to edit the document that is live.
Rather, we want to allow them to create a *new version* by editing
again. Let me try to illustrate the workflow:
user: create new doc (V1: authoring)
user: edit doc (V1: authoring)
user: submit (V1: authoring)
reviewer: publish (V1: live)
user: edit doc (V1: live, V2: authoring)
user: submit (V1: live, V2: authoring)
reviewer: publish (V1: gone, V2: live)
Where V1, V2 designate document versions.
The problem with your suggestion is that once the document is
deactivated by the reviewer, it is no longer visible in the live area.
So we have a gap between the deactivation of the original document and
the publishing of the new version.
Is it possible to implement this workflow (with reasonable effort, of
course)? Maybe by implementing or activating a revision controller in Lenya?
Thanks for help,
Joachim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
