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
Comment #1
salvisI 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:
Comment #2
develcuy commentedThank you @salvis, I appreciate your guidelines but have to leave this as a proposal by now, I'm overloaded of job...
Blessings!
Comment #3
jwarner commentedSubscribing
Comment #4
mudd commentedSubscribing
Comment #5
bitsgrecco commentedSubscribe
Comment #6
salvis