Deleting Items
Deleting an item removes it from the database. Only a user with the DeleteItem permission can delete an item of any type; however, your administrator can assign the ModifyDeleteItemRule permission, allowing a type administrator to set a type rule that specifies which users can delete items of that type. Deleting an item removes the item history and any links to attachments, change packages (change package members associated with the item are not deleted from the database), relationships (including both forward and backward relationships), and some history records from related items. If you delete an item containing relationships, the history of each related items denotes the ID of the deleted items, the user that deleted the items, and the date of the deletion.
Key Considerations
• Deleting an item is irreversible.
• The ID of a deleted item is never reused.
• Do not delete document model items. Items that play a role in the document data model are linked in a document’s history, so when you delete an item, you change the history of that document as if the item never existed.
If you do delete a document model item, the following is true:
◦ If a document item (segment) is being referenced by a node that exists in another document, the segment item cannot be deleted. For example, document A contains a node that references subdocument B. You cannot delete segment B until you first perform a remove content operation on the node from document A.
◦ If a document item contains content (the Contains relationship is not empty), the document item cannot be deleted. Remove the content before attempting to delete the document item.
◦ If a node is part of a document (node has a Document ID value), the node item cannot be deleted until it is removed from the document.
◦ If the shared item is referenced by any nodes that are still contained by a document, the shared item cannot be deleted.
• If document versioning is enabled, a live document or content item with versioned items cannot be deleted.
• If you are using both workflows and documents, and configuration management, do not confuse an item’s change package members with project or Sandbox members.
Related Links