You are viewing limited content. For full access, please sign in.

Discussion

Discussion

Forms 10.2 & Topaz Signature Pad

posted on January 30, 2017 Show version history

I have been using the Topaz T-LBK43LC-HSB-R for the past couple of year to capture signatures on multiple forms.  However, after upgrading to Forms 10.2 over the weekend, the Topaz pad does not become active after clicking the "sign" button on a form.  I have made the changes to the forms.js file, outlined here https://answers.laserfiche.com/questions/86327/Topaz-signature-Pads-and-Laserfiche-Forms,  on the server, but making this change did not resolve the issue, it actually made the body of the form not display.  Has anyone ran into this yet?

0 0
replied on February 20, 2020

Should we use the sigweb.js file or sigwebtablet.js file

 

$(document).ready(function(){
  if (!window.isPrintMode){
    $.getScript(window.location.origin+":47290/SigWeb/SigGetScript/SigWeb.js", $.initSigWeb);
  }
});

 

 

On the Topaz site, the SigWeb FAQ stated to use the SigWebTablet.js file.

 

 

Topaz DEMO source code:

 

0 0
replied on February 20, 2020

You can use SigWebTablet.js, you can refer to https://answers.laserfiche.com/questions/161191/Forms-104-and-Topaz-Signature-Pad#161851, the steps documented have been verified with Forms 10.4

0 0
replied on October 19, 2023

Hello,

Does anyone know if this will work with Forms V11?

Thanks,

Jeff

0 0
replied on October 20, 2023 Show version history

It should still work, both for classic and modern form.

Update: it seemed to work for classic form only, sorry for the inconvenience.

1 0
replied on October 20, 2023

I can confirm that this does work with Forms 11 with the latest patches.

1 0
replied on March 21, 2017

Hello Glenn, we tested the signature pad in our office and used the code Alex provided above and it worked for us in 10.2 update 1. You might want to verify that the js files were updated after the patch.  At this point I guess it's best to open a support case if you cannot get it to work.  

0 0
replied on March 16, 2017 Show version history

Good Morning Everyone,  I have made the above mentioned edits to the script, with 10.2, update 1, and SigWeb installed, and still not working properly.  When the form loads and the signature button is clicked, the signature pane does display and switches to only the draw tab at the top, however, when you sign on the pad, nothing is displayed on the signature pane on the screen.  I am attaching the script I am currently using, which i believe is the same as Alexander's recommendation above with the exception of localhost being replaced with our LF server name.  I am also attaching the warning that is seen in the Chrome console when the signature window displays.

One last thought/question...  What does enabling SSL change to this process?  I am working with a test server to enable SSL and am seeing various warnings if i leave the path to the server as http://server or https://server.domain.coms,.  

 

 

var baseUri = "http://meadelf:47289/SigWeb/";

function initSigWeb(){
  var ctx = $("#sigTabContent .signatureSettings").get(0).getContext('2d');
  ResetParameters();
  SigWebSetDisplayTarget(ctx);
  tmr = setInterval(SigWebRefresh, 50);
  SetDisplayXSize(438);
  SetDisplayYSize(150);
  SetJustifyMode(0);
  SetTabletState(1);

  $("#sigNav a:eq(0)").hide();
  $("#form-signature-dlg").on("shown.bs.modal", function(){
    $("#sigNav a:eq(1)").click();
  });
  $("span.clearSignature").on("click", function(){
    SetLCDCaptureMode(1);
    KeyPadClearHotSpotList();
    ClearSigWindow(1);
    ClearTablet();
    $("button.signSignatureBtn").removeAttr("disabled");
    setTimeout(function(){SetLCDCaptureMode(2);}, 2000);
  });
  $("#form-signature-dlg").on("hidden.bs.modal", function(){
    SetLCDCaptureMode(1);
    KeyPadClearHotSpotList();
    ClearSigWindow(1);
    ClearTablet();
  });
}

$(document).ready(function(){
  if (!window.isPrintMode){
    $.getScript("http://meadelf:47289/SigWeb/SigGetScript/SigWeb.js", function(){
      initSigWeb();
    });
  }
});

 

0 0
replied on March 15, 2017

First, make sure to apply Forms 10.2 Update 1.

Next, try using this updated javascript code on the form:

var baseUri = "http://localhost:47289/SigWeb/";

function initSigWeb(){
  var ctx = $("#sigTabContent .signatureSettings").get(0).getContext('2d');
  ResetParameters();
  SigWebSetDisplayTarget(ctx);
  tmr = setInterval(SigWebRefresh, 50);
  SetDisplayXSize(438);
  SetDisplayYSize(150);
  SetJustifyMode(0);
  SetTabletState(1);

  $("#sigNav a:eq(0)").hide();
  $("#form-signature-dlg").on("shown.bs.modal", function(){
    $("#sigNav a:eq(1)").click();
  });
  $("span.clearSignature").on("click", function(){
    SetLCDCaptureMode(1);
    KeyPadClearHotSpotList();
    ClearSigWindow(1);
    ClearTablet();
    $("button.signSignatureBtn").removeAttr("disabled");
    setTimeout(function(){SetLCDCaptureMode(2);}, 2000);
  });
  $("#form-signature-dlg").on("hidden.bs.modal", function(){
    SetLCDCaptureMode(1);
    KeyPadClearHotSpotList();
    ClearSigWindow(1);
    ClearTablet();
  });
}

$(document).ready(function(){
  if (!window.isPrintMode){
    $.getScript("http://localhost:47289/SigWeb/SigGetScript/SigWeb.js", function(){
      initSigWeb();
    });
  }
});
0 0
replied on March 15, 2017

Since Webshim is no longer used in Forms 10.2, functions from Webshim like $('canvas').getContext() are not supported unless you call reference to Webshim in custom script.

0 0
replied on February 13, 2018

Hello All,

Here is our solution that we are using as a work around.

Prereqs: I have made the forms.js modify on the forms server, we have the sigweb package installed on the machine connected to the Topaz,  and this was tested with a Topaz T-LBK460-HSB-R.

Caveat:   The javascript does allow for an empty signature as we have disabled the sign button checks.

 

var baseUri = "http://localhost:47289/SigWeb/";

function initSigWeb() {
    var ctx = $("#sigTabContent .signatureSettings").get(0).getContext('2d');
    ResetParameters();
    SigWebSetDisplayTarget(ctx);
    tmr = setInterval(SigWebRefresh, 50);
    SetDisplayXSize(438);
    SetDisplayYSize(150);
    SetJustifyMode(0);
    SetTabletState(1);
  

    $("#sigNav a:eq(0)").hide();
    $("#form-signature-dlg").on("shown.bs.modal", function () {
      $("#sigNav a:eq(1)").click();
      //$("span.clearSearch").click();
      KeyPadClearHotSpotList(); 
      ClearSigWindow(1); 
      ClearTablet(); 
      SetLCDCaptureMode(2);     
      $("button.signSignatureBtn").removeAttr("disabled");
      gSignature.sigPad._isEmpty=false;
    });
    $("span.clearSignature").on("click", function () {
        SetLCDCaptureMode(1);
        KeyPadClearHotSpotList();
        ClearSigWindow(1);
        ClearTablet();
        $("button.signSignatureBtn").removeAttr("disabled");
        setTimeout(function () { SetLCDCaptureMode(2); }, 2000);
    });
    $("#form-signature-dlg").on("hidden.bs.modal", function () {
        SetLCDCaptureMode(1);
        KeyPadClearHotSpotList();
        ClearSigWindow(1);
        ClearTablet();
    });
}

$(document).ready(function () {
    if (!window.isPrintMode) {
        $.getScript("http://localhost:47289/SigWeb/SigGetScript/SigWeb.js", function () {
            initSigWeb();
        });
    }
});

0 0
replied on March 10, 2017

This is a known issue and has been fixed in the coming hotfix.

0 0
replied on March 10, 2017

Wonderful, thank you!

0 0
replied on March 13, 2017

When you say in the coming hotfix does that mean you have a new hotfix coming or are you speaking about Update 1 that was released 3/8/2017?  I have applied 10.2 update 1 and my topaz device still isn't working with 10.2.  Can you please clarify if this is still a known issue and being resolved in another 10.2 hotfix release.

 

Thanks

0 0
replied on March 14, 2017

Do you use something like following to get the external script and call the function?

$.getScript("http://localhost:47289/SigWeb/SigGetScript/SigWeb.js", initSigWeb);

If do, please change to following to see whether it works:

$.getScript("http://localhost:47289/SigWeb/SigGetScript/SigWeb.js", function(){
initSigWeb();
});

The issue is that the $.getScript() function is asynchronous. When you call the initSigWeb() function immediately after, the script is not yet loaded so the function is not available.

0 0
replied on March 15, 2017

I just tried to modify my getScript to what you have above, but it did not effect my signature box.  I am open to additional suggestions in order to get this working.

Thanks

0 0
replied on March 28, 2017

Good Afternoon, 

I just wanted to bump this request. Is there a general ETA on the hotfix release or any other suggestions for a interim fix? Thank you guys.

0 0
replied on March 28, 2017

The fix that development referenced above was the Forms 10.2 Update 1 patch that was already released.

The javascript mentioned in this post (https://answers.laserfiche.com/questions/114543/Forms-102--Topaz-Signature-Pad#117279) works fine in a Forms 10.2 Update 1 environment (given that the URL reference and port is valid).

0 0
replied on March 29, 2017

I just wanted to confirm that this resolved the issue for us. Thank you Alex.

0 0
replied on August 10, 2017

This fix doesn't seem to work correctly with 10.2 update 1.  The code in https://answers.laserfiche.com/questions/114543/Forms-102--Topaz-Signature-Pad#117279 does indeed work but with one minor problem.  It doesn't contain the fix for the canvas click bug that another thread (https://answers.laserfiche.com/questions/86327/Topaz-signature-Pads-and-Laserfiche-Forms#98777) addressed.  If I try to use the code from that thread to wrap the function and change the forms.js, the signature stops working altogether again.  

It seems I can fix one issue or the other. Please advise. TIA!

0 0
replied on February 23, 2017

I have had the T-S460-HSB-R working sucessfully with a client running Forms up to version 10.1. The 10.2 update broke the ability to capture signatures. I have reinstalled the sigweb drivers and service, but cannot get the signature pad working with forms again.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.