Case Status: Workflow, Actions & Triggers?
Is there a document which describes a way to, demote from front page, cases which have been closed, on submit?
I'm playing with Actions & Triggers, thinking about investigating Workflow but as you probably know, learning modules in Drupal can be a bit frustrating when you find that this module can't do what you require without re-writing something.
I'm no PHP programmer and I imagine I'd be classed as a beginner Drupal builder, I'll keep on plugging away and will update this Issue when I find an answer.
If anybody has been here before, a little direction would be welcomed.
Maybe I need a differnt Issue Tracking/Project module. I'm using it for personal project management (Getting a wedding cake organised / Tracking the build of another website) so Case Tracker looked like the best option...
Nick
#1
I re-read my post and it sounds a little terse. Sorry if that's how it came across I was trying to be clear and impersonal lol!
#2
I haven't looked into using actions and triggers or workflow with casetracker, but I can certainly imagine some compelling reasons to do so.
However as the maintainer, it I haven't tried this yet, nor heard of anyone trying it, there is probably little chance that anybody else has... I'm very interested in what it would take to make some of case tracker work with some of these, but I'm sure it'll require some coding.
If you do play with actions/triggers or workflow with case tracker please be sure to post back here with what you discover.
#3
I am looking at actions integration with an eye toward Views Bulk Operations. Not sure how far I'll get, but I'll report here with whatever I find.
#4
I've written a casetracker_actions module which directly touches the casetracker_cases database table. I'm trying to figure out how to programmatically create a case comment so updates will happen gracefully for non-administrative users.
Users with "administrate case tracker" permission have a checkbox to turn on "invisible mode" and use the current mechanism. Any pointers on generating a comment, and with the case fields, would be much appreciated.
I'm not even thinking about the specific request about de-promotion, so I won't claim the issue.
Also, I believe the Rules module has trumped Workflow as the "Way of the Future". The problem of Actions integration for Casetracker remains though.
#5
Why aren't you trying Workflow and workflow-ng modules?
#6
Casetracker Actions is at a 1.0 level of completeness. Trying to determine whether it should be a new project or be posted here for inclusion as a submodule.
In the meantime, the issue at hand. If you want to demote cases from the front page manually, you will need a special Action, or possibly just a special workflow/rule. If all you want is to limit the front page to cases with a priority greater than Low, you are thinking too hard.
Voila, you now have a front page with no low-priority views.
#7
The best way for me to evaluate this is if you can post it as a patch, or at link to a tarball.
As I'm not so familiar with actions I'd like to see what this sort of implementation entails before I deiced whether I think it should be included here.
Thanks.
#8
Here it be.
#9
Grayside thanks for your work here. I've added most of your work to casetracker, with some code style clean-up and a couple language change. Two things I've omitted;
1) the README.txt, I'd prefer to include this type of information in the main README.txt.
2) The default view, it didn't work for me and I didn't have the time the troubleshoot. Also I'm not sure how I feel about including a default view that depends on a module we need to detect at run time.
A couple questions as well;
1) I think I'd like to remove 'invisible mode'. Let to my own devices I'd remove it, but can you tell me more about how you're using it?
2) I'm not happy with how the subject and comment body are being populated, but I'm not certain about the best way to populate it. At least we should provide a setting.
#10
Very pleased to hear some of this got in, glad I could help.
Dropping the View makes sense, as it does add a dependency. However, I think one of the most common use cases for Casetracker Actions is an administrative interface. It is probably worth noting in documentation somewhere.
1) Invisible mode is meant to provide administrators with the ability to quietly make changes to the content. I do not have a clear use-case in mind for this, but I've always noticed it to be one of the first three feature requests folks seem to pile on to an administrative interface.
2) I'm not sure what the best approach is either. I stared at the API until I saw an approach. I don't know what you mean by "a setting".
#11
I've opened two tickets to continue the conversations on the details now that this functionality is committed.
Invisible mode removal: http://drupal.org/node/538830
Title and subject text: http://drupal.org/node/538832
#12
Automatically closed -- issue fixed for 2 weeks with no activity.