Bharat_Naik wrote on Feb 12
th, 2012 at 8:43pm:
If anything any part of the signed document is altered, the signature of client's signature will go away, that is why it is a valid e-signature while just placing a signature image using PrintString ( ) or MergeFilePrint () is not a valid digital signature, I believe.
I suspect that research beyond what I can offer is probably necessary to determine the legal requirement for your business in regard to signatures.
That said...
If it is assumed that any change to the Sesame record(s) that comprise a top-level form require a new signature, I'd recommend that you embed a signature file (a newly acquired image of your sig) in that record, that is cleared on record change. You are then notified that some number of records need "re-signed". At which point, using the one of the external-process commands in Sesame, you are provided with a "drawing" program that accepts your sig. That image file is then placed in the image element as your signature for that record. The drawing program should be invocable from a command line and, if possible, be provided with a filename for the image by Sesame.
The image files, could be organized in a sub-directory, using system security to prevent alterations/deletions. Use a unique file naming scheme to identify them by date (seconds since 1970/1980). Etc.
That way the signature is specific to the addendum, new, and dated.