I've seen workflow modules capability to perform user configurable actions, so, it avoids lots of "trivial"(maybe not) custom modules development. It includes sending out email notifications but they have no user interface, so take following scenario as example:

- Content type called: "News"
- "News" have a cck field: "Status" with 3 possible values: "Not reviewed yet", "Review in progress", "Reviewed".
- A workflow rule which notify to coordination@example.com when a "News" node status changes from NULL to "Not reviewed yet", to reviewer@examplecom when status changes to "Review in progress" and do thebigboss@example.com

Now imagine a team of privileged contributors, which would like to subscribe to "News" when they are "Not reviewed yet", and some others would like to subscribe when "News" have a "Review in progress" and finally, normal users got "News" when they are "Reviewed".

Then, if that "News" "Not reviewed yet" is updated but stays in that "Status", perhaps some users would like to receive it, the same when is commented.

Currently this is possible by iterating in the mail template, but could be a painful work to maintain it....

So, it requires two way integration: subscriptions <-|-> workflow/rules

My question is, does it is better to work in both modules? perhaps develop a new plug-in? both?

Blessings!

Comments

salvis’s picture

I don't know enough about workflow to provide an informed answer, but I think a plug-in to both sides would be the way to go. From the Subscriptions side these are the major tasks:

  • provide a page to list and activate/deactivate the subscriptions — that would be a Subscriptions page, the data would need to come from workflow and go into the {subscriptions} table
  • hook into the triggers provided by workflow to create entries in the {subscriptions_queue}
  • define a mail template and the necessary mailvars
  • get the actual information and fill it into mailvars
  • provide an end user interface (like the fieldset/block on nodes) on the subscribable items and/or within the workflow interface
develcuy’s picture

Status: Active » Postponed

Thank you @salvis, I appreciate your guidelines but have to leave this as a proposal by now, I'm overloaded of job...

Blessings!

jwarner’s picture

Subscribing

mudd’s picture

Subscribing

bitsgrecco’s picture

Subscribe

salvis’s picture

Issue summary: View changes
Status: Postponed » Closed (outdated)