no, not a similar api. You have to do it low level
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4270057#4270057
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4270057
___
jbos
Hi,
Is there a similar API in JBPM3 that allows subTask creation for an existing
task?
Any help would be appreciated.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269914#4269914
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&m
Hi,
This is a pretty late response. Out on a trip an could not access for few
days.
The way you are creating sub tasks may not work. You should use command
service to get your job done instead of using direct methods on tasks. Command
service will ensure all the interceptors are invoked bef
Thank you for your help. It has helped us a lot to think a bit more and know
jbpm.
We are trying to follow a similar solution to yours, but, when we try to create
a new subtask on a task, an exception occurs:
|
| 09:41:12,935 SEV | [BaseJbpmTestCase] TEST THROWS EXCEPTION: no environment
How about creating sub-tasks in you actual task? Signalling flag will be false
for the sub-tasks by default. So it will not transit to the next node till you
call complete on the super task.
The following code may be used when the review task becomes active
| Task reviewTask = taskService.cre
Sorry for double posting. Is it possible to do this using a custom
ActivityBehaviour?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4264796#4264796
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4264796
Hi,
Thank you for your reply. It was helpful.
We are using the Assignment Handler right now.
Now we would like to create several instances of the 'Review' task, one for
each user. How can we garantee that the next task will only start executing
when all of the 'Review' tasks are done? We are us
Hi,
did you consider using Assignment handler?
If you implement "Read Document" as a task node and add an assignment handler
to it, which can execute whatever business logic it needs to, to decide whether
X, Y or Z or all of them or none of them can do "Read" task.
| ...
|
|
|