fmESignature Link (DocuSign Edition) Frequently Asked Questions
What versions of FileMaker Pro/Pro Advanced does fmESignature Link (DocuSign Edition) require?
fmESignature Link (DocuSign Edition) currently works with FileMaker Pro/Pro Advanced v16 or later. We continue to develop fmESignature Link (DocuSign Edition) and will ensure it works with future releases of FileMaker Pro Advanced.
What type of DocuSign plan is required?
To use the DocuSign API you need to be using either a DocuSign API plan or have API accessed included in your plan. Please contact DocuSign directly to check if API access is included in your current plan.
Can I use fmESignature Link (DocuSign Edition) with FileMaker Server scripts/Perform Script on Server?
Yes you are able to use FileMaker Server scheduled scripts or Perform Script on Server to check for completed documents. We included some examples in the fmESignature Link (DocuSign Edition) file for polling the DocuSign API every 20 minutes to check for new completed documents. These server scripts will require PHP Custom Web Publishing to be enabled on your FileMaker Server and you to host some included PHP files on your server – see our Server Scripts/Webhooks page for full details.
Is FileMaker Pro Advanced required?
FileMaker Pro Advanced is only required to copy/paste the Custom Functions that fmESignature Link (DocuSign Edition) file uses when you are integrating this into your own FileMaker solution file. Otherwise you can use both FileMaker Pro and Pro Advanced when using the fmESignature Link (DocuSign Edition) functionality (N.B. since the release of the FileMaker 17 platform everyone now receives FileMaker Pro Advanced as standard).
Does fmESignature Link (DocuSign Edition) use a plug-in?
No – fmESignature Link (DocuSign Edition) uses all native FileMaker scripts and functions.
Is FileMaker Go supported?
fmESignature Link (DocuSign Edition) can be used with FileMaker Go 16 or later. fmESignature Link uses a Web Viewer and fmp urls as part of the authentication process with the DocuSign API – if you have multiple versions of FileMaker Go installed it will attempt to use the last version of FileMaker Go that was installed when opening the fmp url. The FileMaker 18 Platform now allows version specific fmp urls (e.g. fmp18://).
We have not created iPhone and iPad specific layouts but have tested the sending of requests and downloading of completed PDF’s successfully using FileMaker Go 17 and 18 on an iPad.
Is FileMaker Cloud/FileMaker Cloud for AWS supported?
There are no issues when using a FileMaker Cloud hosted version of fmESignature Link (DocuSign Edition) when using the FileMaker Pro client application to send document signing requests and download the completed PDF from DocuSign.
The only unsupported feature is the use of Webhooks as this currently requires PHP Custom Web Publishing which is not supported by FileMaker Cloud. We’re investigating options for using the Data API which is supported by FileMaker Cloud.
What’s the best way to integrate this into my existing FileMaker solution?
How you go about integrating the functionality from the fmESignature Link (DocuSign Edition) file is entirely up to you – as the file is completely unlocked you get to go behind the scenes to learn how to send document signing requests and then recreate that in your existing FileMaker solution. Based on feedback from customers there have been three main ways they have approached the integration:
Linking – this involves using the fmESignature Link file as a ‘interface’ or front-end file to your existing FileMaker file. This is a relatively quick way to get up and running – you relink the table occurrences to reference the matching tables in your existing FileMaker file (e.g. Contacts) and then update the layouts and add any new fields. You also need to update any field references in scripts and create any new value lists.
Embedding – this is the most complex and time consuming type of integration as it involves recreating the required functionality from the fmESignature Link file in your existing FileMaker solution. Our Getting Started guide covers the high level steps that you need to take and the order in which to complete them. Most of the code can be copied and pasted, however you will need to manually create some relationships, table occurrences and value lists.
If you do decide to use the fmESignature Link file you will have to create and manage any required FileMaker Accounts and Privilege Sets.
Can I test this out first?
Yes – you can contact us to request a free trial version of fmESignature Link (DocuSign Edition) and setup a free DocuSign Sandbox account to send out an unlimited number of test signing requests. Our Getting Started Guide has more information on setting up the DocuSign Sandbox Account.
Does fmESignature Link (DocuSign Edition) support Webhooks?
We currently have support for receiving completed documents via a DocuSign Webhook – this automatically pushes the completed signed document once all parties have finished signing to your FileMaker Server. You can get further details and instructions on setting this up here.
What paper sizes do you example PDFs use?
Our example PDF files are all set to use A4 as the paper size. If you are planning to use a different paper size, such as US Letter, you will need to adjust your layouts and any scripts that generate PDF files from FileMaker layouts.
I’m getting an error “consent_required” when I try and send a request – how do I resolve this?
The “consent_required” error usually means that you have not granted consent for you app/integration. Go to the Setup screen and click the Request Application Consent button for the environment you’re working in (Sandbox or Production) and once you have granted consent you should be able to send your request successfully.
I’m having issues with the JSON data that I’m sending as part of my signing request – how can I view/debug this?
As well as using the FileMaker Pro Advanced Script Debugger and Data Viewer to debug the script and view the result of various variables and fields, you can also enable a global variable $$fmESignatureLinkDebugMode which when enabled (set to value of 1) will record a copy of the JSON data being send to the the DocuSign APIU in the Requests::EnvelopeSigningRequest field. You can enable this global variable in the OnFirstWindowOpen Script or the DocuSign – Create and Send Envelope script as required.
DocuSign also has a way of logging requests via the API – see here for more details on how to enable logging and download the DocuSign logs.
Is there a list of changes in each version of fmESignature Link (DocuSign Edition)?
Yes – to see what’s new with each update check out the fmESignature Link (DocuSign Edition) version history log