Fago,
I've reviewed some more the workflow module. bottom line is that I don't think it's good enough - the fact that every content type can have only a single workflow was the last straw for me... however I'd like to list several features I found good by order of importance (IMO):

1. There is a workflow tab allowing to change state and you can define access to the tab per role/ author.
2. You can define which role/ author can change the state to which state (snap1).
3. You can add a comment and schedule the state change (snap2).
4. There is a workflow_access module based on the workflow state.

CommentFileSizeAuthor
Snap2.png20.48 KBamitaibu
Snap1.png7.17 KBamitaibu

Comments

amitaibu’s picture

amitaibu
Primary language Hebrew
Location Israel
commented

or, Maybe as you said we simply need to think about some CCK solution.

fago’s picture

fago
Primary language German
Location Vienna
commented

thanks for your review :)

I think CCK is the way to go. People can build already most of it with CCK - for comment integration there is comment CCK. Scheduling is possible with the rules scheduler module and content access / acl integration should cover node access.

What's missing, is the possibility to specify available transitions per role. Which would be no problem to do with a CCK field I think. Furthermore the workflow-ng-logging module needs to be ported, of course.

What's missing when looking at the 5.x states, is tracking user states. However I think this was seldom used anyway, so probably we can deprecate states in favour of good CCK conditions/actions.

amitaibu’s picture

amitaibu
Primary language Hebrew
Location Israel
commented
Status: Active » Fixed

agreed

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

mitchell’s picture

mitchell commented
Component: Miscellaneous » Provided Module Integrations

Updated component.