Loading...
 
Features / Usability

Features / Usability


FEATURE REQUEST: we need a status for tw objects

posts: 112 Austria

hi tw gurus & friends,

a few days before i posted a story about necessary changes in the field of object status. Sadly, no response. But I am dogged wink

New attempt:
1. i think we need a status flag per object (or object type)

2. this status flag can be have a predefined set of values. For instance:
- pending
- wait for approve
- active
- locked
- ...
The status describe the current working "editing status". The "workflow status" must be another flag.

3. tw has functions to change the status. This are the buttons and it can be:
- lock
- sign, control, reject
- check out/in
- ...
(I attached a file as a sample)

4. The workflow engine can use these status for routing the object depending on the current state (if no approve, reject automatically,...).

5. Not all tw objects need such an status. I think the following make sense:
- wiki pages
- html pages
- trackers
- directory links

Please think about. If we want compare tw with solutions such ZOPE we must fair enough not only compare the functions but the architecture too. And this is a archirecture topic.

I see a lot of functions today with a lot of high potential. And I want to help to see some things who can be clever.

Hope this is such a feature.

paulap

There are no comments at this time.

Upcoming Events

1)  18 Apr 2024 14:00 GMT-0000
Tiki Roundtable Meeting
2)  16 May 2024 14:00 GMT-0000
Tiki Roundtable Meeting
3)  20 Jun 2024 14:00 GMT-0000
Tiki Roundtable Meeting
4)  18 Jul 2024 14:00 GMT-0000
Tiki Roundtable Meeting
5)  15 Aug 2024 14:00 GMT-0000
Tiki Roundtable Meeting
6)  19 Sep 2024 14:00 GMT-0000
Tiki Roundtable Meeting
7) 
Tiki birthday
8)  17 Oct 2024 14:00 GMT-0000
Tiki Roundtable Meeting
9)  21 Nov 2024 14:00 GMT-0000
Tiki Roundtable Meeting
10)  19 Dec 2024 14:00 GMT-0000
Tiki Roundtable Meeting