Checksum Collision and Potentially Modified Files
The following sections provide details on checksum collision and files that are considered as potentially modified:
Checksum Collision
PTC RV&S uses the checksum algorithm to calculate the checksum for working files. The working files are marked as modified if the calculated checksum differs after editing the working files. In rare cases, legitimate content changes such as updating only few characters without changing the length of the file may generate the same checksum. As a result, the system fails to detect such changes in the working files. Such a scenario is considered as Checksum Collision.
Potentially Modified Files
Starting with PTC RV&S 13.3.0, the changed working files with checksum collision or working files with identical checksums but updated timestamp are indicated separately with a 
Potentially Modified icon in the sandbox view. Such files are considered as potentially modified files till the application resolves the file modification status based on the content changes. Potentially modified files that do not have content changes are resolved as unmodified files.
Potentially Modified icon in the sandbox view. Such files are considered as potentially modified files till the application resolves the file modification status based on the content changes. Potentially modified files that do not have content changes are resolved as unmodified files. | Based on the resolution, the status of the working file is updated in the sandbox view. If the file contains modifications, the potentiality modified icon in the corresponding delta  column changes to  . If there are unmodified working files, the potentially modified icons in the corresponding delta column are cleared. |