Should be able to schedule an action trigger, like moving to the next workflow state (which could publish, email that's it's been published, etc.). Would be very powerful then, especially since there are actions for publish and promote and all that fun. That would kill several birds with one big stone, I think.

Comments

m3avrck’s picture

m3avrck commented

Certainly a worthwhile idea, if anyone has any patches for this I don't mind commiting it but no time to work on it right now :-)

AjK’s picture

AjK commented
Version: 4.7.x-1.x-dev » master
Assigned: Unassigned » AjK
Status: Active » Postponed

Add to TODO.txt

Making this issue "postponed" as I wish to concentrate on Drupal5 compat and any ensuing bugs. Once stable, I will return to these issues as outlined in the projects TODO.txt file

AjK’s picture

AjK commented

codepoet, it seems to me that the actions module (if installed) provides the site admin with various actions. Is the suggestion that, for example, a site admin could select "for the story node type trigger send email action and publish action" (ie two actions in this example)?

Just want to get this clear in my head. Currently, scheduler provides basically two fields (and a time zone, lets for get that for now) being "publish on" and "unpublish on". In order to trigger actions as suggested, this would do away with two fixed fields and be replaced with "select a time to perform a specified action(s)" and allow for one or more time/action settings per node or per node type.

Am I understanding this right?

Would one want to allow site users (rather than site admins) to select an action type for their node? That seems possibly to liberal or would it be prefered that the site admin could allow a limited action set (say based on user role) on a per node basis?

There's a number of ways this could be done, just looking for feedback really.

regards,
--AjK

codepoet’s picture

codepoet commented

My idea was that I could setup a queue of scheduled actions on a node. Say:

* [node 1] [publish = 1] [12:00pm]
* [node 1] [frontpage = 1] [12:00pm]
* [node 1] [emailstatus = foo@foo.foo] [12:00pm]

Or also use the actions in the workflow module to trigger a move to the next workflow state (which is really what I was after to begin with). But I was thinking of many scheduled actions and times per node rather than one scheduled time with many actions.

AjK’s picture

AjK commented

Seems the best way is to allow for multiple scheduled times per node to trigger workflow transition changes (which in turn, if setup in workflow can trigger multiple actions) ?

AjK’s picture

AjK commented
Status: Postponed » Closed (duplicate)

Decided to mark this as duplicate of http://drupal.org/node/53008 as this functionality will be built as part of that feature request.

--AjK