A technician finishes a service visit and needs a signature against the job record. Kyo Logic’s FileMaker eSignature add-on is a starting point for exploring signature capture inside your application. The accompanying video also shows developers how to turn an existing database feature into a reusable add-on.

What does the FileMaker eSignature add-on demonstrate?

There are two useful parts to this resource: the signature feature itself and the process for packaging it so it can be reused.

The underlying eSignature Application walkthrough explains the feature. It uses a web viewer, a FileMaker object that displays web content inside a layout, to present a signature pad. The example passes the captured signature back to FileMaker and saves it as an image in a container field, the field type used to store files and images.

This article’s video builds on that application. It demonstrates how to take the existing feature and turn it into an add-on rather than rebuilding the same component in another file.

From a working feature to a reusable add-on

Watch Justin Hesser’s eSignature add-on tutorial.

If you’re following along, we recommend exploring the example application first. Seeing which layout objects, fields, and scripts capture and save the signature makes the packaging steps in the video easier to follow.

When you install the component in your application, it needs to know which record the signature belongs to and where to save the result. Those connections are worth checking before you try the adapted workflow.

Getting familiar with the signature workflow

A test copy of your application gives you room to work through the supplied example before changing it. You can capture a test signature, save it, and check the resulting record. Trying Cancel as well will show you what happens when someone stops before saving.

Following the saved image back to its destination field will help you see how the example connects the signature to a record. When you adapt the component, that destination needs to belong to the correct job, delivery, or other business record.

The original application walkthrough explains the JavaScript connection to FileMaker scripts. JavaScript is the code running inside the web viewer. Changes to that code or the scripts it calls can affect how the signature is passed back, so both sides of the connection need testing after an edit.

What is the person signing to confirm?

It helps to be clear about what the person is acknowledging when they sign. After a service visit, a customer might be confirming that the work is complete. For a delivery, they might be acknowledging receipt of the goods.

We would recommend making that acknowledgement clear on the screen so the person knows what they’re confirming. Depending on the workflow, they may also need to see a document or job summary first. How your team retrieves the signed record later is another useful part of planning the feature.

Making the signing process work for your team

The devices and FileMaker clients your team uses are the best place to check the adapted workflow. People need enough room to sign, working Save and Cancel actions, and a signature image that stays attached to the intended record when they navigate away and return.

Everyday interruptions matter, too. Someone might leave the signature empty, try again, or move to another layout before saving. Working through those cases in testing helps you decide how the application should respond.

Frequently asked questions

Do I need to understand the original eSignature Application first?

We recommend starting with that walkthrough if you’d like to understand how the signature is captured and passed back to FileMaker. That background makes this video’s focus, packaging the feature as an add-on, easier to follow.

Is this a complete document-signing service?

No. This resource demonstrates signature capture and add-on packaging. If your workflow also needs document routing, signer verification, or an approval history, those requirements would need a separate assessment for your application.

Can I use the tutorial for a different feature?

Yes! The tutorial shows how an existing database feature can become an add-on, so the approach can help with other features too. The parts each feature depends on will vary, which is why it helps to review its fields, scripts, and connections before packaging it.

Could signature capture help your team?

You can explore the free eSignature add-on alongside the video in a test file. If you’d like help connecting signature capture to a job or approval workflow, contact Kyo Logic. We develop custom Claris FileMaker applications for teams in New England and beyond.