[Zope-CMF] DCWorkflow; missing skins. (content_hide_form)

[seb bacon]

A bit more info to add which may be useful...

the 'review_state' is just a catalog index.

the WorkflowTool has a property, _chains_by_type, which you can use to
'chain' workflows together for a particular content type, like:

 tool._chains_by_type['FooPage']=('default_workflow','bar_workflow')

(or of course you can put them in the ZMI version of the workflow
tool). the 'notify*()' methods are called on each of the workflows in
a chain, one by one. 

seb

* Erik Enge <erik@thingamy.net> [010710 13:34]:
> [Erik Enge]
> 
> | I can't figure out how content and workflow is hooked together.
> | 'review_state' for example; how is that related to a specific piece
> | of content.  *scuba-mode*
> 
> I figured it out, in case you were wondering.  :)
> 
> PortalContent.py's manage_afterAdd() does some jugling to find the
> WorkflowTool and the workflow for that piece of content.  After that
> we dance with notify*() methods of the Workflow and that seems to be
> the story for how content and workflow stays in sync.