Welcome, guest | Sign In | My Account | Store | Cart

Notice! PyPM is being replaced with the ActiveState Platform, which enhances PyPM’s build and deploy capabilities. Create your free Platform account to download ActivePython or customize Python with the packages you require and get automatic updates.

Download
ActivePython
INSTALL>
pypm install products.dcworkflow

How to install Products.DCWorkflow

  1. Download and install ActivePython
  2. Open Command Prompt
  3. Type pypm install products.dcworkflow
 Python 2.7Python 3.2Python 3.3
Windows (32-bit)
2.3.0-beta Available View build log
2.2.4 Available View build log
2.2.3 Available View build log
2.2.2 Available View build log
2.2.1 Available View build log
Windows (64-bit)
2.3.0-beta Available View build log
2.2.4 Available View build log
2.2.3 Available View build log
2.2.2 Available View build log
2.2.1 Available View build log
Mac OS X (10.5+)
2.3.0-beta Available View build log
2.2.4 Available View build log
2.2.3 Available View build log
2.2.2 Available View build log
2.2.1 Available View build log
Linux (32-bit)
2.3.0-beta Available View build log
2.2.4 Available View build log
2.2.3 Available View build log
2.2.2 Available View build log
2.2.1 Available View build log
Linux (64-bit)
2.3.0-beta Available View build log
2.2.4 Available View build log
2.2.3 Available View build log
2.2.2 Available View build log
2.2.1 Available View build log
 
License
ZPL 2.1 (http://www.zope.org/Resources/License/ZPL
Lastest release
version 2.3.0-beta on May 23rd, 2012

This product provides fully customizable workflows for the CMF portal_workflow tool.

Usage

To see an example, after installing DCWorkflow, using the "Contents" tab of your portal_workflow instance add a "CMF default workflow (rev 2)" instance.

Developing a workflow

This tool is easiest to use if you draw a state diagram first. Your diagram should have:

  • States (bubbles)
  • Transitions (arrows)
  • Variables (both in states and transitions)

Remember to consider all the states your content can be in. Consider the actions users will perform to make the transitions between states. And consider not only who will be allowed to perform what functions, but also who will be required to perform certain functions.

On the "States" tab, add a state with a simple ID for each state on your diagram. On the "Transitions" tab, add a transition with a simple ID for each group of arrows that point to the same state and have similar characteristics. Then for each state choose which transitions are allowed to leave that state.

Variables are useful for keeping track of things that aren't very well represented as separate states, such as counters or information about the action that was last performed. You can create variables that get stored alongside the workflow state and you can make those variables available in catalog searches. Some variables, such as the review history, should not be stored at all. Those variables are accessible through the getInfoFor() interface.

Worklists are a way to make people aware of tasks they are required to perform. Worklists are implemented as a catalog query that puts actions in the actions box when there is some task the user needs to perform. Most of the time you just need to enter a state ID, a role name, and the information to put in the actions box.

You can manage all of the actions a user can perform on an object by setting up permissions to be managed by the workflow. Using the "Permissions" tab, select which permissions should be state-dependent. Then in each state, using the "permissions" tab, set up the role to permission mappings appropriate for that state.

Finally, you can extend the workflow with scripts. Scripts can be External Methods, Python Scripts, DTML methods, or any other callable Zope object. They are accessible by name in expressions. Scripts are invoked with a state_change object as the first argument; see expressions.stx.

Once you've crafted your workflow, you hook it up with a content type by using the portal_workflow top-level "Workflows" tab. Specify the workflow name in the target content type's box.


Products.DCWorkflow Changelog

2.3.0-beta (2012-03-21)
  • Removed string exceptions.

System Message: WARNING/2 (<string>, line 77)

Bullet list ends without a blank line; unexpected unindent.

(https://bugs.launchpad.net/zope-cmf/+bug/952301)

  • Made sure converted tools are used as utilities.
  • Don't crash worklist's manage_main if variables are Expression objects.

System Message: WARNING/2 (<string>, line 82)

Bullet list ends without a blank line; unexpected unindent.

(https://bugs.launchpad.net/zope-cmf/+bug/731394)

  • Allow renaming of states, transitions, variables and worklists
  • Require at least Zope 2.13.4.
  • StateChangeInfo: Removed support for deprecated '_isPortalRoot' marker.
  • Hardened XML import parsing against missing boolean attributes.

System Message: WARNING/2 (<string>, line 91)

Bullet list ends without a blank line; unexpected unindent.

(https://bugs.launchpad.net/zope-cmf/+bug/707927)

  • Ensured that emitted XML export has a valid encoding, even when passed

System Message: WARNING/2 (<string>, line 94)

Bullet list ends without a blank line; unexpected unindent.

'None'. (https://bugs.launchpad.net/zope-cmf/+bug/707927)

  • Fixed Chameleon compatibility in 'state_groups.pt'.
  • Workflow states cannot be renamed through the ZMI.

System Message: WARNING/2 (<string>, line 99)

Bullet list ends without a blank line; unexpected unindent.

(https://bugs.launchpad.net/zope-cmf/+bug/625722)

  • Deal with deprecation warnings for Zope 2.13.
  • Change default encoding of exports from None to utf-8.
2.2.0-beta (2009-12-06)
  • no changes from version 2.2.0-alpha
2.2.0-alpha (2009-11-13)
  • moved the Zope dependency to version 2.12.0b3dev
  • Worklists: The catalog variable match setting can now be a

System Message: WARNING/2 (<string>, line 118)

Bullet list ends without a blank line; unexpected unindent.

formatted string (as before), but also a qualified TAL expression, meaning it has a prefix like "string:", "python:". (https://bugs.launchpad.net/zope-cmf/+bug/378292)

  • exportimport: Support for instance creation guards and manager

System Message: WARNING/2 (<string>, line 123)

Bullet list ends without a blank line; unexpected unindent.

bypass added. (https://bugs.launchpad.net/zope-cmf/+bug/308947)

  • Cleaned up / normalized imports:

o Don't import from Globals; instead, use real locations.

o Make other imports use the actual source module, rather than an intermediate (e.g., prefer importing 'ClassSecurityInfo' from 'AccessControl.SecurityInfo' rather than from 'AccessControl').

o Avoid relative imports, which will break in later versions of Python.

  • Strip trailing newlines in order to properly match with a msgid when

System Message: WARNING/2 (<string>, line 137)

Bullet list ends without a blank line; unexpected unindent.

translating transition descriptions.

  • Workflow UI: Remove ancient cruft to accommodate the proprietary

System Message: WARNING/2 (<string>, line 140)

Bullet list ends without a blank line; unexpected unindent.

(and long dead) base_cms product.

  • Worklists and Transitions: Add icon expression properties to worklist

System Message: WARNING/2 (<string>, line 143)

Bullet list ends without a blank line; unexpected unindent.

and transition actions and their GenericSetup profiles.

  • Fixed an import error (Products.PageTemplates.TALES is gone on

System Message: WARNING/2 (<string>, line 146)

Bullet list ends without a blank line; unexpected unindent.

Zope trunk). Because we require Zope >= 2.10, we don't need a BBB conditional import.

2.1.2 (2008-09-13)
  • test fixture: Fix failng tests with GenericSetup > 1.3 by explicitly

System Message: WARNING/2 (<string>, line 154)

Bullet list ends without a blank line; unexpected unindent.

loading GS' meta.zcml during setup.

2.1.2-beta (2008-08-26)
  • completed devolution from monolithic CMF package into its component

System Message: WARNING/2 (<string>, line 161)

Bullet list ends without a blank line; unexpected unindent.

products that are distributed as eggs from PyPI.

2.1.1 (2008-01-06)
  • no changes
2.1.1-beta(2007-12/29)
  • Testing: Derive test layers from ZopeLite layer if available.
  • exportimport: Scripts with invalid types imported

System Message: WARNING/2 (<string>, line 176)

Bullet list ends without a blank line; unexpected unindent.

after scripts with valid types will no longer place the valid script twice. Scripts can also now be specified with meta_types other than the hard-coded meta_types.

  • AfterTransitionEvent now passes along the new status of the

System Message: WARNING/2 (<string>, line 181)

Bullet list ends without a blank line; unexpected unindent.

object, just as StateChangeInfo passes on the new status to after-transition scripts. (http://www.zope.org/Collectors/CMF/490)

2.1.0 (2007-08-08)
  • Fixed all componentregistry.xml files to use plain object paths and strip

System Message: WARNING/2 (<string>, line 190)

Bullet list ends without a blank line; unexpected unindent.

and slashes. GenericSetup does only support registering objects which are in the site root.

2.1.0-beta2 (2007-07-12)
  • moved the Zope dependency to version 2.10.4
  • Remove antique usage of marker attributes in favor of interfaces,

System Message: WARNING/2 (<string>, line 200)

Bullet list ends without a blank line; unexpected unindent.

leaving BBB behind for places potentially affecting third-party code. (http://www.zope.org/Collectors/CMF/440)

  • Add POST-only protections to security critical methods.

System Message: WARNING/2 (<string>, line 204)

Bullet list ends without a blank line; unexpected unindent.

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-0240)

  • Workflow definition instances now have a description field

System Message: WARNING/2 (<string>, line 207)

Bullet list ends without a blank line; unexpected unindent.

(http://www.zope.org/Collectors/CMF/480)

2.1.0-beta (2007-03-09)
  • moved the Zope dependency to verson 2.10.2
  • Tool lookup and registration is now done "the Zope 3 way" as utilities, see

System Message: WARNING/2 (<string>, line 216)

Bullet list ends without a blank line; unexpected unindent.

http://svn.zope.org/CMF/branches/2.1/docs/ToolsAreUtilities.stx?view=auto

  • Merged patches from Martin Aspeli to enable generating events before

System Message: WARNING/2 (<string>, line 219)

Bullet list ends without a blank line; unexpected unindent.

and after DCWorkflow transitions, and in the 'notify' methods of the workflow tool (http://www.zope.org/Collectors/CMF/461).

2.1.0-alpha2 (2006-11-23)
  • moved the Zope dependency to version 2.10.1
  • Fixed test breakage induced by use of Z3 pagetemplates in Zope 2.10+.
  • browser views: Added some zope.formlib based forms.
  • testing: Added test layers for setting up ZCML.
2.1.0-alpha (2006-10-09)
  • skins: Changed encoding of translated portal_status_messages.

System Message: WARNING/2 (<string>, line 239)

Bullet list ends without a blank line; unexpected unindent.

Now getBrowserCharset is used to play nice with Five forms. Customized setRedirect and getMainGlobals scripts have to be updated.

  • Profiles: All profiles are now registered by ZCML.
  • ZClasses: Removed unmaintained support for ZClasses.

System Message: WARNING/2 (<string>, line 245)

Bullet list ends without a blank line; unexpected unindent.

Marked the 'initializeBases*' methods as deprecated.

  • Content: Added IFactory utilities for all content classes.

System Message: WARNING/2 (<string>, line 248)

Bullet list ends without a blank line; unexpected unindent.

They are now used by default instead of the old constructor methods.

  • Content: All content classes are now registered by ZCML.

System Message: WARNING/2 (<string>, line 251)

Bullet list ends without a blank line; unexpected unindent.

ContentInit is still used to register oldstyle constructors.

  • setup handlers: Removed support for CMF 1.5 CMFSetup profiles.
Earlier releases

For a complete list of changes before version 2.1.0-alpha, see the HISTORY.txt file on the CMF-2.1 branch: http://svn.zope.org/CMF/branches/2.1/HISTORY.txt?view=auto


Download

Subscribe to package updates

Last updated May 23rd, 2012

Download Stats

Last month:6

What does the lock icon mean?

Builds marked with a lock icon are only available via PyPM to users with a current ActivePython Business Edition subscription.

Need custom builds or support?

ActivePython Enterprise Edition guarantees priority access to technical support, indemnification, expert consulting and quality-assured language builds.

Plan on re-distributing ActivePython?

Get re-distribution rights and eliminate legal risks with ActivePython OEM Edition.