-
1. Re: Using TaskManagement for non node specific TaskInstances
kukeltje Jun 4, 2008 7:00 AM (in response to camunda)Nice discussion for in Dublin... I'm 'struggling' with this to
-
2. Re: Using TaskManagement for non node specific TaskInstances
aapthorp Nov 30, 2008 11:59 AM (in response to camunda)The solution I came up with for creating ad-hoc tasks (no attached process) is to define a very basic process; start state, task and end state and then instantiate that.
Got this working using a calendar client (Lighting etc) with the Ical wrapper http://www.jboss.com/index.html?module=bb&op=viewtopic&t=131571 I've been working on. -
3. Re: Using TaskManagement for non node specific TaskInstances
kukeltje Dec 1, 2008 3:49 PM (in response to camunda)Yes, we know that it is possible this way, as was advised the last couple of years. But in jBPM 4 it will be close to what Bernd proposed but simpler
-
4. Re: Using TaskManagement for non node specific TaskInstances
aapthorp Dec 1, 2008 5:51 PM (in response to camunda)Oh, OK, hadn't come across this in searching the forum or wiki, hence the post.
-
5. Re: Using TaskManagement for non node specific TaskInstances
tom.baeyens Dec 2, 2008 2:50 AM (in response to camunda)we always envisioned tasks to be created without a process. so the necessity as you mentioned to have a process to create a task is basically a bug that sneeked in somewhere. so yes, we'll make sure these use cases are addressed in jbpm 4. when the alpha 1 comes out (target jan 1st), check out the api. it 'll already contain some basic task mgmt api functionality to create tasks unrelated to process executions.
-
6. Re: Using TaskManagement for non node specific TaskInstances
aapthorp Dec 2, 2008 1:03 PM (in response to camunda)Thanks, will look out for the alpha...