How does checkout for synchronize determine if file needs to be updated/refreshed?
CA Harvest SCM all versions and platforms
Checkout for synchronize depends upon the existing signature file [harvest.sig] on the client path. If it's information is same as latest version in harvest repository then no need to update.
NOTE: Changing file attribute in file system does not affect this.
So developer needs to ensure correct context is set so that relevant client path is chosen.