Here is one explanation. Nice work. Robert (EXPERTS: Is the security setting update necessary at this point?) The permission settings of an object is only set to reflect the one defined for a state, when a state change occurs. Therefor a change to the permission settings for state will only have any impact on objects that enter that state hence on. Any objects that are in the altered states are untouched and reflect the old settings. With the button "security setting update" the permission settings of all objects participating in a work flow are updated to reflect the permission settings defined for the state they are in. Mitch Trachtenberg wrote:

In an attempt to solicit information about DCWorkflow from those in the know, while simultaneously being more useful than not, I've written and posted a preliminary step-by-step howto on creating a minimal custom workflow.

It's available at the url http://zope.org/Members/mitchtrachtenberg/workflowhowto/index_html

There are several spots in the document (flagged EXPERTS:) where I solicit information, and I'd be grateful for any responses to the questions posed. I'd be more than happy to incorporate (and credit, of course) additions and corrections.

Mitch Trachtenberg

_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )