-
1. Re: Best way to extend Tasks in 4.3?
sebastian.s Jan 28, 2010 6:57 AM (in response to gfreeman)Consider voting for the issues or even helping with implementing them:
-
2. Re: Best way to extend Tasks in 4.3?
gfreeman Jan 28, 2010 10:15 AM (in response to sebastian.s)Thanks for pointing those out. I think I might just do that (help implement it).
-
3. Re: Best way to extend Tasks in 4.3?
sebastian.s Jan 28, 2010 10:21 AM (in response to gfreeman)Regarding how to implement it I cannot help you, sorry. Regarding the use of EventListeners I have just read very quickly trough your post but I think you should also have a look at https://jira.jboss.org/jira/browse/JBPM-2644 before running into issues like task not being found when they are executed. -
4. Re: Best way to extend Tasks in 4.3?
kukeltje Jan 28, 2010 2:17 PM (in response to sebastian.s)I added a comment to the xsd extensibility. Personally, I'd go for extending the jBPM task functionality instead of making jPDL (even more) extensible. -
5. Re: Best way to extend Tasks in 4.3?
sebastian.s Jan 28, 2010 2:22 PM (in response to kukeltje)In reply to your comment, Ronald:
So you propose to make tasks extensible in general to enable people to use their own properties on them? If I got you right I like the idea.
-
6. Re: Best way to extend Tasks in 4.3?
kukeltje Jan 28, 2010 2:50 PM (in response to sebastian.s)Yes, and realy make it possible have the task handling process (from create to end/cancel) be customizable in a jpdl kind of format as has always been the intention
<task-lifecycle initial="open"> <state name="open"> <transition name="complete" to="completed" /> <transition name="suspend" to="suspended" /> <transition name="cancel" to="cancelled" /> </state> <state name="suspended"> <transition name="resume" to="open" /> <transition name="cancel" to="cancelled" /> </state> <state name="cancelled" /> <state name="completed" /> </task-lifecycle>
This should be customizable where you can have mailnodes sending mail between states with custom templates etc...
-
7. Re: Best way to extend Tasks in 4.3?
kukeltje Jan 28, 2010 2:53 PM (in response to sebastian.s)Oh, and you could ofcourse also use processvariables there, maybe even have multiple named task-lifecycles which you can refer to in a task and maybe even include specialized ones IN business archives... Kind of like a specialized subprocess -
8. Re: Best way to extend Tasks in 4.3?
sebastian.s Jan 28, 2010 3:46 PM (in response to kukeltje)So this would also address the problem with escalations which are not working right now. (I am refering to the issue that a timer on a transition leaving a user task right now leaves the task open but also incompleteable and indeleteable.) -
9. Re: Best way to extend Tasks in 4.3?
kukeltje Jan 28, 2010 6:54 PM (in response to sebastian.s)Nope, this 'taskflow' is not for 4.4, this is al little longer term issue...
The issue of task not closing is running fine locally here as you can read in the bug report. The only thing is that I 'abuse' passing a temporary process variable (one with a very specific kind of jBPM internal name and never accessible by the customer (it is deleted before that would be possible) Yet it still is a hack, so waiting for an answer by one of the core devs, so that will mostlikely be fixed in 4.4, either with a temporary 'hack' or done right