Implement and use a hierarchy stack to avoid storing delete events for child entities

• Type: Technical Task
• Status: Closed
• Resolution: Completed
• Affects Version/s: 6.2.0 CE M6
• Fix Version/s: 6.2.0 CE B1
• Component/s: Social Networking, Social Networking > Activities, WCM Staging > Export/Import
• Labels: None
• Similar Issues: Show 5 results ; ;

  LPS-35373	Implement parent-child relationship between activities
  LPS-36572	Revert to leaving the social activity stream intact when an entity is deleted
  LPS-38608	Change the way we're using TrashVersion and store original non-approved statuses for child entities
  LPS-27158	Add support for creating hierarchies of sites and navigating through them
  LPS-36037	Create a SystemEventEntry model to store system events (used for deletions for now)

When a container entity is being deleted, it recursively deletes all of its children. Having a separate entry for each of these delete events is unnecessary, so a hierarchy stack should be used so that child events can be detected by the system event service.

For delete events the one for the parent should be enough (deleting the parent entity on the import side should delete all child entities).

To handle this filtering generically, we should have a place (portal.properties for now) to configure this behavior for events.

[Evan Nagayama]

Closing as complete see story ticket for testing.