Hi all Andr� wrote:
>Life cycle: create/publish/archive/delete dates Apart from simple websites this workflow is common. But again, I've been working in projects were most of them this workflow would not work (Governement Institutions, Pharmaceuticals, New Media). It just misses a lot of information. Andr� wrote: >Authoring: custom content creation forms etc. This is not a workflow. These are content capture facilities that have little to do with management. Andr� wrote: >Approval: Chain document approval like departments or up hierarchies etc This should be part of the live cycle of content. Why? Because people approve or reject things due to something, which encompasses the content being worked and have an effect on it. >QA: dev/staging/production transitions There is no such thing as a QA workflow. At least I've never came across to it. Furthermore this is a Workflow commonly used on software development, hardly one useful when managing Minutes for example. As I've said QA is assuring that you do that you say you do, or can be viewed assuring compliance to requirements. As an example of a different workflow (I'm being creative here) consider the following. Traditional 1) Client sends a RFP to a vendor (Email?) 2) Vendor Created a Proposal 3) Vendor sends a Proposal to the client (Email?) 4) Client analyses the Proposal and Rejects (Reason), Approves or sends to the Vendor for reviewing (Reason). Now imagine that the Vendor as acquired a CMS for its Intranet were he want's to store and manage Proposal and RFP. If a CMS do not have a Workflow useful to manage RFP and Proposals it will be nothing more than a database. Small vendors usually store proposals inside a folder in the file system. Probably organized by Vendor, Product or Date (It may be ok). Now consider a Medium to Big Enterprise with 300+ consultants, clearly the same process (store on a folder in the file system) can be inefficient (a lot of information just vaporizes). A CMS with a flexible workflow engine could do cope with this example. Furthermore it could cope with simple workflows like "create/publish/archive/delete dates" often used to manage content of web sites. If one is adopting a CMS for an Intranet I can imagine that this flexibility is desired (I've already posted something about this). Best regards, Nuno Lopes Independent Consultant. -- http://cms-list.org/ trim your replies for good karma.
