Sign
Command for electronic signature of current version of chromatogram. After selection, the Sign dialog will be displayed. After chromatogram is signed the option Open with stored calibration on Results tab is checked automatically to ensure consistency of displayed results.
Caution:
Chromatograms cannot be signed unless you have set up a user account in the User Accounts dialog. It is also impossible to sign a chromatogram which is READ-ONLY mode e.g., as a result of opening historical chromatogram version or not having rights to edit it.
Selects the user who is to sign the current version. A list of users from the User Accounts dialog is displayed.
Content of the Description field of selected user from the User Accounts dialog.
The chromatogram will only be signed using the name and password entered within the framework of the Clarity station.
The chromatogram will be signed using the certificate installed in your computer. Select the certificate by using the Select Certificate command.
Allows to enter the purpose of signature. Select from the preset options or supplement your own.
Date and time of signature.
Mandatory password of selected user.
Selects 3rd party certificate when selecting a signature using certificate (Sign Using Certificate).
Caution:
It is necessary to bear in mind that in case of signing chromatograms with 3rd party certificate it is necessary to have the certificate of each Windows user account installed in the Personal storage of every Windows user account used on the PC where Clarity is operated. If there would be installed more certificates for more Clarity user accounts under single Windows user account it could easily happen that various Clarity users (defined through User Accounts dialog) could sign chromatograms with someone's else certificate. This situation can occur because it is standard behavior of the certificates in Windows environment to ask currently logged Windows user for password to his/her certificate only for the first usage of the certificate during individual Windows user account login session. Every other request to sign any chromatogram with already used certificate won't invoke any other request for repeated password insertion and the selected chromatogram could be signed using any available certificate for which its correct password was entered during current session of the logged in Windows user. To avoid that, in case of wish or necessity to use 3rd party certificates, it is necessary to have for each Clarity user account its separate Windows user account with unique credentials and 3rd party certificate installed in Private storage of this Windows user account. This condition has to be handled when Clarity should be deployed in regulated environment (such as in organizations working in terms of compliance with GLP guidelines) and there should be used certificates issued by 3rd certification authorities. There is still option to avoid this complication by signing of chromatograms by credentials defined for each Clarity user through option Sign As Current User.