workflow-ng

I just today started looking at the Rules Module. The description looks like it fits the bill but not being a programmer type I want to make sure I am on the right track.

I have workflow, workflow access, and workflow fields set to do the workflow transitions I would like on a per content type basis.

The Rules Module description states, "The rules modules allows site administrators to define conditionally executed actions based on occurring events (ECA-rules). It's a replacement with more features for the trigger module in core and the successor of the workflow-ng module." On first glance I wasn't sure, but...

I must confess I am totally confused by workflow. I'm still working in D5 (waiting for modules to be upgrade to D6 so I can upgrade), and would like to set some simple workflows in place. Two examples:

I've added a new event to a module that I'm working on, but I would like to also be able to return a string. Is there a entity type that would allow me to do this. Ideally I would like to pass a string as an argument to the workflow_ng_invoke_event function and access the string's value as a token.

If this doesn't exists, any pointers on how I might write the code to do this.

We have finally gone live with our redesign of the Georgia Podcast Network! For a rundown of what's new from an end user standpoint, check out our announcement blog post.

GAPN is based on Drupal 5.7, and makes heavy use of the following modules: CCK, Views, Workflow-ng, FeedAPI, ImageCache, Usernode, Bio, Fivestar, and Voting API. That's not a full list, but the site leans on those the most.

Additionally, we built a custom theme and wrote several custom modules to get things working just the way we wanted them to. In writing these modules, we built custom Drupal integration for getID3, SWFUpload, and the JW Media Player.

Hope you like the site! I'll be happy to answer any "how did you do that?" questions if you have them.

Hi I have installed workflow-ng on drupal 5.7 and I can't figure out how to allow users to change a state. I have created a state machine with 2 states and connected them with a specific content type. when I either edit or view that content type I cant see any way to change the state of the content? I have read the documentation but it doesnt talk about the state machine.

Once I get the state machine working I will fire an email if the state is changed to a certain "finished" state so that I can then view the node.

Any help would be greatly appreciated.

Hi folks

I'm a newbie to this module and need a little help please :)

After a fresh install of Drupal 5.7, I added and enabled the latest Token and Workflow-ng modules only. The token substitutions fail right "out of the box". For example, if I activate the sample rule called Print the content title of pages and stories and at the top of nodes, it prints:

Workflow-ng example: The title of this post is [node:title].

If I create ANY rules with token replacement, they aren't replaced. I've tried:

<

ul>

I have a nodeprofile field type that can be for example "group 1", "group 2", or "group 3".
Every time a new user registers, I want different emails to be sent to different users based on this type field.
I add a new rule configuration and I choose the "User has registered" event.
The problem is that when I try to add a condition, the only relative thing I can choose from there is
"User has nodeprofile". How can I access my type nodeprofile field???
I have tried the "Textual comparison" too but I had no luck.
What should I do?
Help! I really need to finish this!

I'm trying to use Workflow-ng to set up the following scenario:

A node can have one of three states:

1. Draft
2. Needs Review
3. Published

There are two types of authenticated users:

1. Editor
2. Publisher

The Editor role can create nodes and also edit nodes. The Editor can change the state of a node from Draft to Needs Review but cannot set it to Published. The Editor can no longer edit the node once it has been set to the Needs Review state.

The Publisher role can create, edit and set the node state to published. Once the node is set to Published the Editor role can no longer edit the node. The Publisher can also set the node state back to Needs Review or Draft.

I'm happy to announce that I start working on the next generation workflow module, called workflow-ng.
It's inspired by the existing workflow module, but if things go well it's going to be a lot more powerful.

I can use the development as practical work for my study and I will also write my bachelor thesis about this - thanks to the Information & Software Engineering Group of the TU vienna. Furthermore it's great that this all is sponsored by the Austrian company Pro.Karriere!

So, what's workflow-ng?

Workflow-ng ist the next generation module package for building workflows with Drupal. It allows building configurable state machines, which can be supplied programmatically or through the admin interface. So workflow-ng will be a tool for module developers as well as for site admins.
Workflow-ng doesn't work only for content nodes, it will be coded on top of a “drupal entity” - so it will start with support for nodes, comments and users. Furthermore it doesn't urge you to introduce new states for your entities,because it does interpret each saved entity as a new possible state. This allows one to reuse existing information, e.g. reuse the existing „published“ and „moderated“ fields of nodes.
Also workflow-ng won't allow one building state-machines only. One will also be able to react on various “events” with configurable actions, which allows site-admins or modules to adapt any default behaviour. E.g. this suits very well for e-mail notifications. Send a thank you message to the author of a certain node type? Just configure the action and workflow-ng will do it for you.

Read more about it in the concept I wrote: link