-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
None
When you're about to activate a child, so that its parent has to be created by the receive filter explicitly, this child is removed properly when commit/rollback, however the parent stays there. It affects both the situations when you're about to activate the content for the first time, as well as if you're about to update the existing content. This can introduce inconsistencies to any next activations to the same parent tree.
Acceptance criteria
- clones
-
-
- Closed
-
