<br><div><span class="gmail_quote">On 3/23/06, <b class="gmail_sendername">Kurt Bendl</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hey Mike,<br><br>Could you share an example of one of your AGX-created<br>workflows with us? <br></blockquote></div><br>Sure. At the DCRI, most of the Web sites we are developing in Plone are for restricted communities, and as such, the normal Plone workflow doesn't work for us. We've created a workflow which includes, at its core, another state called public for content that should be available anonymously. Published content is only available to members. We also get rid of public draft as we feel this causes unnecessary confusion to our users.
<br><br>The product also adds another role for users we call content managers who should have manager access to the Plone, but not to the Zope/ZMI.<br><br>The product can be found at <a href="https://plone.dcri.duke.edu/files/dcriworkflows/">
https://plone.dcri.duke.edu/files/dcriworkflows/</a>. I apologize, but in the server transition that occurred last week it appears that the proxy rules aren't correct so you can't actually browse any content that's available outside that folder without knowing the URLs. I'll try to get it fixed tomorrow.
<br><br>Using ArchGenXML to generate workflows is fairly painless once you figure things out. I'd be happy to do a demo (perhaps at a slower pace than last time) at a future meeting.<br><br>Mike<br>