Page Comparison

All old versions of the object are deleted as well.

The assigned binary content files are only deleted from the repository A folder object can only be deleted if it has no child objects, i.e., if there are no objects retrievable via the yuuvis® Momentum API that have the specified objectId as value for the system:parentId property.

Objects under retention cannot be deleted (for more details click here).

As of 2023 Summer, the optional query parameter waitForSearchConsistency can be added to the request URL. If not specified, the default value true is used.

As of version 2023 Spring, the API gateway can be configured to support either synchronous deletion (default and behavior up to version 2022 Winter) or asynchronous deletion.
>> serviceConfiguration.json

Synchronous Deletion

A successful response is returned as soon as:

• the binary content files assigned to the current object or an old version are deleted from the repository (if no other object or object version refers to them

• ),
• the object's metadata is deleted from the database and search index,
• the metadata of all old object versions are deleted and
• the entries 202 and 200 are created in the audit trail.

All previous audit entries for the deleted object remain in the database and can still be retrieved via search.A folder object can only be deleted if it has no child objects, means if there are no objects retrievable via yuuvis® Momentum API that have the specified objectId as value for the system:parentId property

Asynchronous Deletion

A successful response is returned as soon as:

• the object is flagged in the search index to be invisible and excluded from search results and
• the entry 202 is created in the audit trail.

All previous audit entries for the invisible object remain in the database and can still be retrieved via search.

Metadata and binary content are still stored in the search index, database and repository. However, for the users, they are considered as irrevocably deleted. They can be finally removed by a background process, e.g., via the COMMANDER service using the maintain-delete command.