Hello everyone,
The system we currently use at our office is currently built upon the casetracker module. However, the challenge we are encountering is enforcing a "workflow" on those nodes in our system. It would be great to be able to integrate casetracker with workflow so that changes are detected and that changes to the those fields are acted upon and processed.
Since casetracker already has a "status" field to use with cases, it should be be possible to use the States API to expose those states to the state machine, right? And then from there have workflow-ng detect when a comment is posted that changes the state of the case and can execute actions. The only thing that really doesn't make sense is where states come into play in workflow-ng... they only seem to play a role in the workflow module. Having states would also be nice so that we can give users control of what states/statuses they can changes their cases to... i.e. so they can't change it from "processing" to "new" again.
Once this capability is done, it would be possible to handle events like case reassignments, status changes, priority changes, etc and move a lot of the action code into UI-configurable actions that do not require code changes to change.
So, to workflow-ng would the act of posting the comment (with the condition of changing the status field) be the event that would trigger the workflow? Or would it be better to define a new event that detects just the status change of the case? I'm a little confused on this part.
This will really require some changes in the casetracker module, but it would be worth it to allow cases to take advantage of the state engine. Does this make sense, or should I be going in a different direction?
Comments
indeed, that would be cool.
indeed, that would be cool. I think it would be best to do a token integration for the casetracker stati - or as another option add conditions like "status of a case changed" - that are configurable to only match on certain states.
So I think you don't need to convert anything to the state machine API.
The assigned user, could be loaded by an action (by the help of a brand-new-API enhancement). Then one can use the usual user comparison to detetct a change of the assigned user.
I'm curious to know why you
I'm curious to know why you think it doesn't need to be converted to state machine API...
because workflow-ng can work
because workflow-ng can work with the existing data. casetrack just needs to provide tokens or conditions, which allow workflow-ng to work with it.
e.g. one could add a condition to casetracker
* stati of content changed
-> in the condition configuration form, one could provide the possibility to restrict the condition to match only certain state changes.
-> then when a node is updated - or a comment posted - workflow-ng can use this condition
Docs for creating tokens?
Are there some docs for creating tokens for modules? I can't seem to find any.
Nevermind, found them...
In case you're like me and need help finding them, you can find them in API.txt in the token module directory.
any progress?
I am using casetracker and trying to get the hang of workflow_ng as well and can see the benefit of marrying the two.
Craig Bertrand
Craig Bertrand
agreed!
My office is using casetracker and would like to implement some workflow into the states as well. Has there been any progress or another solution in the past 2 years? :D