Details
-
Improvement
-
Resolution: Won't Do
-
Neutral
-
None
-
None
-
None
Description
Rationale
Recording such information can help us to improve resolution of correct order info when publishing content to public instances when nodes have been reordered in a subtree. This info can be also useful as well when restoring previous version of the content that has been moved to different sub-graph since we have all the information we need about it's previous location.
Expected result
Versioned node has 3 new properties saved under system node:
- previousSiblingUuid
- succeedingSiblingUuid
- parentUuid
This ticket might be a prequisite for PUBLISHING-82 ![]()
Checklists
Acceptance criteria