User development,
A new message was posted in the thread "Ad hoc task creation":
http://community.jboss.org/message/525233#525233
Author : Ronald van Kuijk
Profile :
http://community.jboss.org/people/kukeltje
Message:
--------------------------------------------------------------
I don't think he means the for-each construct. Ad-hoc task creation in jBPM 3 was
something I used to. Task created just out of the blue, not related to the flow but part
of the process.
In jBPM4 you can create subtasks of a task like with
Task t = taskService.findPersonalTasks("username").get(0);
Task subtask = taskService.newTask(t.getId());
taskService.saveTask(subtask);
String stId = subtask.getId();
But these are not fully adhoc.
When you create a new task that is not a subtask, you can cast it to TaskImpl and set an
execution. Keep in mind that this is NOT api comformant and might (or might not) break in
the future. So if there is really a use case for it, make a jira issue and gather votes to
get this in the API... You'll have my vote.
--------------------------------------------------------------
To reply to this message visit the message page:
http://community.jboss.org/message/525233#525233