We are in the process of implementing Plone CMS as a repository for ISO9001 documents.
ISO requires a certain amount of logging, as anyone familiar with the standard probably knows :-)
For flexibility, we would like to include in a specific order:
- New types of content: you must include various documents that may arise in the enterprise
- Versions: to show that our documents are always updated and show what changes were made to a previous version of the same document.
- Support for a working copy: so that the βpublishedβ document is online while it is being edited.
- More complex workflow: to accommodate ISO review processes
- Different workflows for different documents: because the workflow depends on the type of document.
Therefore, the holy grail of workflow optimization should be (and please correct me if I am wrong):
- Dexterity for Content Types
- CMFEdition (built into Plone) for version control
- Iteration to support working copy.
- plone.app.workflowmanager for new workflows
- .CMFPlacefulWorkflow products for different workflows according to different documents.
The problem is combining various works:
- How can you manage versions with Dexterity?
- How do you add working copies on top of this (while maintaining the necessary version control)?
- And how do you get your brilliant new workflow (great btw UI for workflowmanager) to play well with versions and work copies.
I looked at the google area and already found these links:
We also checked:
which are all installed and configured ...
However, my new content type does not allow checkout / checkin (Iterate product), and none of these versions / changes are tracked in the historical view for the same content type.
Is their magic sequence, or am I missing something (or, more likely)? Because, if all these products worked out of the box, in my opinion, this is a comprehensive solution for the whole process of work ...
expansion 2012/04/17: As noted by thet, the stack ends as with
workflow plone dexterity
Speediro
source share