workflow

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.

So I have a CCK form for a "problem submission" form. The authenticated user pulls up the form, fills out the fields displayed (field permissions hides fields that the office fills out) and hits submit. Then the office can go in and make changes, add information and update the "progress" (workflow) of the problem. Anytime the status changes ('submitted', in progress', 'oh hold', 'completed' etc.) I have the Actions module send an email to the author. Everything is working fine, but I would like to extend it in one way, and this is what I need help with:

Hi group....I've run out of ideas to search for, so I'm hoping any of you might be able to help.

I have set up a workflow for a CCK node type with only two states: "Requested" and "Read". Workflow NG provides email notifications beautifully. I am trying to hide one of the CCK fields in the node creation step using the Workflow_fields module.

I have set up the permissions on the Workflow_fields module to show the field in question only during the "Read" state, but not on the "Requested" state.

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?

--

We've recently redesigned our website, so I took the time to do a small writeup and look back on our switch to Drupal a while ago. Hope you enjoy the read.

Making the transit from Textpattern to Drupal

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?

I don't seem to be able to schedule more than one change of state in a workflow for a node -- or at least, as there's no list of thee change I've scheduled, I have no way of knowing if adding a second scheduled change works or overrides the first one.
Is this possible?

What I'm trying to do is create a news story list on the front page of my site using a node queue. I have three states in my workflow: Pending, Current, and Expired. When in the Current state, the node is in the queue and removed when it goes to Expired.

I've been using Drupal for a few months now, but have only recently tested the workflow module on one of my sites (for submitting creative writing). I started with workflow-ng, and loved the functionality, but prefer the simplicity of the linear workflow in the "workflow" module.

I have two states in my workflow: Submitted and Published.

I want to restrict anonymous user to submitting to the Submitted state. (done.)

I want logged-in users to automatically post to the Published state. (almost there)

In the creation section of the workflow grid, I've set:
- Submitted: Author, anonymous user
- Published: authenticated user, Content Admin, Site Admin

There is no overlap between user roles in that workflow setup. However, when an authenticated user creates some new content, he is given the choice of Submitted or Published.

I don't even have to get rid of the "Submitted" option, if I can set the "Published" option to be selected by default for authenticated users.

any tips?

thanks in advance!