Description of problem: I have problem with reopening of process (close Problems, etc.). If this process contains MI subprocess whose MI properties are not defined then such MI subprocess is transformed to embedded subperocess. This is problem because Embedded subprocess does not contains MI properties and subprocess cannot be easily transformed back to MI subprocess. Mostly it means deletion of content of such subprocess and create it again. This can be a very painful workaround. Version-Release number of selected component (if applicable): 6.1.0 DR3 How reproducible: MI subprocess without MI properties Steps to Reproduce: 1. Create process with MI subprocess 2. Do not set MI properties (check that source code shows just subprocess element) 3. Close Problems tab (reopen process) Actual results: Process contains just embedded subprocess. Now I cannot set MI properties. Expected results: Process contains MI subprocess. I think that the cause of problem is that both subprocesses are represented by the same bpmn2 element (<subprocess>). Do you think that is possible to add empty '<multiInstanceLoopCharacteristics>' element into '<subprocess>' element? Additional info:
*** Bug 1168888 has been marked as a duplicate of this bug. ***
Currently you need to set both MI collection input and MI data input to save the MI-related data to XML correctly. * Can we add validation in designer so that if MI data collection is not set it is shown as a validation error? * It should be possible to set only MI collection input, not MI data input (as this is not always required). * Would it be possible to make sure a MI sub-process is reopened correctly as MI sub-process, even if no MI collection input is set? Could we fore example use an empty string as MI collection input in that case? Note that if we do that, core engine validation should automatically be able to solve the first item, as validation should catch this.
you can round-trip mi subprocesses now without having to set any of the mi related properties fix in designer master and 6.2.x branches
When the process with a MI subprocess is reopened then the process still contains MI subprocess. The subprocess element contains now the empty 'multiInstanceLoopCharacteristics' element. This issue was verified on 6.1.0 ER4.