P
Philip Colmer
I'm trying to design a form that requires three unique signatures. For
various reasons, I can't use the counter-signing functionality, so I can't
rely on that to enforce the uniqueness issue.
I've been researching the OnSign event handler and the object model. It
seems to me that the easiest way to ensure that a person has only signed
once is to compare the digital signatures to see who has signed each part of
the form.
The problem with that approach is that you can only do this *after* a
signature block has been created and signed, therefore added to the data.
What I cannot determine is the correct process for removing that signature
block if I don't want it any more.
An alternative approach, but I don't know if this is feasible or not, would
be for the event handler to create a standalone signature block, sign it and
then try to incorporate it into the XML if it is valid.
Any thoughts or suggestions?
--Philip
various reasons, I can't use the counter-signing functionality, so I can't
rely on that to enforce the uniqueness issue.
I've been researching the OnSign event handler and the object model. It
seems to me that the easiest way to ensure that a person has only signed
once is to compare the digital signatures to see who has signed each part of
the form.
The problem with that approach is that you can only do this *after* a
signature block has been created and signed, therefore added to the data.
What I cannot determine is the correct process for removing that signature
block if I don't want it any more.
An alternative approach, but I don't know if this is feasible or not, would
be for the event handler to create a standalone signature block, sign it and
then try to incorporate it into the XML if it is valid.
Any thoughts or suggestions?
--Philip