Each row of the explorer represents an explorer item which can be associated with the following statuses:
The read-only mode has been set by someone. Consequently, the file can be opened but the Save action is not allowed. An user who has the Set readonly flag right can remove the read-only flag on the file and then modify it.
In order to preserve the integrity of the files, visionCATS prevents many users from modifying the same file concurrently. This state indicates that someone is already editing the file. Consequently, the file can only be opened in read-only mode.
If an user was editing the file and if visionCATS stopped working unexpectedly (possible causes are: power off/reset of the machine, unexpected Windows error, unexpected visionCATS error), the server unlocks the file automatically after a few seconds.
The file is protected, i.e. it’s in a read-only mode that can’t be unset.
This happens in the following cases:
When importing a file having an e-signature on a foreign system
When deploying an item coming from the Method Library
On some of the sample files added by default when installing visionCATS
The currently connected user has created, opened or modified this file recently. For each File Types and each user, visionCATS considers the last 10 items as “recent”.
The analysis is finished (all steps are executed).
The file has a copyright. It can be edited only on the visionCATS installation where the copyright has been set. On other systems, the file will be locked.
The file has been created by using the import function or by deploying an item of the Method Library. This applies to all File Types except folders.
The file is partially signed : a E-Signature is defined but its level is inferior to the highest level. This applies to methods and analysis files. See E-Signature for more details.
The file is fully signed : a E-Signature in the highest level is defined. This applies to methods and analysis files. See E-Signature for more details.
The file is signed, but its E-Signature is not compatible with the E-Signature settings defined on the current system. This happens if the E-Signature levels and/or names have changed, or if the analysis is imported from a foreign system. This applies to methods and analysis files. See E-Signature for more details.