Multi-instance behavior BPMN spec

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-18-2013 10:10 AM
Hello. I need to do something similar to the BPMN spec "behavior=One" in a multi instance loop. It seems that Activiti does not implement this feature yet, in my tests. Am I right?
For example, I have "User Task A" executing in a multi instance loop with 3 instances. What I need is when one instance is completed, the flow continues to the next task (let's say "User Task B"), but the pending tasks from "User Task A" (the other 2 instances) can't be deleted, the users still need to do that.
If I use the completeCondition, when one task is complete the others are deleted.
Can anyone help me with this scenario?
For example, I have "User Task A" executing in a multi instance loop with 3 instances. What I need is when one instance is completed, the flow continues to the next task (let's say "User Task B"), but the pending tasks from "User Task A" (the other 2 instances) can't be deleted, the users still need to do that.
If I use the completeCondition, when one task is complete the others are deleted.
Can anyone help me with this scenario?
Labels:
- Labels:
-
Archive
3 REPLIES 3

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-18-2013 10:52 AM
Hi,
Could you also use an multi-instance embedded sub process for your use case?
Then you can place the tasks that the user should do all in the multi-instance sub process.
In that way you would get the behavior that the other user tasks are not deleted.
Best regards,
Could you also use an multi-instance embedded sub process for your use case?
Then you can place the tasks that the user should do all in the multi-instance sub process.
In that way you would get the behavior that the other user tasks are not deleted.
Best regards,

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-18-2013 11:36 AM
Hi Tijs, thanks for the answer.
The problem with your solution is that this way every task would execute as multi instance, right? But in my case, the Task A needs to be executed as multi instance, but the Task B don't. Think for example a manager (Task B), waiting his employes to fill a form (Task A). As soon as one employee complete the Task A, the manager will have a Task B to evaluate the answers from everyone, even if not all of them are completed, but the employees can still fill that form (Task A) until the manager complete his Task B.
Am I being clear? Sorry for my english
.
The problem with your solution is that this way every task would execute as multi instance, right? But in my case, the Task A needs to be executed as multi instance, but the Task B don't. Think for example a manager (Task B), waiting his employes to fill a form (Task A). As soon as one employee complete the Task A, the manager will have a Task B to evaluate the answers from everyone, even if not all of them are completed, but the employees can still fill that form (Task A) until the manager complete his Task B.
Am I being clear? Sorry for my english

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-21-2013 03:34 AM
What about a multi-instance sub-process that contains those 2 tasks?
