Workflow

A common requirement is to execute actions based on passage of time. Can I have some input on how you slick Drupal people out there have attacked this issue?

An example. Let's say you have the stereotypical workflow of create -> approve -> publish. If the approver doesn't approve or disapprove within 1 week of node creation, an email reminder is to be sent to the approver.

What's the most elegant way to trigger the email?

Hi,

Im creating a site using Drupal 6.2.
I need to integrate the workflow module with this.

the funtionalities i need are

1. users will submit cases (page with details along with attachments (video, pdf, doc etc))
2. this will go to the reviewer, who reviews this,
   if rejected to notify the submitter with reasons
3. If accepted, it should go to approvers, after accepting the case gets submitted.

Do we any inbuilt module in Drupal to do this functions (like workflow in Drupal 5) in Drupal 6 or is there any other way of doing this in Drupal 6.2

Thanks
Sumesh

I posted this over the the support area of workflow, but I also wanted to post this over here too.

http://drupal.org/node/257258

I don't know if I am missing something or what, but when had version 5x-1.x installed, the actions to publish and unpublish nodes as well as a group of others were listed as actions in the actions area of workflow. I wanted to automatically publish/unpublish nodes when it changed workflow states. Everything is there, and works correctly. But on 5.x-2 they are not an option.

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.

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!

In my website i have 2 flow flow already, when i create a new work flow and sign the node type into the new work flow, all the old content page of this type show errors in the work flow part. It seems like that the old content still link to the old work flow and the new work flow can only work well in the new content. I don't want to delete all the related content in work flow transfer and create the new ones, does any one could help me?

Hey guys,

So I need to extend workflow slightly, I've got to create a field which will give the estimated amount of time that a content type should stay in a particular state. Is the best way to do this to patch workflow or create another module?

--

Hello everyone,

The system we currently use at our office is currently built upon the casetracker module. However, the challenge we are encountering is enforcing a "workflow" on those nodes in our system. It would be great to be able to integrate casetracker with workflow so that changes are detected and that changes to the those fields are acted upon and processed.

Putting it here, for people to comments and review.

> Hi,
> Please review this tutorial, I hope it's better, implementation-wise, then
> last one :)
> http://drupal.org/node/203377

Yep, that sounds like a cool use case.

I'd suggest that we write the tutorial, so that the nodes always keep
visible for everyone. For that we need content access and set it to
allow anonymous + authenticated users to allow view access.

-> Probably you have that already, but I can't find your figure 1?