Hey Kyle,

This one took a while to track down.

Technical Details

The error is caused by a check on a signature canvas variable called _isEmpty that starts out true and would normally be set to false by a function called _drawPoint. This function is invoked when drawing with your mouse but whatever method the Topaz SigWeb API uses to draw doesn't cause it to be invoked. Thus, the _isEmpty variable never gets flipped to false even though a signature has been inputted. Clicking on the canvas triggers the _drawPoint function, setting _isEmpty to false and allowing you to pass the check that is performed when the "Sign" button is pressed.

Resolution

There are two different workarounds to this.

The first effectively bypasses the check by hardcoding the value of _isEmpty to false. The downside is that entirely blank signature canvases can be submitted as valid signatures.

The second is more elegant and effectively disables the check when it detects that the SigWeb API has been invoked in the form.

I will post instructions tomorrow on how to implement each of these workarounds on the Answers thread you posted in previously since at least one other person had the same issue/question there and we can keep all the information in one place.

https://answers.laserfiche.com/questions/86327/Topaz-signature-Pads-and-Laserfiche-Forms

Could you also let me know what version of Forms you're using?

Thanks,

Sam