activiti
ut in a callActivity allows the possibility to write a result from a subprocess back to its parent process.
However, activitiut does not work in a multi-instance of callActivity, which means there are no ways to write the result back to the main process when you are in a loop.
I think it is very important. One of the Scenario I can think of, is to terminate the loop under some result receiving from a sub-process. For example, when an activity inside a subprocess fails, you may want to set a variable to say the loop to terminate immediately (with <completionCondition>)…
[size=150]Solution[/size]:
One possible solution I've already tested successfully, is to pass a list from our main to the sub process (well, you can say, pass by the value of a reference)
[attachment=1]activiti.jpg[/attachment]
[size=150]Problems:[/size]
But another problem, when you use a userTask inside the subprocess, then whatever changes to the list before the userTask, the list will be empty after that.
[attachment=0]activiti2.jpg[/attachment]
I guess, at the userTask, a transaction is completed and all data are persisted to the database. After that, the list we want to reference to, may be not the same list anymore. The above scenario is for sequential loop. For a parallel loop, it is a little bit different. But I want to discuss about sequential loop first. Any ideas to solve the problems would be helpful.
thank you
ut in a callActivity allows the possibility to write a result from a subprocess back to its parent process.However, activiti
ut does not work in a multi-instance of callActivity, which means there are no ways to write the result back to the main process when you are in a loop.I think it is very important. One of the Scenario I can think of, is to terminate the loop under some result receiving from a sub-process. For example, when an activity inside a subprocess fails, you may want to set a variable to say the loop to terminate immediately (with <completionCondition>)…
[size=150]Solution[/size]:
One possible solution I've already tested successfully, is to pass a list from our main to the sub process (well, you can say, pass by the value of a reference)
[attachment=1]activiti.jpg[/attachment]
<callActivity id="callactivity1" name="Call activity" calledElement="subProcess"> <extensionElements> <activiti:in source="list" target="list"></activiti:in> </extensionElements> <multiInstanceLoopCharacteristics isSequential="true"> <loopDataInputRef>…</loopDataInputRef> <completionCondition>${list.size()!=0}</completionCondition> </multiInstanceLoopCharacteristics></callActivity>[size=150]Problems:[/size]
But another problem, when you use a userTask inside the subprocess, then whatever changes to the list before the userTask, the list will be empty after that.
[attachment=0]activiti2.jpg[/attachment]
I guess, at the userTask, a transaction is completed and all data are persisted to the database. After that, the list we want to reference to, may be not the same list anymore. The above scenario is for sequential loop. For a parallel loop, it is a little bit different. But I want to discuss about sequential loop first. Any ideas to solve the problems would be helpful.
thank you
The simplest solution imo would be to allow for expressions in the activitiut, allowing to write variables like activitiut="myVar-${loopCounter}". Would that cover your use case?
ut, allowing to write variables like activitiut="myVar-${loopCounter}". Would that cover your use case?
I'm very glad that you replied to this topic.
Your suggestion is to write variable from every sub process to different variables of the main process. It's a good idea,. But sadly, the problem is, the element activitiut does not work. activitiut does not write any thing when being used in a multi-instance, even a value like this:
So when I looked back in the source code of MultiInstanceActivityBehavior, seems like there are no functions to set variables to its parent process when a sub process "leave"
Your suggestion is to write variable from every sub process to different variables of the main process. It's a good idea,. But sadly, the problem is, the element activiti
ut does not work. activitiut does not write any thing when being used in a multi-instance, even a value like this:
<activitiut sourceExpression="${"HelloWorld"
}" target="i"></activitiut>
So when I looked back in the source code of MultiInstanceActivityBehavior, seems like there are no functions to set variables to its parent process when a sub process "leave"
