Search:     Advanced search

Understanding Electronic Signatures

Article ID: 455  |  Last updated: 27 Apr, 2017

You can require electronic signatures when users change records in Helix ALM. When electronic signatures are required, the user is prompted to enter an electronic signature and an optional reason when a record is created, modified, or deleted. When the record is saved, the user’s name, ID, and change reason are stored with the record.

For most users, electronic signatures are validated by comparing the password with the username and password. For single sign-on users, the electronic signature is validated through the Helix ALM License Server and the LDAP server. LDAP users that use an alternative form of login, such as swipe cards, must have an electronic signature password stored in their user profile to validate electronic signatures.

See the Helix ALM help for information.

Article ID: 455  |   Last updated: 27 Apr, 2017
electronic signature audit

Prev   Next
Setting Drop-Down Field Values to Not Set in the TestTrack SDK     Upgrading Workflow Event Dates to TestTrack 2008 and Later