Moving files to a new folder
search cancel

Moving files to a new folder

book

Article ID: 15839

calendar_today

Updated On:

Products

CA Harvest Software Change Manager - OpenMake Meister CA Harvest Software Change Manager

Issue/Introduction

We are planning to move all items within a certain folder to a new path, including all historical versions in our Harvest project. 

Is it possible? 

Environment

Harvest Software Change Manager v12.x and higher

Resolution

To change the parent folder of all past versions of a file would be to change the history of the file and the project and make it impossible to revert back to an earlier point in time in the project.  Harvest supports moving a file or folder to a different parent folder location (refactoring) but does it in such a way as to preserve the history of the file within the project.

With refactoring, when you execute the "Move Item" process, Harvest will create a new version of the file in it's new folder location, while leaving all previous versions in their original folder as they were.

In the state's data view, the file now appears in the new folder location.

However, if you do a "Find Version" search, you will see in the resulting list at what point the file was moved to its new location.

Because the new version is contained in a package, the package must be promoted through the states for the change to become visible in all states.

Refactoring also includes the "Rename Item" (giving the file a new name), and "Remove Item" (logically delete the file while preserving the file's history), and these processes operate in a very similar way.  With "Rename Item", the new version of the file will have its new name while the old name is preserved in the previous versions.  With "Remove Item", the new version will have a "D" tag indicating it has been deleted, and the state's data view will no longer show the existence of the file.

All three types of refactoring can also be performed at the folder level with the "Move Path", "Rename Path", and "Remove Path" processes.  When refactoring a folder, the change creates a new version of all files and sub-folders within the folder, reflecting the desired change.

 



Additional Information