Overview

This add-on for Zope and Plone aims to provide user-friendly automatically generated documentation about workflow definitions.

Currently two Zope3-style views for Products.DCWorkflow.interfaces.IDCWorkflowDefinition are provided:

• @@wf-graph: Render an image representing the workflow's states and transitions as a graph.
• @@wf-doc: Render an HTML page describing the workflow. This includes the graph mentioned above.

Requirements

• Tested with Zope XYZ + Plone 3.2.2. However only Zope 2.x is needed (hopefuly).
• Graphviz [1]. More precisely: there must be an executable called dot in the system path and the user running Zope must have execute permission on it.
• Other requirements are pure Python packages registered on PyPI and distutils should handle them without problems.

Installation

This package is easy_install'able. Just make it available in your Zope Instance and don't forget to load its ZCMLs. If you don't have any idea of what I'm talking about please refer to Installing an Add-on Product [4].

Usage

Just use the provided views on an workflow definition. Examples (type these URLs in your browser):

• http://localhost:8080/manuaisrfb/portal_workflow/plone_workflow/@@wf-graph
• http://localhost:8080/manuaisrfb/portal_workflow/plone_workflow/@@wf-doc

You can pass the following parameters to @@wf-graph in the query string: hide_roles and hide_permissions. These are lists of things to hide in the output, separated by ".". Example:

• http://localhost:8080/manuaisrfb/portal_workflow/plone_workflow/@@wf-doc?hide_roles=Anonymous.Authenticated.Member&hide_permissions=Access+contents+information.List%20folder%20contents

To-do

• Render an HTML image map, so the user can click on a state or transition and see its description.
• Test and adapt for Windows.
• Make the location of the dot executable configurable.
• i18n.
• Write automatic tests.

History

Credits

• Author: Rafael Oliveira <rafaelbco@gmail.com>
• The idea of using Zope3-style views to render information about workflow definitions was inspired by Martin Aspeli's collective.wtf [2].

Contribute and report bugs

Help is welcome. Contact the author or file a ticket at the Issue tracker [3].

References