When an item is locked by a user Upchain should check that the local file is current. Sync or warn. Lock an item, start changing the CAD and save it locally, change mind and cancel the lock. The modified file is sitting there on your computer. If you start working on it again later, maybe a totally different detail, you may forget that it is modified. There is no warning or indicator that you have a modified file, which is one of responsibilities of a PDM system. Similarly, if I lock a bunch of files, a subassembly, and start modifying some of them. There is no warning if I Cancel Checkout on the the bunch. Upchain cancels immediately and with no awareness that some were modified. This creates a risk of using the wrong files, or the risk of lost work. Not sure what it does if you overwrite the home folder copy with a different file with the same filename. If you then cancel the lock, does it notice? I don't think there are tenant properties that help with this (update or check local copy when item is locked). Correction - GTerbrack pointed out "redownload.files.to.home.folder" will help with at least making sure checked-out files start with the vaulted version.
Show More