![]() |
Telelogic SYNERGY (steve huntington) | ![]() |
Topic Title: FDA 21 CFR pt 11 Topic Summary: Approaches to use of electronic signatures in Synergy/Change Created On: 21-Sep-2006 14:41 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Has anyone implemented electronic signatures in Change? Documentation of this feature seems to be non-existent. Any clues, strategies and best practices would be appreciated.
|
|
![]() |
|
![]() |
|
In know in Synergy/Change version 4.5, the default lifecycle uses electronic signatures. This is just an attribute with the web type of e_signature. You can check out the dev_process lifecycle that comes out of the box with Synergy/Change 4.5. I am not sure how long it has been in the product, ex. 4.3 and 4.4?
------------------------- Thanks, Brian Edited: 5-Oct-2006 at 12:43 by Brian Barde |
|
![]() |
|
![]() |
|
I have used the e-sig for approving change requests. I created new attributes with the web type of e-signature. The e-signature attribute, from my experience, can only be used on a tranistion. You can change the meaning of the signtures (approve, reject etc) through the list box manager in the admin tab. select other and you can modify the esig purpose.
------------------------- jmccarty |
|
![]() |
Telelogic SYNERGY
» SYNERGY/Change
»
FDA 21 CFR pt 11
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.