Any issues using this option under setting / users?
Local file clean-up
Automatically delete local read-only files that are not part of the file vault
Local folders and local read-only files that are stored only in the local vault view and are not part of the vault are automatically deleted.
Enterprise PDM uses a local cache mechanism; each vault view stores a cached copy of a retrieved file or folder.
For example, if a file or folder is deleted or moved in the vault from another client view, a cached local copy of the deleted file or folder is left in the local client views on other systems. This option ensures that these orphaned objects are cleaned up automatically.
Local file clean-up
Automatically delete local read-only files that are not part of the file vault
Local folders and local read-only files that are stored only in the local vault view and are not part of the vault are automatically deleted.
Enterprise PDM uses a local cache mechanism; each vault view stores a cached copy of a retrieved file or folder.
For example, if a file or folder is deleted or moved in the vault from another client view, a cached local copy of the deleted file or folder is left in the local client views on other systems. This option ensures that these orphaned objects are cleaned up automatically.
I wonder this myself.......seems like this option should on for everyone....otherwise when you move and rename stuff in the vault, users that have local copies now have greyed out files hanging around.
Is there a disadvantage to checking this option to automatically delete local files that are not part of the vault? Or rather are there cases where we might need this that will make us regret checking this later?
The one scenario that I know of that you have to tell peope to just not do is have a file in a folder that is part ofthe vault and that file is not actualy added to the vault and the user wants to make sure it doesn't get updated so they make it read-only. That file will disappear.
WT
I hate to bring up such an old topic but is there any reason why a local file can't be deleted? I re-orginized the vault and I have one pesky file that will not delete off my local machine.
What kind of error message do you get?
WT
I think this option is extremely dangerous for any user who creates new files in the Vault.
If the user is ever working offline(network down?) then any files they create will be deleted on the next check-in. Or if a add to vault operation fails, lost files once again.
I suggest only using this option only for users with view only rights. Even this is dangerous because if they ever logon to a machine that has legitimate local files, the Vault will delete them.
Regards,
Corey V
Keep in mind that for those files to be deleted, they have to be read-only, an unlikely state for files added as you suggest. The intent of that checkbox is to delete orphans.
WT
Neither of these scenarios should be an issue, for the user to be working on the files, they would not be readonly thus this option would not harm those files.