fmESignature Link (DocuSign Edition) Now Supports SMS Delivery

When DocuSign recently announced the availability of SMS Delivery we knew this would definitely be a feature we would be supporting in fmESignature Link (DocuSign Edition), our Claris FileMaker Solution for integrating with the DocuSign eSignature Platform. Databuzz pioneered the sending of SMS messages directly from the FileMaker Platform 20 years ago and fmSMS, our FileMaker solution for sending/receiving SMS messages, has been used since then to send millions of SMS messages by organisations all around the world.

SMS is perfect for personalised notifications that you need the recipient to read and respond to quickly. Research shows that SMS open rates are as high as 98%, compared to just 20% of all emails. And, on average, it takes 90 seconds for someone to respond to a text and 90 minutes to respond to an email.

With DocuSign’s SMS delivery you can reach signers wherever they are, in the way they prefer, through real-time notifications sent directly to their mobile device – enabling them to quickly open and electronically sign documents. Some key benefits of SMS delivery:

  • Reduce completion time for agreements
  • Reach signers who don’t have or don’t want to use email
  • Increase successful transaction rates

fmESignature Link 1.41 includes support for sending requests with SMS Delivery. SMS Delivery allows you to notify signers via SMS in addition to the standard email notifications. Recipients will receive an SMS notification on their mobile phone like the following:


and can click the link and sign the document directly on their mobile device. Combined with DocuSign’s Responsive Signing functionality you can present documents for review and signing that are mobile friendly based on the signer’s device:

We have a new article on our support site that covers all the details for sending requests with SMS Delivery from fmESignature Link.

The full list of changes are listed in the version history notes here. Existing customers can download this version from the link on your original order email (contact us if you need the link to be reset etc).

fmESignature Link (DocuSign Edition) Updated to Use Authorization Code Grant OAuth Flow

When we were originally developing v1.0 of fmESignature Link back in 2018/2019 one of the first decisions we had to make was which of the three OAuth Types we should choose for handling the authentication with the DocuSign API: JWT Grant, Authorization Code Grant or Implicit Grant. Each flow has its pros and cons and we eventually settled on using the JWT Grant OAuth Flow. The main advantage of using the JWT Grant is that it doesn’t require a user to be present after initially gaining consent. The downside to using the JWT Grant is that FileMaker Pro cannot natively generate the JWT (JSON Web Token) required as part of the flow in requesting the access token that you ultimately need.

We found a workaround using a FileMaker Web Viewer and a JavaScript function that we could pass parameters to which would generate the JWT and return that as a parameter to a FileMaker script called via the FMP URL protocol. The downside to using a FileMaker Web Viewer is that this cannot be performed as a FileMaker Server script (either via Perform Script on Server or as part of a script scheduled using the Admin Console). We created some PHP files that used either the Data API or the older PHP API to handle scripts that needed to run under FileMaker Server.

We were never 100% comfortable with using the Web Viewer and as more customers have deployed and integrated fmESignature Link over the past few years we have become aware of some further limitations with using this approach. We’ve had reports that the FMP URL script wasn’t firing all the time, particularly on Windows and iOS. Troubleshooting these is particularly challenging and we often struggled to reproduce them in our own testing. Another downside to the Web Viewer approach concerned when the FMP URL script would run if you had a long running FileMaker script that you wished to incorporate the sending of a request to DocuSign. You couldn’t always control when the FMP URL script would run – at least until FileMaker Pro 19.1.3 was released. As we support all versions of FileMaker Pro from v16 onwards we couldn’t rely on this either. On Windows the script we wanted to run immediately after the Web Viewer loaded was added to the end of the FileMaker script stack and would run when the currently running FileMaker script finished, by which time the context had changed and it was too late for our script!

After implementing a similar version of the Authorization Code Grant OAuth Flow for our fmAccounting Link (Xero Edition) solution in 2019 we became convinced that this would ultimately be a much better experience for our fmESignature Link (DocuSign Edition) solution as well. It would require the user to perform an initial approval inside of the fmESignature Link file but after that we can programatically refresh the tokens without user intervention. This can also be setup a server schedule so that the token is refresh daily/weekly etc so that it will never expire.

We’ve just released v1.4 of fmESignature Link which now uses the Authorization Code Grant OAuth Flow instead of the JWT Grant OAuth Flow. If you’re currently using fmESignature Link v1.36 or earlier and everything is working well for you there’s no need to rush out and change anything here. You can continue to use the JWT Grant OAuth Flow if it’s working well for you.

If you have encountered some of the issues described above and would like to simplify the authentication and remove the dependency on the Web Viewer then you can update your existing integration using the latest version of the fmESignature Link file. We’ve put together a number of new and updated support articles to assist you with this process:

fmESignature Link (DocuSign Edition) Getting Started Guide

Authorization Code Grant OAuth Flow Setup Video

Authorization Code Grant OAuth Flow Details

Converting from the JWT Grant to the Authorization Code Grant OAuth Flow

All of the changes can be copied across from the v1.4 file into integrations using earlier versions of fmESignature Link and the process should generally take around 30 minutes to complete. In addition to the new fields, scripts and layout that you can copy across you only need to update two existing FileMaker scripts and one existing FileMaker layout. We’ve tried to keep these changes to a minimum and none of the scripts that send requests to the DocuSign API will need to be updated.

Other Changes in v1.4

In addition to the Authorization Code Grant OAuth Flow changes outlined above we’ve also include some new features in this release, including:

  • added support for PDF Form Fields transformation and a new Template Example for this
  • added support for Radio Group Tabs
  • updated Webhooks to use JSON notifications for the the eventNotification webhook (change from XML)

The full list of changes are listed in the version history notes here. Existing customers can download this version from the link on your original order email (contact us if you need the link to be reset etc).

Now that we have the Authorization Code Grant OAuth Flow changes out of the way we are working on adding support for SMS Notifications to fmESignature Link and hope to have this released shortly.

fmESignature Link (DocuSign Edition) Now Supports DocuSign Payments

Version 1.35 of fmESignature Link (DocuSign Edition) has just been released and it includes a number of exciting new features that we’ve been working on over the past few months. Here is a brief summary of the main new features in this release.

DocuSign Payments Support

With fmESignature Link you can now send an agreement to be signed which also includes a request for payment using DocuSign Payments. Customers can pay with a credit card, debit card, Apple Pay, and Google Pay using one of the supported Payment Gateways. Connecting payments and agreements into a single workflow reduces payment delays and provides a superior customer experience by allowing customers to sign and pay from almost anywhere in the world on most devices in one transaction.

DocuSign Payments are great for agreements that have and associated payment such as membership renewals, deposits, event registrations, rentals and payment authorisations.

When you send an agreement with an associated payment request the recipient is prompted to make the payment after signing the agreement:

Here’s a short video demonstrating DocuSign Payments with fmESignature Link (you can also watch this on YouTube here):

We have a new article on our support site that covers all the details for setting up DocuSign Payments and creating a template in fmESignature Link which includes a payment request.

Carbon Copy Recipients

You can now include recipients who don’t need to sign but do need to receive a copy of the completed agreement:

Check out our new support article for all the details on including carbon copy recipients.

Recipient Language Settings

You can now specify the language for signers that will be used in the DocuSign email notifications and the online signing ceremony. For example you could specify French for one signer and German for another if that is their preferred language:

This article in our support site has all the details for specifying the recipient language.

The full list of changes are listed in the version history notes here. Once again this is a free update and existing customers can download this version from the link on your original order email (contact us if you need the link to be reset etc).

fmESignature Link (DocuSign Edition) v1.3 Update

We’ve just released another free update to fmESignature Link (DocuSign Edition), our FileMaker solution for integrating with the DocuSign eSignature platform. This update includes a number of new examples for sending and updating DocuSign Envelopes, including:

  • we’ve added an example for sending a signing request using Perform Script on Server
  • you can now void Envelopes that are not completed from fmESignature Link
  • you can resend the email request to all pending recipients. This can be helpful when you need to remind recipients that have not completed the signing process
  • you can now edit the email address of an Envelope recipient and resend the email notification. This is helpful when you’ve entered the wrong email address for a recipient and need to update this and resend it to their new email address
  • you can now delete Envelope recipients whose status is still pending
  • you can now set the Event Notification Webhook URL in the Requests table (as well as in the Templates table) to allow for greater flexibility in setting this for ad hoc requests
  • you can now set the Email Body of the DocuSign emails that are sent when sending a request from fmESignature Link

The Email Body that you can set via the DocuSign API is also referred to as the email “blurb” and the standard email body if not specified typically looks something like the highlighted text in this screenshot:

You can now specify some custom text to appear in place of the default email body which will look like this:

The full list of changes are listed in the version history notes here. Existing customers can download this version from the link on your original order email (contact us if you need the link to be reset etc). We’re working on the next update to fmESignature Link that will include examples for sending requests for Payments via the DocuSign API and specifying the language used for the signing process and hope to have this released within the next few weeks.

Auto Place Makes Agreement Setup Easy with fmESignature Link (DocuSign Edition)

We recently released a free update to fmESignature Link (DocuSign Edition), our FileMaker solution for integrating with the DocuSign eSignature platform, that included support for AutoPlace. AutoPlace (also referred to as anchor tagging) is an advanced field action in DocuSign that adds fields near each occurrence of a given string in a template or document.

With a typical document you would need to specify where you wanted the DocuSign tabs (fields) to appear on the document, for example to capture a signature, initials, name or date. In the fmESignature Link file the setup for adding Template Tabs looks like this:

It can be somewhat fiddly while you work out the coordinates from the left and top of the page for each tab and can involve a bit of trial and error before you get the positioning right. This also means that your tabs are hardcoded into fixed positions on a specific page, which is fine for fixed length documents where these positions will never change.

If you’re working with a variable length document, such as the legal agreement where the length of the agreement could change depending on the number of included clauses, then you won’t be able to know in advance what page and what position to place the these tabs. Fortunately DocuSign has a solution to this problem called AutoPlace, which involves the use of hidden strings that won’t appear anywhere else in your document. The tab/field is then automatically placed in the position of your hidden text string.

This makes setting up Template Tabs in the fmESignature Link file much simpler: instead of working out the pixel positions from the left and top of your page you simply enter the matching string to look for like this:

If your agreement PDF is being generated from a FileMaker layout you simply place the corresponding string on the layout like this (I’ve changed the text colour to red to make it visible, but you would set this to the same colour as the background of your agreement which is typically white)

DocuSign then automatically place the specified tab at the position of the matching string, regardless of which page or where it appears on the final document. With AutoPlace you can have your templates setup for eSignature with DocuSign within minutes using the fmESignature Link (DocuSign Edition) solution.

We’ve added a support article that has all the details of using AutoPlace with fmESignature Link, along with a short video demonstrating the setup of this which you can watch below or on YouTube here.

fmESignature Link (DocuSign Edition) v1.25 Update

We’ve just released another free update to fmESignature Link (DocuSign Edition), our FileMaker solution for integrating with the DocuSign eSignature platform. This update includes a new Template example that utilises the Auto-place (anchor tagging) feature, as well as Webhooks that work with the FileMaker Data API (in addition to the PHP API Webhooks).

Auto Place Template Example

We’ve added another example Template that demonstrates how to use the Auto-place (anchor tagging) feature of DocuSign. AutoPlace adds fields near each occurrence of a given string in a template or document. You can use AutoPlace with any field type – it is automatically placed at all instances in your document of the specified string.

Our previous Template examples demonstrated how to place DocuSign tabs at fixed locations on a page or by reference to a DocuSign Template, but there are circumstances where you will not know in advance the page number where the tabs should be placed. For example you might have a standard legal agreement that varies in length due to the number of standard clauses that are included which might cause the document to run to 1, 2, 3 or more pages in length as a result.

Tab anchoring enables you to place tabs at every location where a specified text string, also known as an anchor, is found in a document. This allows the tabs to move with the text of the document. One common approach to anchor tagging is to use special strings that don’t appear anywhere else in the document as the anchorString property for anchor tagging, then setting the colour of these strings to match the document background, making them invisible to recipients. This enables you to easily attach tabs to many places in your documents without disrupting the signing experience for your recipients.

The new Auto Place Agreement Template uses a new layout Customer Agreement Auto Place PDF that demonstrates the use of special text strings that are used as the guide for the Auto Place tabs. If you have a look at this layout in Layout mode you will see these invisible text objects highlighted here:

These text objects have a white text colour set – the same colour as the layout background – so they are not visible when printed or saved to a PDF file. If we change the colour of these to red you can see the strings that we have set for these:

There is a new setting option on the Template Tabs tab in the Template Details screen where you can specify the same strings to associate with these. If you click the gear icon to the right of a Template Tab you will get this popover:

Here you can specify the Anchor String and any X/Y offset values. As I have specified /SigName1/ as the Anchor String for this tab it will search the document for any matches for this and place the specified tab in that location.

Webhooks Changes

In addition to the existing PHP API Webhooks we now include Data API compatible versions of these. Remember when working with the Data API you will need to enable the fmrest extended privilege for the Webhooks Privilege Set:

You’ll now find 2 folders in the PHP Webhooks folder containing the php files for both the Data API Webhooks and the PHP API Webhooks:

Both folders contain the same contents (each set of PHP files works with either the PHP API or the newer Data API) – see our DocuSign Webhooks page for further details on installing these on your server and configuring the fmESignature Link (DocuSign Edition) file for these.

Other Changes

As well as the new Auto Place Template example and Data API Webhooks updates this update includes a number of other small changes, including:

  • you can now specify the Template Tab Recipient ID to assign tabs to specific recipient
  • we’ve added the option to allow you to set the Routing Order to 1 for all recipients which means that when set all recipients will receive the signing request at the same time. This overrides the Position value that you can set when specifying the Recipient Contacts for a Request. This is helpful when you don’t want all recipients to be delayed by a previous recipient not having signed the document in a timely manner.

The full list of changes are listed in the version history notes here. Existing customers can download this version from the link on your original order email (contact us if you need the link to be reset etc).

fmESignature Link (DocuSign Edition) v1.1 Update

We’ve just released another free update to fmESignature Link (DocuSign Edition), our FileMaker solution for integrating with the DocuSign eSignature platform. This updates provides additional functionality around DocuSign Templates including:

  • you can now specify a value or a field name to use to pre-populate Template Tabs such as Text and Number tabs that can have the value set dynamically
  • you can now download the Tabs and Roles for DocuSign Templates to save you having to enter these manually (we downloaded a Template with 6 Roles and 120 tabs in under 2 seconds)
  • we’ve updated to support the latest version of the eSignature API (v2.1) and are now using a custom function to store the value of the DocuSign API to allow this to be updated more easily in the future

The new Template Tabs Value field allows you to specify a hardcoded value (e.g. “Acme Inc” for a text tab that users would enter their Company Name into) or a merge field, e.g.:

RequestsContactsContacts::Position

that will be merged at runtime as the Envelope is being constructed and replaced with the value from that field reference for the current recipient record. We’v also added a Locked field to the Template Tabs table to allow certain fields to be locked or “read-only” to the recipient. You can see the difference in the following screenshots. In the first screenshot we have set the Locked Value to false – the field has the pre-populated value but we can edit this if required:

In the next screenshot we have set the set the Locked Value to true and the field has the blue border and cannot be edited:

Here’s a short video showing the downloading of Template Tabs and Roles and how to use the new Template Tabs Value field to pre-populate custom tabs (you can also watch it on YouTube here):

The full list of changes are listed in the version history here. Existing customers can download this version from the link on your original order email (contact us if you need the link to be reset etc).

Databuzz releases fmESignature Link (DocuSign Edition) – Integrate FileMaker Pro and DocuSign

Sydney, Australia – June 04, 2019 – Databuzz today announced fmESignature Link (DocuSign Edition), a FileMaker solution that integrates with the DocuSign eSignature platform.

fmESignature Link (DocuSign Edition) is a FileMaker solution that integrates between FileMaker Pro and DocuSign. DocuSign is one of the most popular electronic signature platforms and helps organisations connect and automate how they prepare, sign, act-on, and manage agreements and allows users to sign electronically on practically any device, from almost anywhere, at any time.

fmESignature Link (DocuSign Edition) allows you to quickly send electronic signature requests and download the signed version of the document into FileMaker at the click of a button. fmESignature Link (DocuSign Edition) is completely unlocked allowing you to integrate it into your existing FileMaker solutions. You can copy and paste examples showing you how to authenticate with the DocuSign API and send signing requests and more at the click of a button.

fmESignature Link (DocuSign Edition) features include:

  • works with FileMaker Pro 16 or later
  • uses all native FileMaker scripts and functions (no plug-ins required)
  • completely unlocked for you to integrate into your own FileMaker solution
  • can be hosted by FileMaker Pro or FileMaker Server
  • works with Macintosh and Windows

“Many of our customers use the FileMaker Platform to run their business and DocuSign for electronic document signing,” said Andrew Duncan, CEO of Databuzz. “With fmESignature Link (DocuSign Edition) you can send document signing requests and downloaded completed documents from DocuSign at the click of a button, without having to give users direct access to your DocuSign account.”

fmESignature Link (DocuSign Edition) includes examples for the following DocuSign features:

  • Send Document Signing Requests: you can use fmESignature Link to send documents that are generated dynamically from a FileMaker layout, from a PDF file stored in a FileMaker container field, or using a DocuSign Template (including support for multiple recipients and roles)
  • Check Status: check the Status of Sent Requests at the click of a button
  • Download Completed/Signed PDFs: download the completed PDF file into FileMaker at the click of a button
  • Download Form Data: download any associated Form Data back into FileMaker at the click of a button
  • Support for Webhooks: have completed PDFs pushed automatically to FileMaker within seconds of being completed (requires FileMaker Server and PHP Custom Web Publishing)
  • Support for FileMaker Server Schedules: setup schedules to poll DocuSign every 20 minutes for any new completed agreements (requires FileMaker Server and PHP Custom Web Publishing)
  • Testing Sandbox support: dynamically switch between the DocuSign Sandbox test environment and the live production environment. You can perform all required tests in the free Sandbox account before switching to your live production account

 Availability, Pricing, and Compatibility

fmESignature Link is available in a number of licenses: Company, Product (Vertical Solution) and Developer. It is available now from the Databuzz website at https://www.databuzz.com.au/fmesignature-link-docusign-edition/. Company Licenses start at AUD $795.00. fmESignature Link (DocuSign Edition) requires FileMaker Pro v16 or later and a DocuSign account with API access.

Media/Customer Contact:

Andrew Duncan

Phone: +61 418 468 103

sales@databuzz.com.au

AboutDatabuzz: Databuzz is a long-standing member of the FileMaker Business Alliance. We have been developing and deploying FileMaker solutions for clients in Australia and internationally since 1999. Our clients are individuals, small-medium businesses, government agencies and multi-national corporations. Databuzz was founded by Andrew Duncan, a Certified FileMaker 17 Developer. For more information please visit our website at https://www.databuzz.com.au.

###

FileMaker is a trademark of FileMaker, Inc., registered in the U.S. and other countries. All other trademarks are the property of their respective owners.

Coming Soon – fmESignature Link (DocuSign Edition)

For a number of years we’ve been helping customers automate the management of electronic document signing requests using the DocuSign platform, one of the most popular electronic signature platforms. Managing the workflow around the sending of documents to be signed (contracts, quotes, real estate tenancy agreements etc) can be challenging when you’re using an associated FileMaker custom business application to run your business. You end up performing double data entry and updating multiple systems and inevitably something gets missed and one system is now out-of-date.

We’ve previously written about the benefits of integrating your FileMaker solution with DocuSign so you can manage the document signing process in one central place from start to finish. The new workflow could then look like this:

We’ve taken everything we’ve learned over the past few years helping customers manage their document signing workflow in FileMaker (saving them time and money) and turned this into a new product called fmESignature Link (DocuSign Edition) which we will be launching very soon.

The main features of fmESignature Link include:

  • Send Document Signing Requests: you can use fmESignature Link to send documents that are generated dynamically from a FileMaker layout, from a PDF file stored in a FileMaker container field, or using a DocuSign Template (including support for multiple recipients and roles)
  • Check the Status of Sent Requests
  • Download Completed/Signed PDFs into FileMaker at the click of a button
  • Download any associated Form Data back into FileMaker at the click of a button
  • Support for Webhooks: have completed PDFs pushed automatically to FileMaker within seconds of being completed (requires FileMaker Server and PHP Custom Web Publishing)
  • Support for FileMaker Server Schedules to poll DocuSign every 20 minutes for any new completed agreements (requires FileMaker Server and PHP Custom Web Publishing)
  • dynamically switch between the DocuSign Sandbox test environment and the live production environment

fmESignature Link (DocuSign Edition) uses all native FileMaker scripts and functions (no plug-ins required) and requires FileMaker Pro 16 or later. Like our other products it will be 100% unlocked for you to integrate into your own FileMaker solution.

We’ve put together a short preview video showing fmESignature Link (DocuSign Edition) in action sending a signing request to a contact and then downloading the completed PDF back into FileMaker at the click of a button. You can watch this below or via this link on YouTube:

If you would like to be notified when fmESignature Link (DocuSign Edition) is release please subscribe to our newsletter or follow us on Twitter or Facebook.