We are using DTI from the web browser (i.e. not directly in Windows explorer) in Windchill 11.1, and an issue we have seen too often is that users lose several hours of work due to overwriting their locally modified files. The scenario is as follows:
1. The user checks out and downloads a document.
2. The user works on it locally.
3. The user either forgets to check in or DTI for some reason fails to check in (this happens quite a lot).
4. The user goes into Windchill and downloads the document again, believing he/she opens the latest version.
5. DTI now informs the user that a local file exists and asks if the user wants to overwrite the local file.
6. The user answers "Yes", and all local modifications are lost.
This frustrates our users a lot. As a comparison, we have another system which only manages documents. This system is a desktop application, and if you open a file which you have previously checked out and modified, your modified copy is always opened - i.e. no risk of losing any changes, and no confusing overwrite questions.
I understand that a web application behaves differently, but I believe it should be possible to improve this. Since the DTI is capable of identifying that a local file exists, I would think it should be possible to identify whether that local file has been modified compared to the server version, and always open the locally modified copy instead?