Show TOC

Background documentationFile Operations in KM Folders Locate this document in the navigation structure

 

In KM folders there are commands for the following file operations.

Features

Functions for Organizing Items in KM Folders

Command

Description

Copy...

Creates a copy of the current item, so that the original is retained in the current folder. You reach a dialog box that you can use to select a target folder.

Move...

Removes the current item from the current folder and places it in another folder. You reach a dialog box that you can use to select a target folder.

Rename...

Changes item names that are displayed on the user interface.

Create Link...

Creates a link to the current item in another folder. You reach a dialog box that you can use to select a target folder.

Clipboard

You can use the clipboard to copy or move an item from one folder to another.

From the context menu of the item in question, choose   Clipboard   Copy   or   Clipboard   Cut.   Then navigate to the target folder and choose   Clipboard   Paste   from the context menu of the target folder.

The source folder and target folder can be located in different iViews in the portal.

Delete

You can delete items permanently or move them into a wastebasket, which allows you to retrieve them later on if required. For more information, see Deleted Items.

Note Note

The Copy and Move functions are not available for the root folder of an iView (that is, the first folder displayed in the folder hierarchy list).

End of the note.

When moving a versioned resource form one repository to another, the following restrictions apply:

  • Both the source and the target repositories are CM repositories.

  • Both the source and the target CM repositories are operated in DB or DBFS persistence mode.

    Note Note

    FSDB mode is not supported.

    End of the note.

  • Both the source and the target CM repositories are operated in DB or DBFS persistence mode.

  • The security manager configured for the two CM repository managers is the same.

If the source and the target repositories do not meet one or more of the above requirements, the moved resource loses its versions, and only the current version remains.