Copying and Moving Folders or Elements
The VCS Integration feature integrates with the copy, paste, and move functionality of Designer. The results of all these actions are applied to the VCS repository. You cannot copy and paste, move an earlier version of a package, folder, or element.
Important: When you move or rename a folder or element, you are effectively creating a new entity in the VCS repository. Therefore, the previous folder or element is deleted and a new entity is created. This means that a new revision history is started for the moved or renamed entity as well. If you want to view previous revision information for a moved or renamed folder, or element, you must locate the deleted version of the file in the VCS repository and view the revision history there.
Because the default behavior of the VCS Integration feature is to add any new folder or element to the VCS repository, a copied or moved folder or element automatically appears in the VCS repository in its new location. In the case of a moved item, the previous location is deleted from both Designer and the VCS repository.
A copied folder or element is always placed in a checked out state in its new location. A moved folder or element retains its checked in or checked out state; special conditions apply when you copy or move a coded service. For more information on copying and moving coded services, see
Working with Java Services.
When you move an element that has dependents, the dependents will not be updated until you check in the moved element. This may cause failure of any services that use the dependent elements.