Add ability to schedule a State change at node creation (not only when editing existing nodes)

You already have the role able to move something from creation to draft. Did you set the role to be able to move something from creation to published. I would think that would allow you to schedule the publish state change the first time you create the node. Of course then it might be sitting in limbo somewhere as it would only be in 'creation' stage, not 'draft' nor 'published'.

Any progress on this? I'd also like to be able to schedule a workflow transition during node creation, cutting out the extra step.

subscribing

Hello tanoshimi, mglover , and janusman:

I've illustrated a sort of programmatic semi work around in this blog post:

http://treehouseagency.com/blog/sean-buscay/2008/10/24/building-publishi...

I hope it might help. If you have any specific questions I might try to answer, feel free to ask.

Best Regards,
Sean Buscay

Brilliant work and well documented.

Hats off to you!

Hello all

i am also facing same problem in work flow
i have create publishing work flow with state as draft,review,rework,unpublished and published and created a n action for that my question is if i change the state from unpublished to publish state why the content remains in not published state weather i am doing wrong thing or should we click on publish in publishing option inorder to publish the content please any one could suggest an idea how to do automating publishing and un publishing of content using work flow

Hi,

With the release of Drupal 7, Drupal 5 is no longer receiving security updates, reviews, or development from many contributed modules. Since 5 is now considered a depreciated version, you really should seriously look into upgrading to Drupal 6 or 7. The newer versions of Drupal work better, have more support, and will be safer (literally! security patches!) for your website. We are currently working on a new release for Workflow to Drupal 7. In light of that, further support for Drupal 5 issues is infeasible at the moment. Please consider upgrading to Drupal 6 or 7 in the near future - you'll be glad you did.

- Bastlynn

Scheduling a workflow transition at the point of node creation would be very handy in D7 version too.

It is deliberately hardcoded to not allow scheduling upon node creation. See this comment in the code:

function workflow_node_form(..) {
  ...
  // Display scheduling form only if a node is being edited and user has
  // permission. State change cannot be scheduled at node creation because
  // that leaves the node in the (creation) state.
  ..
}

We need to have an answer to the following question, first:
"If the scheduled state is set on the Node Creation page, what state will the new node have directly after saving?"
#7 has a workaround.

See #737738: Add ability to schedule a State change at node creation (not only when editing existing nodes) (II) for a proposal and a patch.

Personally, I would rather not have workflow on the node edit form at all.

Crossposting: below issues both regard the situation "change immediate state, while having a scheduled transition":
#2097401: Multi review
#189572: Add ability to schedule a State change at node creation (not only when editing existing nodes)

I've added this to a meta issue:
#2144747: [META] Flexible transitions

Marked #737738: Add ability to schedule a State change at node creation (not only when editing existing nodes) (II) as duplicate. Since it contains a patch, I repeat it here:

Posted by Josh Waihi on March 10, 2010 at 1:45am
Currently there are two ways to make a transition; immediately or at a given date and time. However there is a need to be able to make a transition both immediately and another transition at a later date and time.

For example, lets say we're using workflow for task assignment priorities. We may want to lower the priority for now but push the priority at a later time. Rather than having to do this in two steps we should be able to do this in one.

I've attached a solution I'm using at the moment. Though it could do with some UI improvments (so could the existing implementation for that matter!) Mayebe this should be a configuration to turn on?

In general, if you have only 2 states, I wouldn't use Workflow, but Scheduler.

This would be useful if some of the content needs to follow workflow, but some should be published scheduled without workflow. Currently the content has to be saved before it can be scheduled for publication for example.

ITMT, in version 8.x, some features have been added.
- hooks in workflow.api.php
- events directory src/Event, including some example code.