[prev in list] [next in list] [prev in thread] [next in thread] 

List:       zope-cmf
Subject:    Re: [Zope-CMF] DCWorkflow: End State?
From:       Florent Guillaume <fg () nuxeo ! com>
Date:       2001-12-28 17:57:11
[Download RAW message or body]

As Jeffrey mentionned, DCWorkflow is (IMO) geared towards document- or
publication-oriented workflows, not generic (WfMC-like) ones. A
publication process never really stops, there can always be revisions,
retracts, etc. What would be a relevant STOP state for a publication in
a workflow ? Maybe "archived"...

The real question is, what do you need an "ending state" for, exactly ?
Is this for interoperability with other tools ? Or do you simply need a
distinguished state upon which certain actions can be done ? In that
case what's wrong with adding an "end" state to your DC-workflows ?


Florent
-- 
Florent Guillaume, Nuxeo (Paris, France)
+33 1 40 33 79 10  http://nuxeo.com  mailto:fg@nuxeo.com


[prev in list] [next in list] [prev in thread] [next in thread]