Skip to main content

rbco.wfdocumentator

Overview

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

Currently the following 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.

  • @@wf-doc-user-friendly: Same as @@wf-doc but hides some roles and permissions and the “acquire” column.

  • @@wf-validate: Validate the workflow according to a set of general rules.

Requirements

  • Tested with Plone 4.3.x. However only Zope 2 is required (hopefuly).

  • Graphviz. 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.

Usage

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

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:

There’s also the hide_acquire parameter, which hides the “acquired” column.

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.

  • Write automatic tests.

Credits

  • Author: Rafael Oliveira <rafaelbco@gmail.com>

  • The idea of using Zope3-style views to render information about workflow definitions and to do sanity check on workflows was inspired by Martin Aspeli’s collective.wtf.

Contribute and report bugs

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

Thanks

  • To lucmult, for reporting the bug #2 (the one fixed in 0.0.3).

History

1.0.0 (2015-08-27)

  • Plone 4.3.x compatibility.

  • Workflow validation (@@wf-validate view and correspondent function).

0.0.4 (2011-06-13)

  • Implemented i18n.

  • Added z3c.autoinclude.plugin entry point.

  • Now @@wf-doc uses main_template.

  • Added @@wf-doc-user-friendly.

0.0.3 (22-november-2009)

  • Corrected packaging error: README.txt was not included in the released tarball :-(.

0.0.2 (22-november-2009)

  • Added “acquired” column to @@wf-doc.

0.0.1 (03-june-2009)

  • First release.

Metadata

Release files for rbco.wfdocumentator 1.0.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for rbco.wfdocumentator 1.0.0
File Size Uploaded Provenance Actions
rbco.wfdocumentator-1.0.0.zip 19.5 kB Without provenance Details for rbco.wfdocumentator-1.0.0.zip

Release files / rbco.wfdocumentator-1.0.0.zip

Download URL rbco.wfdocumentator-1.0.0.zip
Size 19.5 kB
Tags Source
SHA-256 checksum
How to use checksums
4a487c4f3c9ccfce0e2cfac4a31d408697060025221162827cbd369cf4373cdd
BLAKE2b-256 checksum
How to use checksums
432fafd70cc04863c3dde0b0a585f202955c29accdd3f7e787928ec7edceb0c7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for rbco.wfdocumentator 1.0.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page