-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
-
False
-
False
-
NEW
-
NEW
-
Undefined
-
- Create a project.
- Import processes:
- Deploy the project.
- Create a process instance of "Proceso_Padre".
- Go to "Task Inbox" and completes the "SPEsperarAQueTermine".
- Go to "Task Inbox" and we will see 2 "Tarea Proceso Padre" instances.
Actual result
Go to "Task Inbox" and we will see 2 "Tarea Proceso Padre" instances.
Expected result
Go to "Task Inbox" and we should see 1 "Tarea Proceso Padre" instance.
Create a project. Import processes: SubProcess.bpmn SubProcess.bpmn Parent_Process.bpmn Parent_Process.bpmn Deploy the project. Create a process instance of "Proceso_Padre". Go to "Task Inbox" and completes the "SPEsperarAQueTermine". Go to "Task Inbox" and we will see 2 "Tarea Proceso Padre" instances. Actual result Go to "Task Inbox" and we will see 2 "Tarea Proceso Padre" instances. Expected result Go to "Task Inbox" and we should see 1 "Tarea Proceso Padre" instance. -
Given a parent process with 2 tasks: a Reusable sub-process task where the sub-process is executed once and it contains one Human Task "Tarea 1 SPEsperarAQueTermine", and a Human Task "Tarea Proceso Padre".
When the Reusable sub-process ends, 2 tasks are shown in the "Task Inbox" waiting for executing the Human Task. It seems that the invocation of the Reusable sub-process ends more than once, so many instances of the human task "Tarea Proceso Padre" are created as many times the invocation of the Reusable sub-process has been completed.
- clones
-
-
- Closed
-
