PloneWorkflows
Category: Workflow
—
Other products by this author
Current release
No stable release available yet.
Experimental releases
Upcoming and alpha/beta/candidate releases
- Alpha releases should only be used for testing and development.
- Beta releases and Release Candidates are normally released for production testing, but should not be used on mission-critical sites.
- Always install on a separate test server first, and make sure you have proper backups before installing.
Release roadmap for PloneWorkflows…
Project Description
- Project resources
The idea is to provide not one but several built-in workflows for Plone, to respond to 80% of common Use Cases and also to show there is a powerful wf engine in Plone, not just an hardcoded wf like many CMS around.
Modifing workflows is difficult for many site managers, so we will give them some easy choice.
Available workflows
- One state workflow
- Immeditate publication, a dumb workflow for non-workflowed content and very small sites. The one state workflow is useful when you do not want workflow at all in your Plone, and you just want your contents to show up. The one state is also useful if you want only a particular kind of content (i.e. a forum post or a FAQ) to automatically show.
- Simple publication workflow
- Simple publication is especially useful for small portals and small intranets (with some modifications), when no reviewer is necessary; it is a one-step publication process.
- Intranet workflow
- In intranet workflow only members can access portal contents; an internal document can be also internally published when it is somehow
officialfor the organization or company. - Community workflow
- This is a refactored Plone Default workflow; the default Plone workflow is enough general for most portals and intranets; with simple customizations it can be adapted to address many use cases.