[jboss-user] [jBPM Users] - Re: Conditional Task Assignment with Fork
There is a discussion going on about this "issue" at the moment. Right now you can only complete tasks which belong to an execution and you can only delete tasks which were created independently. However if modelling an escalation from one task to a second one the first tasks remainds open and incompleted in the user's task list but it can't neither be deleted (because it belongs to an execution) nor completed because it is not active anymore. Join the discussion in the dev's forum and have a look at the matching JIRA issues. One idea is to introduce an additional state for tasks: cancelled View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4263697#4263697 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4263697 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [jBPM Users] - Re: Conditional Task Assignment with Fork
hi,
I've tried a different look around for this.
viz., Assign all tasks with fork and delete unnecessary tasks with
taskService.deleteTask();
But I'm getting error like this:
org.jbpm.api.JbpmException: tasks related to an execution must be completed.
they cannot just be deleted
Conversely javadoc suggests like this:
anonymous wrote : /** Deletes the task without completing indicating the
reason. Example reasons
|* could be: "failed", "error", "exited", "obsolete" or "deleted".
|* The history information is kept in the DB.
|* The reason ends up as the state in the {...@link
HistoryActivityInstance}.
|* If this task was created in the context of a process execution,
|* the execution remains active and the {...@link
ExecutionService#signalExecutionById(String)}
|* is to be given explicitly. */
http://docs.jboss.com/jbpm/v4/javadocs/org/jbpm/api/TaskService.html#deleteTask(java.lang.String)
Am I'm missing anything ??
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4263683#4263683
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4263683
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [jBPM Users] - Re: Conditional Task Assignment with Fork
Relax .. if you post on Sunday you shouldn't expect people to have reacted a lot by Monday ;-) Regarding your question: No, in jBPM you cannot model 'optional'/'mandatory' tasks in the process. However, I'm guessing you can model something alike using a decision after the task, a wait state before the join and a custom activity which triggers waiting executions. But I haven't thought this through so I could be completely wrong here ... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262930#4262930 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262930 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [jBPM Users] - Re: Conditional Task Assignment with Fork
Plz reply [/img] View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262172#4262172 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262172 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
