[Zope-CMF] (DC)WorkflowTool / CatalogTool suggestion

Big Sebastien.Bigaret@inqual.com
23 Sep 2001 17:12:55 +0200


    Hi,

I have a question or, say, a proposal, about the behaviour of workflows'
catalogued variables and the CatalogTool, more precisely with DCWorkflow
instances. Well, first at all, I am a zope rookie (wahoooo) but still a cmf
newbie, so don't be too cruel ;)

  To my understanding and through source code reading, it appears to me that
even if you can specify that a workflow variable is 'available to the
catalog', no particular action is taken to make it *actually* available.

  I understand well that, since the CatalogTool and the default workflow are
part of the CMFCore and 'review_state' is the only variable in the supplied
default workflow which was made available to catalog, this 'review_state'
field index can be hard-coded into the catalogTool indexes.
  TTW-configurable DCWorkflows are different: this (wonderful) product allows
you to make your own workflow definition. In particular you can make some of
your workflow's variables 'available to catalog'... and maybe think you're
done, but you're not: you still have to manually add those variables to the
catalogTool.
  NB: same thing about state variable since DCWorkflow.getCatalogVariablesFor()
always provides it.

  Ok, this is not *that* bad, at least one is quickly aware of this. However,
wouldn't it be nice if DCWorkflow-instances automagically add these
'available-to-catalog-variables' to catalog indexes (and possibly metadatas,
for state variable e.g.) ?

  Or am I missing some important points of Zope/CMF Zen?

   Thanks for bringing the light!

        Zopely yours,
                        SB aka Big.