We want to overcome the restriction that requires us to use only one workflow per content type.

We don’t want to use a content type approach as in the workflow module.

We intend to use Revisioning, TAC Lite, and Module Grants modules, but have not investigated these fully.

We’re aiming to provide our content publishing users with more states (such as needs pending publish, pending approval, share view, draft, ), with multiple approvers as defined by user groups, and with triggers such as sending an email to a user group based on a state change such as “for approval”.

1. Will these modules enable us to achieve these goals?
2. What other options should we consider?
3. Has anyone implemented something similar?
4. What approach should be taken, and how should it be set up?
5. What should we watch out for when attempting this?

I see that you are no longer active with the workflow module, but I’ll post here in hopes that other interested parties wind up here. I have an intranet site where I’ve created a Category taxonomy. Every new node is classified to a category (which amounts to a content hierarchy). For purposes of routing new nodes (or edited nodes) to the appropriate content-area owner for review, I was thinking it would be useful if I could assign a username to each category. Then, when content is added/updated, the node would be routed to the correct person for review.

If anyone has any suggestions on how to accomplish this, I appreciate your feedback.

Thanks,
Todd

Thanks for writing. At present I am gainfully employed with Acquia and am working on Apache Solr stuff.

http://pajamadesign.com/category/solr/

Don’t really have anytime to work on my workflow contribs. If you would like to pick them up, you are MORE than welcome. There are a lot of people who used this and liked it, and I’ve gotten many requests to get it using Rules, etc.

Best,
Jacob

It seems that the Rules Module (much better name!) is no longer integrated with workflow module and your workflow owner module is not ready for 6 yet either.

So I guess my question is:

1. Is there a plan to port these?
2. If not then do you have any suggestions for D6.

Once again thanks for your contributions!

Craig Bertrand
Gateway Services Asia

It looks like we will be rolling out with Drupal 5 anyway since CCK, Views, et al. are still in progress toward Drupal 6 compatibility. I’m going to start playing around with the Workflow-related parts of the project today and see what I can do.

Regards,
Devin

Thanks for coming and commenting. It’s nice to see people interested in this! I’m sorry it’s not a more exciting tutorial at present, but yeah the technology is great and usable.

There are plans to port this to Drupal 6, but unless you are starting your project in 4-5 months, I wouldn’t gamble on it (I personally wouldn’t start any large project on D6 for another 6 months).

The D6 version has a better name (which I suggested to Fago )

It’s called Rules .

It will be even better and will support D6 actions. I think there will be a clean upgrade, so you could consider starting in D5, but don’t take my word for it…

Let me know if you have any more questions or would like some help setting up your workflow/workflow-ng config.

All the best,
Jacob