Loading...
 
Skip to main content

Features / Usability


we need a DRAFT status for almost each objecttype

posts: 112 Austria

Hi developers,

I know, you are working very hard and I want to say "Thank You" for the good job you do.

But I see a very important requirement for tikiwiki, to play in the next "liga" of CMS/Blog/Wiki systems:

  • each object (or the objecttype behind) need a status flag, to define the working and the workflow status of this object
  • the status should be defined be admins per objecttype, workflow, installation and to associate with system status (they are part of the installation)
  • depending on the status, the object can be changed, viewed,...
  • the workflow can test the status and depending on this, change the next activation or worker (role) in the worklist
  • the workflow can change the status automatically. That means, that the creator of a worklist can define the changing-process
  • depending of the status, there can be a archiving komponent (export and delete all objects with the status "to archive" and set the status "archived")


Please give feedback. I hope it works with the current implemented functions and only little adoptions.

If you think this opinion is useful I will extend the docs and try to working on a more detailed version.

paulap

There are no comments at this time.