Search:     Advanced search

Helix ALM Electronic Signature Exceptions

Article ID: 395  |  Last updated: 14 Jun, 2017

If electronic signatures are enabled in Helix ALM, users are prompted to enter their username, password, and a reason for making the change when adding, editing, or deleting items. This electronic signature is saved with the items and helps enforces compliance with business or regulatory processes, such as 21 CFR Part 11.

Helix ALM can be configured to require users to enter a change reason with the following exceptions:

  • Creating items using email import
  • Creating items using SoloSubmit
  • Any item modifications using a SOAP-based interface
  • Escalation rules that modify an item
  • Attach and fix actions performed in Surround SCM except when adding or editing items from the Helix ALM Browser dialog box
  • Source control files attached from a provider that uses the Helix ALM source control CGI (ttextpro.exe), such as Helix Versioning Engine triggers or Git.

To ensure compliance, configure projects so users cannot add, edit, or delete items using these actions.

Article ID: 395  |   Last updated: 14 Jun, 2017
exceptions electronic signature

Prev   Next
Troubleshooting TestTrack Server Problems on Unix     Oracle NLS_LANG Setting