You are not logged in Log in Join
You are here: Home » Members » ajung » PloneCollectorNG » wiki » WorkflowSupport » wikipage_view
Log in
Name

Password

 
Link icon Forgot your password?
 
Print

WorkflowSupport

Every issue is controlled by an issue workflow. In CMFCollector and CMFCollectorNG there was one workflow for all Collector instances. With PloneCollectorNG every Collector instance can have its own workflow. The particular workflow can be choosen at creation time of a collector instance as part of the collector metadata. PloneCollectorNG 1.2+ ships with two different workflows:

  • DefaultWorkflow (image)

    States

    • created -- initial state
    • pending -- state after submitting a new issues
    • resolved -- issue has been resolved
    • accepted -- issue accepted and assigned
    • defered -- issue effort defered
    • rejected -- issue has been rejected
    • resigned -- issue can not or will not be resolved
    • wontfix -- issue will not be fixed
  • SimpleWorkflow

    Same as the DefaultWorkflow? but without defered and resigned states

WARNING: The workflow should only be changed as long as there are no issues within the PloneCollectorNG instance. You must re-create the workflow and catalog tool through the corresponding option under Configuration -> Maintenance.
Copyright (c) 2011 Zope Foundation. All rights reserved. Legal | Contact
If you can read this text, it means you are not experiencing the Plone design at its best. Plone makes heavy use of CSS, which means it is accessible to any internet browser, but the design needs a standards-compliant browser to look like we intended it. Just so you know ;)