Show TOC

WastebasketLocate this document in the navigation structure

Use

If this function is active, users can use the UI Delete command to move items in KM repositories to a wastebasket. The content of the wastebasket is user-specific. Users can display the items in their wastebasket and restore them, if necessary.

Prerequisites

The wastebasket service is active for the repositories in which you want to use the wastebasket.

The wastebasket service is supported only for CM repositories that are operated in DB mode or DBFS mode.

Caution

However, the wastebasket can also work in other repositories (for example, CM repositories in FSDB mode, file-system repositories, or other writeable repositories that support the Move command). Nevertheless, if a user changes data in the back-end system at the same time, inconsistencies can arise. This is why SAP does not support such scenarios.

For more information, see CM Repository Manager

Features

When a user chooses the UI Delete command in a repository with an active wastebasket service, the system moves the item to a local wastebasket folder in the relevant repository:

/< Repository ID >/.~system~/wastebasket/< User ID >

At the same time, the system creates a link to the item in a global wastebasket folder for the user:

/userhome/< User ID >/Deleted Items

The global wastebasket folder for a user can contain links to items in different repositories.

In his or her Deleted Items folder , each user sees only the items that he or she has personally deleted.

Note

The system creates the /userhome/< User-ID >/Deleted Items folder the first time that the user deletes an item in a repository that the wastebasket service has been activated in. If you have not deleted any items since the wastebasket service was activated, you cannot display this folder.

Scope of Restored Data

The system restores the following data:

  • Content

  • Resource properties

  • ACLs (where available)

All other data including application-specific properties cannot be restored.

The list below contains examples of applications whose data cannot be restored:

  • Access statistics

  • Layout service (folder display)

  • Relation service

  • Subscriptions

  • Time-dependent publishing

  • Approval process

  • All comments (personal notes, feedback, public comments, ratings, discussions)

  • Classification

  • Collaboration rooms

    The wastebasket service is not supported for collaboration rooms. Therefore, content stored in the collaboration room repositories cannot be restored after deletion.

Integration in Applications

The wastebasket is transparent to applications. For example, if an application monitors deletion operations in a repository, a deletion operation using the wastebasket behaves in exactly the same manner as a deletion operation that cannot be restored. The restore operation from the wastebasket behaves in the same manner as the creation of a new object.

If you develop an application, you can use the code to define whether an item should be deleted permanently or simply moved into the wastebasket.

Reports

You can use the following reports to manage the wastebaskets during production operations:

  • Wastebasket quota check: You can use this report to define threshold values for the size of users' wastebaskets and for the time interval after the deletion date. When the threshold value is exceeded, the system can automatically delete old items.

    For more information, see Deleted Items Quota Check .

  • Wastebasket cleanup: This report searches for inconsistencies in wastebasket folders that can be caused by users or administrators during production operations and cleans them up.

    For more information, see Deleted Items Cleanup .

More Information

Deleted Items