Which kind of workflow engine would solve at least the 85% of your use cases

public
group: Rules
arhak - Mon, 2008-07-21 02:19
Single state workflow
40% (2 votes)
Multiple states workflow
60% (3 votes)
neither solves as much as 85% of my use cases
0% (0 votes)
Total votes: 5

Sorry, I don't understand

amitaibu's picture
amitaibu - Mon, 2008-07-21 07:40

Sorry, I don't understand the poll's question.


Sorry, I was thinking...

arhak - Mon, 2008-07-21 08:19

Sorry, I was thinking several thing at a time and I ended up writing nonsenses.
But I don't know how to edit the poll's question.

I would like to know if other developers can solve the must of their projects having a workflow in which object go from a single state to other single state, or if they need those objects to be in several states at a same time (kind of divergence to parallel workflows on the same object)

The poll should read:
- Single state workflow (each object remains in only one state at a time)
- Multiple states workflow (an object might be in several states at a time)

Can't I edit the poll?

multiple

fago@drupal.org's picture
fago@drupal.org - Mon, 2008-07-21 12:04

I've come over the need of multiple states several times. It happens that items play a role in different processes at the same time.


strange...

arhak - Tue, 2008-07-22 20:13

Do you really can't solve the 85% of your cases with simple state?
I did the question because, having a single state workflow I can solve perhaps up to a 90% or regular cases,
BUT then some other requirements comes up and then is a mess if I don't have the appropriate tool.
Do you thing that Rules module should handle multiple states?

I'm usually building complex

fago@drupal.org's picture
fago@drupal.org - Thu, 2008-07-31 09:12

I'm usually building complex things where I need multiple states.

@rules: Rules itself has no state. But e.g. you can use CCK fields for tracking states, or the workflow module or a port of the states module of worklfow-ng.