cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

When dropping a sandbox that was created in a non empty folder, avoid deleting other folders/files.

When dropping a sandbox that was created in a non empty folder, avoid deleting other folders/files.

User story:

1.- A user creates a sandbox in a non empty folder, for example "C:\Users\userid\Documents". The user don't create an empty folder before creating the sandbox, he creates the sandbox directly in the folder "C:\Users\userid\Documents"

2.- The user drops the sandbox selecting the option "Entire Sandbox Directory".

3.- PTC Integrity deletes the folders/files corresponding to the sandbox but also other folders/files in the Documents folder which doesn't belong to the sandbox because they were previously created. PTC Integrity doesn't send the folders/files to the Recycle Bin.
 

To avoid this situation I can think of these possible solutions:

1.- When dropping a sandbox, Integrity should only delete the folders/files corresponding to the sandbox, not folders/files that were previously there before creating the sandbox in the parent folder.
2.- A new feature can be added to PTC Integrity to send the deleted folders/files to to the Recycle Bin, instead of permanently delete them.
3.- When the user is creating a sandbox and he selects a folder that is not empty, add a new feature to PTC Integrity to display a warning saying that the folder is not empty and is better to select a folder that is empty.
4.- Add a new feature to PTC Integrity so Integrity creates an empty folder automatically and creates the sandbox in this new folder.

1 Comment
Regular Member

Anyway Integrity holds PJ file, which contains all its sub project and file information's. So deletion shall be made based on it instead of removing entire stuffs under selected project. With related to safety I strongly recommend this.