Documentation Center

Cascade effects of deleting objects

When you delete a logical object, version item or language item, the deletion can have an upward or downward cascade effect.

Upward cascade effect
If you delete the last remaining item of a lower level, you trigger the deletion of its higher-level item. That is:
  • Deleting the last remaining language item of a version triggers the deletion of that version.
  • Deleting the last remaining version of a logical object triggers the deletion of that logical object.
For example, imagine that your topic "Configuring the Encabulator" is a logical object with two versions, v1 and v2. A user deletes v2, which has no effect on the logical object. Next, a user deletes v1, which has the effect of triggering the deletion of the logical object itself.
Downward cascade effect
If you delete an item of a higher level, you automatically trigger the deletion of all of its lower-level items. That is:
  • Deleting a version item triggers the deletion of all language items in that version item.
  • Deleting a logical item triggers the deletion of all versions of that logical item, and of all language items in all versions.
For example, imagine that your topic "Configuring the Encabulator" is a logical object with two versions, v1 and v2. Version v1 exists in 3 languages, and version v2 exists in 5 languages. Deleting the logical object now triggers the deletion of 10 further objects: the 3 + 5 languages across the two versions, plus the two versions themselves.