Wacom STU-530 Signature Pad

replied on January 6, 2017 • Show version history

@████████ - who's your VAR? I noticed you are in Financial Services in Salt Lake City (me too!) so I was thinking that your VAR is maybe Millennial Vision... If so, they are currently helping me with this very problem.

1 0

View 5 previous replies

replied on January 9, 2017

It is indeed Millennial Vision. I reached out to them about the same time as posting the original message. We haven't had much progress since then though.

0 0

replied on January 9, 2017

Oh cool. @████████from Millennial Vision has demonstrated the functionality for me, and it works pretty good (in IE only). I have all the documentation he provided me. I haven't been able to get it to work myself, because the Wacom plugin isn't registering in IE. We actually have some MVi installers in our office today, so I'm asking them to take a look.

I'll let you know how it goes.

0 0

replied on January 9, 2017

That would be great. Thank you. If we can get it working in IE alone, that would be more than sufficient.

Thanks!

0 0

replied on January 11, 2017

Hey @████████ - we got the signature pads working in our environment. In my case, simply adding the MVi Receipt Capture product resulted in the code I was using in forms starting to work. Since it is code that was written by Millennial Vision, I don't think I can share it here, but I recommend reaching out to Neal Leavitt at MVi - he is aware of your post here.

Good luck!

0 0

replied on January 25, 2017

@████████ - I was able to get the Wacom Pad to finally work with my computer and capture the signature! I've hit a bit of a snag after that though. The way we set it up with MVi, the image of the signature displays in an HTML field. That image works fine in the form that is being signed, and saves long enough to display the signature on the Thank You/Confirmation Page. (See first image/Capture)

Since the HTML fields aren't assigned a variable within forms, I've not been able to carry the image to further stages in the business process, and ultimately to the repository. It only displays the sign button in later stages, and archived version. (See second image/Capture2)

Have you had any success in getting this image to carry forward? Is there a way to regenerate the image based on the sig_data field?

Capture.JPG (13.73 KB)

| Download

Capture2.JPG (11.01 KB)

| Download

0 0

replied on January 26, 2017

I haven't tested it on a live working form yet, so I hadn't encountered that issue (yet). But when I went in to try it out, I found that it's not working at all right now to retrieve the signature from the sig pad and return it to the form. Something seems to have broken when I upgraded to 10.2.

I'm going to be talking to MVi about it later today, so if we make any progress, I'll let you know.

If I understand the process correctly (and that's questionable) - the script should be getting the signature data and storing it into a multi-line field with CSS Class of sigdata. And then the script actually uses that data to create the signature image in the HTML field. So if it's not populating onto a later stage in your process, I'm wondering if something had gone awry that that multi-line field.

There should be a bit of CSS code that says: .sigdata{display:none;}
This causes that sigdata field to be hidden from the user. Maybe try commenting that out (add /* before and */ after) on your form(s) and see if the values in that field are carrying over between your processes. That's at least a starting point to researching it.

1 0

replied on January 30, 2017

I was able to find a solution.

As it turns out, Forms wasn't recognizing the custom html fields in the later portions of the process to be connected to the custom fields in the original, starting form.

However, if you take your original, starting form, and make a copy of it, Forms will then recognize that they are supposed to be connected, and will carry the image forward to latter stages of the process, and ultimately the repository.

(I've likely oversimplified, and can explain more in depth if needed).

It'll be a bit tedious going back to older forms and recreating all of the later step in the various processes, but at least new forms I know going forward, that this is a working solution.

0 0

replied on January 31, 2017

That makes sense.

Since custom HTML doesn't carry over across forms, the actual signature data is being stored in the hidden multi-line field, and then the Javascript is creating the signature image based on that hidden field, therefore all those fields would need to exist on every form that you want the signature to display on, so that it can "re-create the signature image" on each form.

FYI - I still don't know why it's not working in 10.2. MVi is looking into it, to try to determine what part of the code has broken with 10.2.

0 0

replied on June 3, 2021

Hello Evan,

Did you use the SigCaptX SDK from Wacom to get this working?

If so do you mind briefing me please on how to get the image on the canvas.

1 0

View 1 previous reply

replied on June 3, 2021

Yes, this is done with SigCaptX (we use version 1.18).

The files we use we got from our VAR (Millennial Vision) and I know Evan did the same.

There is a script file on the server, which the Javascript in LFForms calls, and then does a bunch of other Javascript within the document itself to manipulate the signature pad, retrieve the signature, and populate it into a multi-line field and generate visually via HTML.

Personally, I've done a ton of customization beyond what Millennial Vision original provided to me, but the framework is still what they wrote. I wouldn't feel comfortable sharing any of their code here. But if you were to coordinate something with them to get access to the code samples they wrote, I'd be happy to share any of my own customizations I made on top of that.

1 0

replied on June 3, 2021

Matthew is correct in that our VAR ultimately got it to work. (Millennial Vision) Since it is their code and work, deferring to them in terms of accessing it would be best.

I will note that we only had success using version 1.18 of SigCaptX. Other versions would draw on the form and browser, but wouldn't draw on the sig pad. I'm not sure if Matthew had similar challenges with other versions or not.

1 0

replied on June 3, 2021

Thank you guys, I appreciate the feedback.

I will speak to my superiors about contacting Millennial. I was attempting to put the signature on the existing Forms' canvas and maybe I just need to change my approach. I will also try the 1.18 version

2 0

replied on June 3, 2021

That is true about what Evan said with the other versions being finicky. We also had a lot of issues with our anti-virus stopping SigCaptX from working.

2 0

Question

Question

Replies

Sign in to reply to this post.